<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 28 Mar 2017, at 8:04 PM, Steve Noble <<a href="mailto:snoble@sonn.com" class="">snoble@sonn.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div dir="auto" class="">Hi John, <br class="">
<div class="gmail_extra" dir="auto"><br class="">
<div class="gmail_quote">On Mar 28, 2017 3:22 PM, "John Curran" <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:<br type="attribution" class="">
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="quoted-text"> <br class="">
<br class="">
</div>
Steve -<br class="">
<br class="">
If we do not lock the resources but do add the old network Admin/Tech contact info to<br class="">
the organization record, then a very large number of these blocks have the potential to<br class="">
be readily hijacked – one simply would have to register the domain name and setup<br class="">
email for any defunct organization, and you could readily transfer the addresses<br class="">
(despite having no association whatsoever with the original registrant…)<br class="">
<br class="">
Some in the community would view that consequence as an unacceptable tradeoff –<br class="">
what is your thoughts on it?<br class="">
<br class="">
</blockquote>
</div>
</div>
<div class="gmail_extra" dir="auto">I think it is logical to lock ones where the original domain does not exist or was registered after the object. Then I understand a more extensive vetting process. </div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">My issue is with cases like mine where everything was in order. </div>
</div>
</div>
</blockquote>
<div class="">
<div dir="auto" class="">
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">Steve - </div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">Acknowledged, and thanks for the excellent feedback. </div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">Given that all of these organization records are currently subject to vetting (and</div>
<div class="gmail_extra" dir="auto">would remain so under the proposed change to put the Tech and Admin contacts</div>
<div class="gmail_extra" dir="auto">onto the Org record), it would be helpful to get some additional feedback from you.</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">If the vetting scope is not changed per the proposed change to the registry that is now </div>
<div class="gmail_extra" dir="auto">under consultation, would you prefer that the registry remain as-is, or that we proceed </div>
<div class="gmail_extra" dir="auto">with putting the original network Tech and Admin contacts on the Org records as </div>
<div class="gmail_extra" dir="auto">proposed?</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">Thanks!</div>
<div class="gmail_extra" dir="auto">/John</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto">John Curran</div>
<div class="gmail_extra" dir="auto">President and CEO</div>
<div class="gmail_extra" dir="auto">ARIN</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto"><br class="">
</div>
<div class="gmail_extra" dir="auto"> </div>
</div>
</div>
</div>
</body>
</html>