<html><head></head><body><div style="color:#000; background-color:#fff; font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><span id="yui_3_16_0_ym19_1_1507715420084_719210">Hi Job</span><div class="qtdSeparateBR"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1507715420084_719165" style="display: block;"><div style="font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1507715420084_719164"><div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1507715420084_719163"><div class="y_msg_container" id="yui_3_16_0_ym19_1_1507715420084_719168"><div id="yiv4972883340"><div id="yui_3_16_0_ym19_1_1507715420084_719171"><div style="color:#000;background-color:#fff;font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;" id="yui_3_16_0_ym19_1_1507715420084_719170"><div id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674462"><span><br clear="none"></span></div><div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674465"><span id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674499">I agree with your assessment and, although it should be in a separate thread later, I think it's worth having a discussion about notifying resource holders if a foreign ROUTE object is created in the RIPE Database. But lets focus on the main points for now.</span></div><div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674548"><span id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674499"><br clear="none"></span></div><div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674558"><span id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674499">cheers</span></div><div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674560"><span id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674499">denis<br clear="none"></span></div><div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674565"><span id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674499">co-chair DB WG</span></div><div class="yiv4972883340qtdSeparateBR" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674441"><br clear="none"><br clear="none"></div><div class="yiv4972883340yqt8714446602" id="yiv4972883340yqt81416"><div class="yiv4972883340yahoo_quoted" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674445" style="display:block;"> <div id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674444" style="font-family:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674443" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif;font-size:16px;"> <div dir="ltr" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674442"> <font id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674502" face="Arial" size="2"> </font><hr id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674501" size="1"> <b><span style="font-weight:bold;">From:</span></b> Job Snijders via db-wg <db-wg@ripe.net><br clear="none"> <b><span style="font-weight:bold;">To:</span></b> den is <denis1@gmail.com> <br clear="none"><b><span style="font-weight:bold;">Cc:</span></b> Database WG <db-wg@ripe.net><br clear="none"> <b><span style="font-weight:bold;">Sent:</span></b> Tuesday, 17 October 2017, 10:06<br clear="none"> <b><span style="font-weight:bold;">Subject:</span></b> Re: [db-wg] Foreign ROUTE objects in RIPE Database - final decision?<br clear="none"> </div> <div class="yiv4972883340y_msg_container" id="yiv4972883340yui_3_16_0_ym19_1_1507715420084_674586"><br clear="none">Dear Denis,<br clear="none"><br clear="none">Just to make sure we are on the same page, the 2 items presented by Bill<br clear="none">are not two mutually exclusive options, I think both need to be done. <br clear="none"><div class="yiv4972883340yqt8904217029" id="yiv4972883340yqtfd32606"><br clear="none">On Tue, Oct 17, 2017 at 01:04:08AM +0000, den is via db-wg wrote:<br clear="none">> 3) Consider possible, simple options to allow non RIPE resource<br clear="none">> holders to 'approve' (if not authorise) the creation of a foreign<br clear="none">> ROUTE object.</div><br clear="none"><br clear="none">An even simpler option is to not even attempt to authorize the creation<br clear="none">of non-RIPE route objects, but simply flag them as "RIPE-NONAUTH". If<br clear="none">people want to create authoritive route objects for non-RIPE-managed<br clear="none">space they can create those objects in the DB from the RIR where the<br clear="none">space is managed (APNIC, AFRINIC, etc).<br clear="none"><br clear="none">While on the surface of things, it looks trivial to have the RIPE<br clear="none">database software fire off an email to what most probably is the<br clear="none">legitimate 'foreign' owner of the IP block, it introduces quite some<br clear="none">complexity such as "what if the resource is transfer to a new owner"<br clear="none">"what if the resource is transferred to a new owner and a new RIR". Even<br clear="none">though at some point in the past a form of approval was given, a day<br clear="none">later that approval may have been revoked. The RIPE DB would have to<br clear="none">continuously track movement of IP space. <br clear="none"><br clear="none">The continuously tracking of ownership aspects in other databases<br clear="none">certainly can be done, but now the project no longer is simple low<br clear="none">hanging fruit. <br clear="none"><br clear="none">I see some value if the RIPE DB could notify owners of non-RIPE IP<br clear="none">blocks when non-authoritative data is created in the RIPE DB, but I<br clear="none">think that would be something to consider in the future.<br clear="none"><br clear="none">Kind regards,<br clear="none"><br clear="none">Job<div class="yiv4972883340yqt8904217029" id="yiv4972883340yqtfd54994"><br clear="none"><br clear="none"><br clear="none"></div><br clear="none"><br clear="none"></div> </div> </div> </div></div></div></div></div><br><br></div> </div> </div> </div></div></body></html>