<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none"></style> </head> <body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;"> <p>+1<br> </p> <p><br> </p> <div id="Signature"> <div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0"> - Torunn</div> </div> <div style="color: rgb(33, 33, 33);"> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Fra:</b> routing-wg <routing-wg-bounces@ripe.net> p� vegne av Andreas Larsen <andreas@1o.se><br> <b>Sendt:</b> 14. august 2019 17:28<br> <b>Til:</b> Melchior Aelmans<br> <b>Kopi:</b> RIPE Routing Working Group<br> <b>Emne:</b> Re: [routing-wg] 2018-06 Review Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)</font> <div> </div> </div> <div> <div dir="auto">+1 <div dir="auto"><br> </div> <div dir="auto"><br> </div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">Den 14 aug. 2019 17:18 skrev Melchior Aelmans <melchior@aelmans.eu>:<br type="attribution"> </div> </div> <div> <div dir="ltr"> <div>+1 we should do this now.<br> </div> <br> <div class="gmail_quote"> <div dir="ltr" class="gmail_attr">On Wed, Aug 14, 2019 at 5:06 PM Paul Hoogsteder <<a href="mailto:paul@meanie.nl">paul@meanie.nl</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex"> <div dir="auto"> <div dir="ltr"></div> <div dir="ltr">Yes, I think we should go ahead with this.</div> <div dir="ltr"><br> </div> <div dir="ltr">Kind regards,</div> <div dir="ltr"><br> </div> <div dir="ltr">Paul Hoogsteder.</div> <div dir="ltr"><br> On 14 Aug 2019, at 16:00, Job Snijders <<a href="mailto:job@ntt.net" target="_blank">job@ntt.net</a>> wrote:<br> <br> </div> <blockquote type="cite"> <div dir="ltr"> <div> <div dir="auto">Dear all,</div> </div> <div dir="auto"><br> </div> <div dir="auto">Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal.</div> <div dir="auto"><br> </div> <div dir="auto">As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source.</div> <div dir="auto"><br> </div> <div dir="auto">I look forward to hearing the groups’ thoughts on how to proceed.</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 Wed, 14 Aug 2019 at 15:24, Marco Schmidt <<a href="mailto:mschmidt@ripe.net" target="_blank">mschmidt@ripe.net</a>> wrote:<br> </div> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px solid rgb(204,204,204); padding-left:1ex"> Dear colleagues,<br> <br> Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route <br> Object Clean-up", is now in the Review Phase.<br> <br> The goal of the proposal is to delete an non-authoritative object stored <br> in the RIPE IRR, if it conflicts with an RPKI ROA.<br> <br> The proposal has been updated following the last round of discussion and <br> is now at version v3.0. Some of the differences from version v2.0 include:<br> - Provides details about the process how to identify and solve conflicts<br> <br> The RIPE NCC has prepared an impact analysis on this latest proposal <br> version to support the community’s discussion. You can find the full <br> proposal and impact analysis at:<br> <a href="https://www.ripe.net/participate/policies/proposals/2018-06" rel="noreferrer" target="_blank">https://www.ripe.net/participate/policies/proposals/2018-06</a><br> <br> And the draft documents at:<br> <a href="https://www.ripe.net/participate/policies/proposals/2018-06/draft" rel="noreferrer" target="_blank">https://www.ripe.net/participate/policies/proposals/2018-06/draft</a><br> <br> As per the RIPE Policy Development Process (PDP), the purpose of this <br> four week Review Phase is to continue discussion of the proposal, taking <br> the impact analysis into consideration, and to review the full draft <br> RIPE Policy Document.<br> <br> At the end of the Review Phase, the Working Group (WG) Chairs will <br> determine whether the WG has reached rough consensus. It is therefore <br> important to provide your opinion, even if it is simply a restatement of <br> your input from the previous phase.<br> <br> We encourage you to read the proposal, impact analysis and draft <br> document and send any comments to <<a href="mailto:routing-wg@ripe.net" target="_blank">routing-wg@ripe.net</a>> before 12 <br> September 2019.<br> <br> Kind regards,<br> <br> Marco Schmidt<br> Policy Officer<br> RIPE NCC<br> <br> <br> </blockquote> </div> </div> </div> </blockquote> </div> </blockquote> </div> </div> </div> </div> </div> </body> </html>