<div dir="ltr"><div dir="ltr" class="gmail_msg">I support Option 3.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">--</div><div class="gmail_msg">Brian</div></div><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Wed, Mar 29, 2017 at 1:34 PM Owen DeLong <<a href="mailto:owen@delong.com" class="gmail_msg" target="_blank">owen@delong.com</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">I support recommended option 3.</div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Owen</div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Mar 27, 2017, at 12:39 , John Curran <<a href="mailto:jcurran@arin.net" class="gmail_msg" target="_blank">jcurran@arin.net</a>> wrote:</div><br class="m_2476349953394261685m_-4219225130323408747Apple-interchange-newline gmail_msg"><div class="gmail_msg">
<div style="word-wrap:break-word" class="gmail_msg">
<div style="word-wrap:break-word" class="gmail_msg">
Folks -
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg"> We have initiated a community consultation on a possible restructuring of existing </div>
<div class="gmail_msg"> information in the ARIN registry – this is to address the long-standing concern that</div>
<div class="gmail_msg"> some have expressed with the association of a “No Contact Known” point-of-contact</div>
<div class="gmail_msg"> (POC) in some registry records that may have potentially valid Admin and Tech </div>
<div class="gmail_msg"> contact information. </div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg"> If you have hold a strong view on this matter, please see the attached consultation </div>
<div class="gmail_msg"> announcement and participate in the discussion on the arin-consult mailing list. </div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">Thanks!</div>
<div class="gmail_msg">/John</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">John Curran</div>
<div class="gmail_msg">President and CEO</div>
<div class="gmail_msg">ARIN</div>
<div class="gmail_msg"><br class="gmail_msg">
</div>
<div class="gmail_msg">===</div>
<div class="gmail_msg">
<div class="gmail_msg"><br class="gmail_msg">
<blockquote type="cite" class="gmail_msg">
<div class="gmail_msg">Begin forwarded message:</div>
<br class="m_2476349953394261685m_-4219225130323408747Apple-interchange-newline gmail_msg">
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" class="gmail_msg">
<span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif" class="gmail_msg"><b class="gmail_msg">From:
</b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif" class="gmail_msg">ARIN <<a href="mailto:info@arin.net" class="gmail_msg" target="_blank">info@arin.net</a>><br class="gmail_msg">
</span></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" class="gmail_msg">
<span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif" class="gmail_msg"><b class="gmail_msg">Subject:
</b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif" class="gmail_msg"><b class="gmail_msg">[ARIN-consult] Community Consultation on CKN23-ARIN Now Open</b><br class="gmail_msg">
</span></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" class="gmail_msg">
<span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif" class="gmail_msg"><b class="gmail_msg">Date:
</b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif" class="gmail_msg">22 March 2017 at 1:24:12 PM EDT<br class="gmail_msg">
</span></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px" class="gmail_msg">
<span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif" class="gmail_msg"><b class="gmail_msg">To:
</b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif" class="gmail_msg"><<a href="mailto:arin-consult@arin.net" class="gmail_msg" target="_blank">arin-consult@arin.net</a>><br class="gmail_msg">
</span></div>
<br class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">There are thousands of instances of the ARIN Point of Contact (POC)<br class="gmail_msg">
handle “No, Contact Known” or CKN23-ARIN registered in the ARIN<br class="gmail_msg">
database, most of them associated with legacy resource records. ARIN<br class="gmail_msg">
would like the community to review the history of this situation and the<br class="gmail_msg">
proposed solution and provide us with their feedback.<br class="gmail_msg">
<br class="gmail_msg">
The creation and addition of this POC handle was due to a combination of<br class="gmail_msg">
factors.<br class="gmail_msg">
<br class="gmail_msg">
* In 2002, a database conversion project was done at ARIN that<br class="gmail_msg">
created a new database structure and added a new record type<br class="gmail_msg">
(Organization ID) as well as new POC types (Admin, Tech, Abuse and NOC).<br class="gmail_msg">
When an Org ID didn’t have a clear POC that had been recently updated or<br class="gmail_msg">
vetted by ARIN staff, the original resource POC remained on the resource<br class="gmail_msg">
record only and no POCs were added to the Org record at all.<br class="gmail_msg">
* In a later 2011 database conversion, reverse DNS delegation<br class="gmail_msg">
switched from per-net to per-zone. This created significant hijacking<br class="gmail_msg">
potential by allowing resource POCs to change their reverse delegation<br class="gmail_msg">
without first being verified by staff as legitimate.<br class="gmail_msg">
* Also in 2011, ARIN added a new business rule that required an Admin<br class="gmail_msg">
and a Tech POC on all Org records as a way of enhancing data quality.<br class="gmail_msg">
* Policy 2010-14 was implemented in 2011 and required Abuse POCs on<br class="gmail_msg">
all Org records.<br class="gmail_msg">
<br class="gmail_msg">
In order to maintain ARIN’s business rules, comply with policy 2010-14,<br class="gmail_msg">
and prevent hijackings, several actions were initiated by staff:<br class="gmail_msg">
<br class="gmail_msg">
* CKN23-ARIN was created to become the Admin and Tech POC on Orgs<br class="gmail_msg">
that lacked them<br class="gmail_msg">
* Resource POCs of legacy networks that had never been updated or<br class="gmail_msg">
validated by ARIN were moved to the Organization record as the Abuse POC<br class="gmail_msg">
* ARIN’s verification and vetting requirements were thus reinstated<br class="gmail_msg">
as the Abuse POC had to be vetted before making any changes to the<br class="gmail_msg">
record, and therefore could not hijack the resource by adding or<br class="gmail_msg">
changing the nameservers<br class="gmail_msg">
<br class="gmail_msg">
Over time, the above actions have created several issues:<br class="gmail_msg">
<br class="gmail_msg">
* It is easy for hijackers to identify and target records with CKN23<br class="gmail_msg">
(no contact known) as the handle<br class="gmail_msg">
* POCs that were moved from resource tech to Org abuse are not happy<br class="gmail_msg">
about no longer having control of their resource record<br class="gmail_msg">
<br class="gmail_msg">
There are several different courses of action that ARIN could take to<br class="gmail_msg">
resolve the current situation.<br class="gmail_msg">
<br class="gmail_msg">
Option 1<br class="gmail_msg">
<br class="gmail_msg">
Retain the current status and do nothing<br class="gmail_msg">
<br class="gmail_msg">
Option 2<br class="gmail_msg">
<br class="gmail_msg">
Restore the resource POCs back to their original state on the<br class="gmail_msg">
resource record keeping in mind that this would open up the hijacking<br class="gmail_msg">
risk by giving the original resource POC control of the network without<br class="gmail_msg">
a verification process<br class="gmail_msg">
* Retain the Abuse POC on the Org record<br class="gmail_msg">
* Retain CKN23-ARIN as Org POC<br class="gmail_msg">
<br class="gmail_msg">
Option 3 - **Recommended option**<br class="gmail_msg">
<br class="gmail_msg">
Restore the resource POC back to their original state on the<br class="gmail_msg">
resource record. This will allow contacts historically associated with<br class="gmail_msg">
a resource record to more readily administer that record going forward.<br class="gmail_msg">
* Retain the Abuse POC on the Org<br class="gmail_msg">
* Replace CKN23-ARIN with a handle that better explains the record’s<br class="gmail_msg">
status (e.g. “Legacy Record – See Resource POC”)<br class="gmail_msg">
* Lock all resources associated with these legacy records who have<br class="gmail_msg">
had their resource POC restored. This would ensure that any changes made<br class="gmail_msg">
by the resource POC would first have to be reviewed by ARIN.<br class="gmail_msg">
<br class="gmail_msg">
We would like to thank the ARIN Services Working Group (WG) for their<br class="gmail_msg">
helpful review of the proposed change – while the ARIN Services WG did<br class="gmail_msg">
not take a formal position in support of or in opposition of the<br class="gmail_msg">
proposed change, their review led to improvements in presentation of the<br class="gmail_msg">
options<br class="gmail_msg">
<br class="gmail_msg">
We are seeking community feedback on this proposed change (Option #3) to<br class="gmail_msg">
the ARIN Registry database.<br class="gmail_msg">
<br class="gmail_msg">
This consultation will remain open for 60 days - Please provide comments<br class="gmail_msg">
to <a href="mailto:arin-consult@arin.net" class="gmail_msg" target="_blank">arin-consult@arin.net</a>.<br class="gmail_msg">
<br class="gmail_msg">
Discussion on <a href="mailto:arin-consult@arin.net" class="gmail_msg" target="_blank">arin-consult@arin.net</a> will close on 22 May 2017.<br class="gmail_msg">
<br class="gmail_msg">
If you have any questions, please contact us at <a href="mailto:info@arin.net" class="gmail_msg" target="_blank">
info@arin.net</a>.<br class="gmail_msg">
<br class="gmail_msg">
Regards,<br class="gmail_msg">
<br class="gmail_msg">
John Curran<br class="gmail_msg">
President and CEO<br class="gmail_msg">
American Registry for Internet Numbers (ARIN)<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
ARIN-Consult<br class="gmail_msg">
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="gmail_msg">
List (<a href="mailto:ARIN-consult@arin.net" class="gmail_msg" target="_blank">ARIN-consult@arin.net</a>).<br class="gmail_msg">
Unsubscribe or manage your mailing list subscription at:<br class="gmail_msg">
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="gmail_msg" target="_blank">http://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="gmail_msg">
Help Desk at <a href="mailto:info@arin.net" class="gmail_msg" target="_blank">info@arin.net</a> if you experience any issues.</div>
</div>
</blockquote>
</div>
<br class="gmail_msg">
</div>
</div>
</div>
_______________________________________________<br class="gmail_msg">PPML<br class="gmail_msg">You are receiving this message because you are subscribed to<br class="gmail_msg">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="gmail_msg" target="_blank">ARIN-PPML@arin.net</a>).<br class="gmail_msg">Unsubscribe or manage your mailing list subscription at:<br class="gmail_msg"><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="gmail_msg" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="gmail_msg">Please contact <a href="mailto:info@arin.net" class="gmail_msg" target="_blank">info@arin.net</a> if you experience any issues.</div></blockquote></div><br class="gmail_msg"></div></div>_______________________________________________<br class="gmail_msg">
PPML<br class="gmail_msg">
You are receiving this message because you are subscribed to<br class="gmail_msg">
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="gmail_msg" target="_blank">ARIN-PPML@arin.net</a>).<br class="gmail_msg">
Unsubscribe or manage your mailing list subscription at:<br class="gmail_msg">
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="gmail_msg">
Please contact <a href="mailto:info@arin.net" class="gmail_msg" target="_blank">info@arin.net</a> if you experience any issues.</blockquote></div></div></div></div>