<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Jun 5, 2012, at 12:06 PM, Lindsey, Marc wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 15px; ">A
legacy resource is an IPv4 address or Autonomous System Number that (a) was issued to an entity (other than a Regional Internet Registry) or individual (the “original legacy holder”) prior to ARIN's inception on Dec 22, 1997 either by an organization authorized
by the United States to perform the Internet Assigned Numbers Authority (“IANA”) functions or an Internet Registry, and (b) has not been returned to<span class="Apple-converted-space"> </span><span style="color: black; ">a</span><span class="Apple-converted-space"> </span>Regional
Internet Registry under a binding written agreement between the original legacy holder (or its legal successor or assign)<span class="Apple-converted-space"> </span><span style="color: black; ">and the RIR<span class="Apple-converted-space"> </span></span>for
subsequent allocation<span style="color: black; ">and assignment</span><span class="Apple-converted-space"> </span>in accordance<span class="Apple-converted-space"> </span><span style="color: black; ">with<span class="Apple-converted-space"> </span></span>such
RIR’s number resource policies<span style="color: black; "><span class="Apple-converted-space"> </span>and membership (or service) agreements</span>.</span></span></blockquote>
</div>
<br>
<div>Marc - </div>
<div> </div>
<div> The existing NRPM does not qualify the nature of transactions such as</div>
<div> you propose in (b), i.e. "a binding written agreement", and yet we have</div>
<div> had numerous resources returned over the years through requests of </div>
<div> various forms (including email, in-person, fax, telephone and online),</div>
<div> so your proposed definition has potential creates significant uncertainty</div>
<div> for past resource transactions already completed. </div>
<div> </div>
<div> I would therefore recommend that if section b is included, it simpler to</div>
<div> go with a basic definition which states "and (b) for which the entity is</div>
<div> still the registered address holder."</div>
<div><br>
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
</body>
</html>