<html><head></head><body><div class="ydp55df0950yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Hi Aris</div><div><br></div><div>Can you clarify one point about this. Are you saying you want to be notified if someone changes their data that you have no direct relationship with? So if I maintain a set object and you are not part of my company and have no direct business relationship with me and I have no idea who you are, but if I modify this object you want to be notified?</div><div><br></div><div>cheers</div><div>denis</div><div>co-chair DB-WG</div><div><br></div>
</div><div id="ydpad051f14yahoo_quoted_3310337349" class="ydpad051f14yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Saturday, 23 March 2019, 01:02:48 CET, Aris Lambrianidis via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Wilfried,<br clear="none"><br clear="none">Thank you for the effort in helping out!<br clear="none"><br clear="none">Unfortunately this will not do as:<br clear="none"><br clear="none">1. It notifies via an "out-of-band" method (i.e. email). This makes<br clear="none">it difficult (but not impossible) to handle with automation. <br clear="none">Nonetheless, the<br clear="none">more elegant way would be through an API leveraging a push mechanism.<br clear="none"><br clear="none">but more importantly:<br clear="none"><br clear="none">2. the "notify:" attribute has to actually be configured with an address <br clear="none">of the<br clear="none">interested party for it to work.<br clear="none"><br clear="none">However I'm looking for mechanism for interested parties to be notified of<br clear="none">any changes in objects independently to what the maintainer has configured<br clear="none">as a notify address.<br clear="none"><br clear="none">Kind regards,<br clear="none">Aris<br clear="none"><br clear="none"><div class="ydpad051f14yqt4670213523" id="ydpad051f14yqtfd05341"><br clear="none">Wilfried Wöber wrote on 22/03/2019 21:50:<br clear="none">> Hi Aris!<br clear="none">><br clear="none">> Is this what you are looking for?<br clear="none">><br clear="none">> <a shape="rect" href="https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/notifications/9-2-notification-messages/9-2-1-notification-attributes" rel="nofollow" target="_blank">https://www.ripe.net/manage-ips-and-asns/db/support/documentation/ripe-database-documentation/notifications/9-2-notification-messages/9-2-1-notification-attributes</a><br clear="none">><br clear="none">> I may be off-track, of course :-)<br clear="none">> Wilfried<br clear="none">><br clear="none">> On 22/03/2019 20:29, Aris Lambrianidis via db-wg wrote:<br clear="none">>> Dear all,<br clear="none">>><br clear="none">>> Back in the day, RFC1996 introduced the NOTIFY mechanism in DNS, which significantly helped with information propagation delay,<br clear="none">>> as it facilitated the transition from a pull (poll) to a push (interrupt) model.<br clear="none">>><br clear="none">>> The problem we, as AMS-IX, are facing is quite similar when it comes to polling the RIPE database for changes. This seems<br clear="none">>> inefficient.<br clear="none">>><br clear="none">>> Although the analogy breaks down quickly, as there are no RIPE database "clients" similar to DNS slave servers<br clear="none">>> parsing NOTIFY messages, we would love to see any RIPE API created or extended, or any other mechanism implemented by which<br clear="none">>> a client "registers interest" for any objects it wants to be notified of changes.<br clear="none">>><br clear="none">>> As a simple example, if we were to "register interest" (e.g. via a REST POST or PUT method) for the AS-AMS-IX-SET as-set object, we would be<br clear="none">>> programmatically notified whenever the "last-modified" field of the as-set was changed.<br clear="none">>><br clear="none">>> Based on the above, I have 3 questions:<br clear="none">>> 1. Does something like what is described above already exist?<br clear="none">>> 2. If it doesn't exist, would others be interested on such functionality?<br clear="none">>> 3. If it doesn't exist, while knowing that this is only a high level overview of the concept and many details are missing, is this generally feasible?<br clear="none">>><br clear="none">>> Kind regards,<br clear="none">>> Aris Lambrianidis<br clear="none">>> AMS-IX<br clear="none">>><br clear="none"><br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>