<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 6/3/2015 3:06 PM, John Curran wrote:<br>
</div>
<blockquote
cite="mid:CA3A6FC5-5DC5-4F5E-A977-E237C370EB6C@corp.arin.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
On Jun 3, 2015, at 5:48 PM, Matthew Kaufman <<a
moz-do-not-send="true" href="mailto:matthew@matthew.at" class="">matthew@matthew.at</a>>
wrote:<br class="">
<div>
<blockquote type="cite" class="">...<br
class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica; font-size:
12px; 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;
float: none; display: inline !important;" class="">You
could certainly argue (and I might) that the records of
legacy assignments were in fact entrusted to ARIN to keep,
and keep updated *whether or not the community drafted
policy that said such updates were disallowed*</span></div>
</blockquote>
</div>
<br class="">
<div class="">Noting just one of the significant problems with
that argument being that at the time </div>
<div class="">of ARIN’s formation, the actual applicable registry
policy was RFC 2050 (having been </div>
<div class="">finished just a year earlier with folks like David
Conrad and Jon Postel as authors) -</div>
</blockquote>
<br>
And strangely after many legacy addresses had already been
allocated.<br>
<br>
<blockquote
cite="mid:CA3A6FC5-5DC5-4F5E-A977-E237C370EB6C@corp.arin.net"
type="cite">
<div class="">it states that those obtaining addresses via
transfer must "meet the same criteria as </div>
<div class="">if they were requesting an IP address directly from
the Internet Registry."</div>
</blockquote>
<br>
Yes, the word "transfer" appears exactly once, and undefined, in
RFC2050.<br>
<br>
The same RFC says that one of the three goals is to "document
address space allocation and assignment" - as it says "this is
necessary to ensure uniqueness and to provide information for
Internet trouble shooting at all levels". It is this latter goal
that will no longer be met if organizations are forced to "transfer"
without "transferring".<br>
<br>
<blockquote
cite="mid:CA3A6FC5-5DC5-4F5E-A977-E237C370EB6C@corp.arin.net"
type="cite">
<div class=""><br class="">
</div>
<div class="">I.E., If we were maintain the exact status quo that
such parties had prior to ARIN’s</div>
<div class="">formation, recognized ARIN is entrusted to maintain
that, then folks probably would</div>
<div class="">not like the result - today’s transfer policy is
more lenient than the transfer policy at </div>
<div class="">that point in time.</div>
<div class=""><br class="">
</div>
</blockquote>
<br>
That's one possible conclusion.<br>
<br>
<blockquote
cite="mid:CA3A6FC5-5DC5-4F5E-A977-E237C370EB6C@corp.arin.net"
type="cite">
<div class="">
</div>
<div class="">(Thank an ARIN Advisory Council member when you next
see them for all of their </div>
<div class="">efforts getting useful transfer policy in the Number
Resource Policy Manual! :-)</div>
<div class=""><br class="">
</div>
</blockquote>
<br>
We'll see.<br>
<br>
Matthew Kaufman<br>
<br>
</body>
</html>