<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#000000" bgcolor="#FFFFFF">Hi Job,<br>
<br>
AFAIK (and perhaps I'm missing something) an NRTM feed has a few
drawbacks:<br>
<br>
1. It still is a pull rather than a push mechanism<br>
2. It doesn't allow any granularity to receiving only specific objects:
We would<br>
need to receive all of the database as-set and aut-num objects and parse
them for the ones we're interested in<br>
3. It needs some red tape before being able to consume it <br>
<br>
Kind regards,<br>
Aris<br>
<br>
<span>Job Snijders wrote on 23/03/2019 20:05:</span><br>
<blockquote type="cite"
cite="mid:CACWOCC_P6hh_E0ds7jXzBC8Y3FJ5tyFMD3so9kBJwztA4xW+Dw@mail.gmail.com">
<div><div dir="auto">Dear Aris,</div></div>
<div dir="auto"><br></div>
<div dir="auto">Did you consider consuming a NRTM feed? That’s an
approach that already exists.</div>
<div dir="auto"><br></div>
<div dir="auto">Kind regards,</div>
<div dir="auto"><br></div>
<div dir="auto">Job</div>
<div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On
Sat, Mar 23, 2019 at 19:22 Aris Lambrianidis via db-wg <<a
href="mailto:db-wg@ripe.net" moz-do-not-send="true">db-wg@ripe.net</a>>
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000"
bgcolor="#FFFFFF">Hi Denis,<br>
<br>
We, and other IXPs, create filters (prefix-lists) for services such as
route servers, by parsing aut-num and as-set objects from IRR databases,
such as the RIPE database, using tools such as bgpq3. <br>
<br>
Right now, to the best of my knowledge, the only way to maintain those
filters up to date for all of our route server peers, is to periodically
poll IRR databases for changes. <br>
IMO it would seem more efficient if the database itself notified us of
any changes, rather than us constantly asking the same question(s).<br>
<br>
Does this make sense?<br>
<br>
That said, I can also think of other use cases in which interested
parties having no direct relationship to certain objects and their
maintainers are interested in finding out of any changes, <br>
especially in the field of research, but let me not delve into this and
keep things simple for the time being.<br>
<br>
Kind regards,<br>
Aris</div><div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<span><a class="m_-4174280507711073586moz-txt-link-abbreviated"
href="mailto:ripedenis@yahoo.co.uk" target="_blank"
moz-do-not-send="true">ripedenis@yahoo.co.uk</a> wrote on 23/03/2019
02:26:</span><br>
<blockquote type="cite"><div
class="m_-4174280507711073586ydp55df0950yahoo-style-wrap"
style="font-family:Helvetica
Neue,Helvetica,Arial,sans-serif;font-size:16px">
<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="m_-4174280507711073586ydpad051f14yahoo_quoted_3310337349"
class="m_-4174280507711073586ydpad051f14yahoo_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 <a
class="m_-4174280507711073586moz-txt-link-rfc2396E"
href="mailto:db-wg@ripe.net" target="_blank" moz-do-not-send="true"><db-wg@ripe.net></a>
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="m_-4174280507711073586ydpad051f14yqt4670213523"
id="m_-4174280507711073586ydpad051f14yqtfd05341"><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" moz-do-not-send="true">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></blockquote>
<br>
</div></blockquote></div></div>
</blockquote>
<br>
</body></html>