<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 11, 2011, at 10:16 AM, Stephen Sprunk wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div bgcolor="#ffffff" text="#000000">
On 11-May-11 11:39, Martin Millnert wrote:<br>
<blockquote cite="mid:BANLkTinXfCViH2-3puroCVTCr7ZTqJ4JvQ@mail.gmail.com" type="cite">
<pre wrap="">On Tue, May 10, 2011 at 9:01 PM, Jimmy Hess <a class="moz-txt-link-rfc2396E" href="mailto:mysidia@gmail.com"><mysidia@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I suggest something more like:
The recipient of transferred number resources must sign a standard
Registration Services Agreement made public by ARIN, that ensures ARIN retains the right to charge fees and revoke resources as needed, to enforce number resource policies, or reclaim underutilized resources.
</pre>
</blockquote>
<pre wrap="">I'm admittedly not very experienced in ARIN procedures, so if you would please help me out here:
How does this motivate sellers of legacy space to involve ARIN in their transactions?
</pre>
</blockquote>
<br>
A transferee is very interested in involving ARIN because they want
to make sure the registration database will get updated; if ARIN
refuses to record the transfer because it doesn't comply with
policy, there is no reason to pay because they have received nothing
of value. Therefore, a transferor must involve ARIN because they
need to validate that the transfer will be recorded before they can
get their money.<br>
<br>
Remember, numbers are not property and cannot be sold; what is being
"sold" is a slot in ARIN's database. If you don't care about ARIN's
database, just use whatever numbers you want without paying anyone!<br>
<br>
<blockquote cite="mid:BANLkTinXfCViH2-3puroCVTCr7ZTqJ4JvQ@mail.gmail.com" type="cite">
<pre wrap="">My understanding of the term "legacy space" is that it was assigned to users prior to ARIN's (or others) existence, and that you can't assume there is contracts in place where the legacy space holder in effect converts their space to ARIN managed space (which in practical terms means the space isn't "legacy space" per my definition).
</pre>
</blockquote>
<br>
All resources issued prior to ARIN's formation are legacy,
regardless of whether they are currently covered by an (L)RSA.
However, that's a moot point because the policy doesn't really
affect to the transferor; it only applies to the transferee, who
will be forced to sign some sort of contract for services rendered.<br>
<br>
Note that, while there is no legacy IPv6, there <i>are</i> legacy
ASNs, not just IPv4 space; that's why we use the generic term
"resources". (I'm not aware of anyone wanting to "buy" a legacy
ASN, but in theory it could happen.)<br>
<br></div></blockquote>Not really. Section 8.3 applies only to IPv4 resources.</div><div><br></div><div>Owen</div><div><br></div></body></html>