<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi<br>
</p>
<p>Thanks for the history and better clarification. However it is
not still clear to me if ARIN can, at some point and under which
conditions recover these legacy blocks which look abandoned and
have zero signal of being used or have some organization looking
after it, and send to be re-assigned to the waiting list.<br>
</p>
<p>I agree with some of the messages that is not reasonable to think
that after all this time some organizations may be unaware of what
is happening that justifies to keep having special treatment. 25
years is quiet a while ! Legacy Resources has always been an issue
in different aspects and there should have been more stuff done to
avoid certain controversies where possible overtime. I personally
don't have a problem with them keeping the resources as long they
have justification of need and not just based on "acquired
rights".<br>
</p>
<p>If I understand it correctly it is possible to advance further in
this specific matter without a need for the community to produce
and agree in a new policy, so what prevents this from happening ?
Are there any major legal risks or is it just extra patience with
those who don't seem to want to cooperate in a well established
system for the past decades ?</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 14/04/2022 11:50, John Curran wrote:<br>
</div>
<blockquote type="cite"
cite="mid:61F9DC53-10E5-429E-B0C2-85658DC5F665@arin.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Folks -
<div class=""><br class="">
</div>
<div class="">I have some good news and some bad news… The good
news is that the history of the Internet number registry system
is actually fairly well-known
<span style="font-size: 11px;" class="">– for instance,</span> we
know the parties that were involved and have many examples of
the emails that were sent when number resources were issued –
whether it was done by SRI, GSI, NSI as InterNIC, NSI directly,
etc. (This shouldn’t be unexpected, since NSI transferred the
personnel, systems, and records from IP number registry to ARIN
at the time of our formation.)</div>
<div class=""><br class="">
</div>
<div class="">The bad news is that such communications were
written to be expeditious in the administration of the registry,
as opposed to being written with legal clarity. As a simple
example of that fact, consider that the term "IP address block”
– the "thing" being issued – was actually not defined in any of
these communications. As a result of the nature of these early
communications, there’s enough ambiguity to support differences
in opinion over the nature of the legacy address assignments in
the registry. </div>
<div class=""><br class="">
</div>
<div class="">However, there are a few points in the history of
the registry that are quite clear, and these include:</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">ARIN was formed for the purpose of administration
of the registry in North America and took over that
responsibility at the time of our formation – including the
transfer of the registry database to ARIN at USG direction. </li>
<li class="">ARIN’s administration of the registry is be
performed in accordance with our community-developed
policies – and we are aware of no obligations that prevent
ARIN from doing so for all number resources in the registry,
including legacy resources. </li>
<li class="">Those with legacy number resources are encouraged
to participate in the open policy process so as to have
a voice in the policies by which they are managed – such
participation doesn’t require any agreement with ARIN and is
actually a significant part of why ARIN was formed -
“Creation of ARIN will give the users of IP numbers (mostly
Internet service providers, corporations and other large
institutions) a voice in the policies by which they are
managed and allocated within the North American region.”
<<a
href="https://www.nsf.gov/news/news_summ.jsp?cntn_id=102819"
class="moz-txt-link-freetext" moz-do-not-send="true">https://www.nsf.gov/news/news_summ.jsp?cntn_id=102819</a>></li>
</ol>
<div class=""><br class="">
</div>
</div>
<div class="">This is why organizations with legacy number
resources are encouraged to participate in ARIN’s policy
development process – ARIN was specifically formed so that they
would have a voice in the policies used in the management of
those number resources, and hence why ARIN routinely reiterates
that legacy number resources are indeed subject to ARIN's
registry policies. (The community can certainly make policies
that exclude legacy number resources or affect them in a
different manner, but again, that is for the community to
decide…)</div>
<div class=""> </div>
<div class="">Thanks! </div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</body>
</html>