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