[arin-ppml] ARIN-prop-153 Correct erroneous syntax in NRPM 8.3

Matthew Kaufman matthew at matthew.at
Tue May 31 12:22:32 EDT 2011


On 5/31/2011 5:10 AM, Frank Bulk wrote:
>
> As long as everyone works within the ARIN transfer policy, attaching 
> the limits on the recipients would seem sufficient.
>
>

I disagree... putting limits on the holder of space that prevents them 
from breaking it up too rapidly (and thus creating BGP table growth) is 
fairly easy. Putting limits on the buyer makes the transfer market 
incredibly complex and confusing.

For instance, a buyer who needs a /23 of space might see that there's no 
/23s available but that there are two /24s available. Can they acquire 
those /24s?

Under existing policy the answer is "yes, if they can demonstrate need 
for the /23 of space". Under the various proposed policies the answer is 
"it depends". In some cases it might depend on whether or not ARIN had 
originally allocated either or both of those as /24s. In other cases it 
might depend on whether the two /24s come from the same original block 
that ARIN had allocated. But in no case is the answer simple.

Matthew Kaufman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20110531/04afbca3/attachment.html>


More information about the ARIN-PPML mailing list