<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;">
On Feb 15, 2014, at 10:10 AM, Steven Ryerse <<a href="mailto:SRyerse@eclipse-networks.com">SRyerse@eclipse-networks.com</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="auto" style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div>But real life is that short of congress acting, unless you have 100% of all the large block holders it will never happen. Therefore the prudent action is to accept reality. Ripe 605 does just that. <br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Steve -</div>
<div><br>
</div>
<div> It is quite likely that normal market dynamics over time will result in many of </div>
<div> the underutilized address blocks being transferred and ending up under an </div>
<div> agreement (in ARIN or another region) - that's precisely what Keith was </div>
<div> noting in his posting.</div>
<div><br>
</div>
<div> Furthermore, 100% is not necessary and may not be desired by some parties,</div>
<div> since many legacy address holders probably just want to have their registration </div>
<div> services and be otherwise undisturbed. Note that Ripe-605 doesn't actually </div>
<div> change anything in that respect, in fact, it parallels ARIN's existing practices </div>
<div> for those without formal agreement - </div>
<div><br>
</div>
<div>From <<a href="http://www.ripe.net/ripe/docs/ripe-605">http://www.ripe.net/ripe/docs/ripe-605</a>> - </div>
<div><br>
</div>
<div>"2.6 No relationship</div>
In case no formal relationship has been established in support of a particular legacy resource, the RIPE NCC<br>
<br>
<div><span class="Apple-tab-span" style="white-space:pre"></span>• will continue to provide any registry service element already provided in support of each Legacy Internet Resource involved;<br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>• will have no obligation to begin to provide any registry service element not already provided in support of a particular Legacy Internet Resource, even in case the service element is provided
in support of any other Legacy Internet Resource held by the same or another Resource Holder;<br>
</div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>• and may update the related entries in the RIPE Database from time to time to correspond to the current actual situation."</div>
<div><br>
</div>
<div> It would be most helpful if you could fully explain the problem you are trying to</div>
<div> solve, and then which section of RIPE 605 addresses it. Simply indicating that </div>
<div> it is prudent (because of lack of 100% LRSA adoption) does not explain why.</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>
<div><br>
</div>
<div><br>
</div>
</div>
</body>
</html>