<div dir="ltr">A or C seems fine.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 26, 2017 at 11:34 PM, John Curran <span dir="ltr"><<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
On 12 Sep 2016, at 10:05 AM, David R Huberman <<a href="mailto:daveid@panix.com" target="_blank">daveid@panix.com</a>> wrote:<br>
<div>
<blockquote type="cite"><br class="m_-980946247610967532Apple-interchange-newline">
<div>
<div>WG and staff,<br>
<br>
I have re-reviewed the CKN23 document, and in light of our call, here are my final thoughts:<br>
<br>
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>
<br>
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>
<br>
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>
</div>
<div>Members of the ARIN Services Working Group -</div>
<div><br>
</div>
<div>Welcome to 2017, including formal resumption of our ARIN Services WG efforts! </div>
<div><br>
</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>
</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>
</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>
</div>
<div> A) “The ARIN Services Working Group reviewed this proposed change and is supportive”</div>
<div><br>
</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>
</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>
</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><br>
</div>
<div>Thank you!</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
</div>
<div><br>
</div>
<div>
<div>Begin forwarded message:</div>
<br class="m_-980946247610967532Apple-interchange-newline">
<div style="margin:0px"></div>
<blockquote type="cite">
<div style="margin:0px"><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif"><b>From: </b></span><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif">John
Curran <<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>><br>
</span></div>
<div style="margin:0px"><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif"><b>Subject: </b></span><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif"><b>[Services-wg]
ARIN Services WG - CKN23 materials for your consideration</b><br>
</span></div>
<div style="margin:0px"><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif"><b>Date: </b></span><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif">14
June 2016 at 1:58:09 AM PDT<br>
</span></div>
<div style="margin:0px"><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif"><b>To: </b></span><span style="font-family:-webkit-system-font,'Helvetica Neue',Helvetica,sans-serif">"<a href="mailto:services-wg@arin.net" target="_blank">services-wg@arin.net</a>"
<<a href="mailto:services-wg@arin.net" target="_blank">services-wg@arin.net</a>><br>
</span></div>
<br>
<div>ARIN Services WG (SWG) - <br>
<br>
Please find attached the “CKN23" project document and an overview slide deck<br>
of same, for your consideration. Leslie Nobile produced these and is available <br>
to brief the Services WG on the issue and potential options for moving forward.<br>
<br>
It would be my desire the Services WG consider the matter and provide an initial <br>
recommendation on how to proceed. I would inform the ARIN community of this <br>
direction by putting the matter out for community consultation along with the SWG’s <br>
recommendation.<br>
<br>
Please review the materials at your convenience, and we’ll arrange a teleconference<br>
in the near future to review jointly.<br>
<br>
Thank you!<br>
/John<br>
<br>
John Curran<br>
President and CEO<br>
ARIN<br>
<br>
<br>
</div>
</blockquote>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Services-wg mailing list<br>
<a href="mailto:Services-wg@arin.net">Services-wg@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/services-wg" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/<wbr>listinfo/services-wg</a><br>
<br></blockquote></div><br></div>