<html><head></head><body><div class="ydp6237c1a0yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>HI guys</div><div><br></div><div>You seem to now be suggesting that a form of NRTM for only routing information<span><span style="color: rgb(0, 0, 0); font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 16px;"> (IRR data) and open to anyone without a contract</span></span> would satisfy what you are looking for. I thought NRTM is a pull mechanism not a push? Aris mentioned you need this info to 'create filters'. Not being a routing expert, is this something you do periodically or in real time as routing information changes? If it's periodically then to pull an edited NRTM stream, only containing operational routing data updates, would work. If you want changes to routing data in the RIPE Database to trigger filter creation then you do need a new push mechanism.</div><div><br></div><div>cheers</div><div>denis</div><div>co-chair DB-WG</div><div><br></div>
</div><div id="ydp93c4bc0ayahoo_quoted_4393789594" class="ydp93c4bc0ayahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Sunday, 24 March 2019, 11:58:40 CET, Cynthia Revström via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">Hi Job,<br clear="none"><br clear="none">I guess you have a point seeing as the non-realtime DB files are public <br clear="none">without any paperwork.<br clear="none"><br clear="none">- Cynthia<br clear="none"><div class="ydp93c4bc0ayqt1280887221" id="ydp93c4bc0ayqtfd40527"><br clear="none">On 2019-03-24 10:46, Job Snijders wrote:<br clear="none">> In order to provide the most value to RIPE NCC's members, I'd argue<br clear="none">> that we need to remove ALL the paperwork e.g. allow any IP address to<br clear="none">> set up a NRTM stream for the purpose of mirroring IRR objects that<br clear="none">> contain routing information: route/route6/route-set/as-set. NTT is<br clear="none">> mirroring the RIPE database at rr.ntt.net and we filter away anything<br clear="none">> non-routing anyhow.<br clear="none">><br clear="none">> The current NRTM agreement poses a significant barrier, the barrier<br clear="none">> can be easily be circumvented; so it only causes harm.<br clear="none">><br clear="none">> Having an agreement in place for IRR data that contains PII,<br clear="none">> Organisation or any non-routing information is fine with me. That data<br clear="none">> has no value in router configuration automation pipelines anyway.<br clear="none">><br clear="none">> Kind regards,<br clear="none">><br clear="none">> Job<br clear="none"><br clear="none"></div></div></div>
</div>
</div></body></html>