<div dir="ltr"><div class="gmail_default" style="font-size:small">See inline comment.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">--<br>Brian</div></div>
<br><div class="gmail_quote">On Mon, Oct 5, 2015 at 4:40 PM, John Curran <span dir="ltr"><<a href="mailto:jcurran@arin.net" target="_blank">jcurran@arin.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Oct 5, 2015, at 4:07 PM, Martin Hannigan <<a href="mailto:hannigan@gmail.com">hannigan@gmail.com</a>> wrote:<br>
><br>
> Let me give you a real world example.<br>
><br>
> 1. Buy rights to use addresses in any quantity you believe you need<br>
> 2. Use those addresses as you need them, assuming the agreement you made with the party works properly<br>
> 3. Get an LOA from the documented owner<br>
> 4. Bypass ARIN entirely<br>
> 5. Use the addresses.<br>
><br>
> How do you think we should solve that problem?<br>
<br>
<br>
</span>It is not my job to determine whether the example above is a major problem (or not) -<br>
that’s for the community to assess, but I do want to highlight some aspects that result<br>
from situations (such as the one described above) of which everyone on the list might<br>
not be aware -<br>
<br>
1) While the network operations confusion that can result is fairly well understood to<br>
those on this list, what may not be apparently is that there are others who rely upon<br>
the registry (e.g. researchers, anti-spam folks, law enforcement, etc.) and for whom<br>
address blocks being used as described above results in real impacts to their ability<br>
to rely upon the registry, and thus accomplish their job.<br>
<br>
2) Because the “documented owner” doesn’t ever update the registry, a number of<br>
creative schemes are possible whereby the documented owner gets paid from<br>
multiple parties for the same rights and then effectively disappears with their<br>
proceeds leaving the individual buyers to fight it out. There are ways to reduce<br>
this risk (e.g. escrow arrangements, guarantees with adequate backing, etc.)<br>
but the need for these (and probability of circumvention) goes up dramatically<br>
absent an updated registry. Likewise for the case where the “documented<br>
owner” doesn’t actually have a documentation trail that would support their<br>
ability to sell the rights to even one party, but that is not uncovered since the<br>
documentation never gets reviewed by the registry.<br></blockquote><div><br><div class="gmail_default" style="font-size:small">Number 2 here is the crux of the matter IMHO. In this case the registry not getting updated could cause Internet routing issues, and may not get discovered until routing advertisements for the addresses starts being announced from multiple sources. There is a need for central registration of addresses regardless. I think the entire reasoning for 2015-7 is to simplify the needs assessment process in order to maintain an accurate registry of IPv4 addresses. How do we do that otherwise?<br></div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I have not seen a clear expression of these cases on the list, and felt it important<br>
to describe them for those who may not have first hand involvement. It is true that<br>
under 2015-7, parties would be able to obtain more address space then presently<br>
allowed and to so do based upon an officer representation, so the risks that such<br>
a change would bring about should be carefully weighted by the community against<br>
the situations outlined above which exist under the status quo.<br>
<br>
Thanks,<br>
/John<br>
<span class="HOEnZb"><font color="#888888"><br>
John Curran<br>
President and CEO<br>
ARIN<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div></div></blockquote></div><br></div></div>