<div dir="ltr"><div dir="ltr">While I generally support the idea behind this change, the specifics of the language added to the RSA matters significantly. Furthermore, I do not believe that the language added to the RSA should be specific to routing. The language added to the RSA should be more generic, such as a commitment to not deliberately interfere with another registrant's use of the resources that are registered to them within the context of their use on Internet and not limited to any specific form of interference. Where making route announcements for blocks without permission of the registrant should be a specific example of such prohibited interference. </div><div dir="ltr"><br></div><div dir="ltr">Also, ARIN will need to create formal procedures, in addition to the informal procedures discussed in the following;</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://teamarin.net/2019/05/06/how-does-arin-handle-reports-of-route-hijacking/" target="_blank">https://teamarin.net/2019/05/06/how-does-arin-handle-reports-of-route-hijacking/</a> </div><div dir="ltr"><br></div><div dir="ltr">I think only the registrant affected should be able to formally make a complaint and such a complaint is only actionable by ARIN after the accused is given a formal opportunity to cure the complaint.</div><div dir="ltr"><br></div><div>I think this type of change to the RSA is important and within the scope of the industry self-regulatory framework that the RIR system is intended to provide. Further, such a change promotes an equitable registry system, entities that are unwilling to respect other's registrations do not deserve the protections afforded to them by the registry system. For the RIR system to be taken seriously and provide effective industry self-regulation it needs a mechanism to sanction those that systematically and egregiously thwart the fundamental intent of the registry system, especially when such activities constitute deliberate interference with the proper operation of the Internet. <br><br></div><div>That said, while in my opinion, this change is necessary, it is only a very small part of the overall fix for the problem, as most incidents are neither systematic or egregious, and are usually not deliberate, most incidences are merely accidental. In addition this change to the RSA, the industry needs to adopt best practices for routing security, including route filtering and RPKI, to prevent and mitigate these accidental incidents, such as promoted by the MANRS program;</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://www.manrs.org/">https://www.manrs.org/</a><br></div><div><br></div><div>Thanks. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 31, 2019 at 2:24 PM ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.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">On 31 July, we received a new suggestion, numbered 2019.17 upon confirmed<br>
receipt, that ARIN update its Registration Services Agreement. Staff is<br>
reviewing this suggestion and will issue a formal response once analysis <br>
is complete.<br>
<br>
The full text of the suggestion may be found below or at:<br>
<br>
<a href="https://www.arin.net/participate/community/acsp/suggestions/2019-17/" rel="noreferrer" target="_blank">https://www.arin.net/participate/community/acsp/suggestions/2019-17/</a><br>
<br>
***<br>
<br>
Description: ARIN should modify its Registration Services Agreement so <br>
that address holders agree to only announce routing for its own address <br>
blocks, or those address blocks for which it has obtained permission of <br>
the registrant as listed in the Internet Number Registry System.<br>
<br>
Value to Community: The additional value to the community would be that <br>
ARIN address holders would be far less likely to hijack routes as it <br>
would represent a breach of their agreement with ARIN.<br>
<br>
Timeframe: Not specified<br>
<br>
***<br>
<br>
Regards,<br>
<br>
Communications and Member Services<br>
American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>
_______________________________________________<br>
arin-suggestions mailing list<br>
<a href="mailto:arin-suggestions@arin.net" target="_blank">arin-suggestions@arin.net</a><br>
<a href="https://lists.arin.net/mailman/listinfo/arin-suggestions" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-suggestions</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-5200970538260029595m_-7240009749905681881m_1766390749043026100m_-864264758959371257m_-222091773504166411gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== </div></div>