<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="">
On 12 Sep 2016, at 10:05 AM, David R Huberman <<a href="mailto:daveid@panix.com" class="">daveid@panix.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class="">WG and staff,<br class="">
<br class="">
I have re-reviewed the CKN23 document, and in light of our call, here are my final thoughts:<br class="">
<br class="">
1) I agree with Matt that hijackers are more normally going to use Whois to verify what they already know: that a block is abandoned and ripe for their misuse.<br class="">
<br class="">
2) If, as reported by staff, ARIN is receiving 5-10 calls a week on this, that doesn't seem like a "problem" to me. Rather, it seems like CKN23-ARIN is working as intended. It's causing registrants to contact ARIN and, unwillingly or not, learn how to update
their registration information. I see this as highly valuable to the community -- more up-to-date contact information is good. If the registrant who contacts ARIN to complain does not ultimately update their information, then I can only assume it either wasn't
important enough of a problem to them to actually do anything about it, or perhaps they really shouldnt be listed :)<br class="">
<br class="">
3) Formally, I support Option #1, the do nothing option. But I can support Option #3, reinstating old resource tech POCs back to the resource, but locking to prevent them from making rDNS changes without validation.</div>
</div>
</blockquote>
<br class="">
</div>
<div>Members of the ARIN Services Working Group -</div>
<div><br class="">
</div>
<div>Welcome to 2017, including formal resumption of our ARIN Services WG efforts! </div>
<div><br class="">
</div>
<div>Based on the discussion within the Services WG (and some discussion in halls at </div>
<div>the October ARIN meeting) on the topic of CKN-23 cleanup, I am proposing that </div>
<div>the ARIN proceed with Option 3 (i.e. the restoration of the admin and tech resource </div>
<div>points-of-contact and locking the record.) (See attached email for a refresher if </div>
<div>desired.)</div>
<div><br class="">
</div>
<div>This change would provide legacy resource holders with entries which most closely </div>
<div>resemble that which was originally registered (rather than having only the oblique </div>
<div>“abuse POC” entry), yet does not significantly alter the steps necessary to make </div>
<div>changes to the number resource (i.e. parties must have access to the original email </div>
<div>or perform recovery to make substantial changes to their number resources.) </div>
<div><br class="">
</div>
<div>I am now preparing a community consultation proposing this change (including the </div>
<div>supporting material that was reviewed by the Services WG), and will include one of</div>
<div>the following statements or equivalent - </div>
<div><br class="">
</div>
<div> A) “The ARIN Services Working Group reviewed this proposed change and is supportive”</div>
<div><br class="">
</div>
<div>
<div> B) “The ARIN Services Working Group reviewed this proposed change and does not support</div>
<div> proceeding as suggested.”</div>
<div><br class="">
</div>
<div> C) “I would like to thank the ARIN Services WG for their helpful review of the proposed </div>
<div> change and resulting improvements to the supporting materials, noting at this time</div>
<div> that the Services WG did not take formal position in support or opposition to the </div>
<div> proposal.”</div>
<div><br class="">
</div>
<div>From the earlier discussion on the list, one could argue for any of the above outcomes; </div>
<div>I’d ask that the Services WG converge on one of the three outcomes listed above (and</div>
<div>I would be happy to coordinate with the Chair to schedule a teleconference if needed for</div>
<div>this purpose.) </div>
<div class=""><br class="">
</div>
<div class="">Thank you!</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>
<div><br class="">
</div>
<div>
<div class="">Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<div style="margin: 0px;" class=""></div>
<blockquote type="cite" class="">
<div style="margin: 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="">John
Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>><br class="">
</span></div>
<div style="margin: 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="">[Services-wg]
ARIN Services WG - CKN23 materials for your consideration</b><br class="">
</span></div>
<div style="margin: 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="">14
June 2016 at 1:58:09 AM PDT<br class="">
</span></div>
<div style="margin: 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:services-wg@arin.net" class="">services-wg@arin.net</a>"
<<a href="mailto:services-wg@arin.net" class="">services-wg@arin.net</a>><br class="">
</span></div>
<br class="">
<div class="">ARIN Services WG (SWG) - <br class="">
<br class="">
Please find attached the “CKN23" project document and an overview slide deck<br class="">
of same, for your consideration. Leslie Nobile produced these and is available <br class="">
to brief the Services WG on the issue and potential options for moving forward.<br class="">
<br class="">
It would be my desire the Services WG consider the matter and provide an initial <br class="">
recommendation on how to proceed. I would inform the ARIN community of this <br class="">
direction by putting the matter out for community consultation along with the SWG’s <br class="">
recommendation.<br class="">
<br class="">
Please review the materials at your convenience, and we’ll arrange a teleconference<br class="">
in the near future to review jointly.<br class="">
<br class="">
Thank you!<br class="">
/John<br class="">
<br class="">
John Curran<br class="">
President and CEO<br class="">
ARIN<br class="">
<br class="">
<br class="">
</div>
</blockquote>
</div>
</body>
</html>