[arin-ppml] On IPv4 free pool runout and transfer policy requirements for the ARIN region
John Curran
jcurran at arin.net
Fri Jun 5 13:06:20 EDT 2015
On Jun 5, 2015, at 12:52 PM, William Herrin <bill at herrin.us> wrote:
> Reciprocity. It must not be practical to transfer addresses to a
> registry where registrants of record are not permitted to transfer
> addresses from the registry. Not just directly but through
> second-order activity too. E.g. I would disallow ARIN->APNIC absent a
> commitment from APNIC to disallow a subsequent APNIC->CNNIC activity
> due to CNNIC disallowing all out-transfers.
Can you explain what the underlying requirement that is satisfied by having
such a criteria in the transfer policy? Given that regions came about out of
administrative convenience and efficiency in distribution, it is interesting to
see them take on significant meaning in a post-allocation environment...
> BGP protectionism. The Internet BGP table is somewhat fragile. The
> problem is exacerbated by a tragedy of the commons problem comprised
> of the lack of any practical way to exact payment for the routes in
> the local BGP table from the organization which first announced those
> routes into the BGP system. To whatever extent practical, transfers
> should avoid inducing or requiring further fragmentation in the myriad
> routing tables that comprise that very expensive system.
>
> I'm not convinced about having hard policy for minimum transfer sizes.
> I think that could be better managed as an ARIN business matter by
> requiring anyone requesting an unusually small transfer to sign a
> letter to the effect that, "Undersigned registrant acknowledges that
> address blocks smaller than /24, including the requested block, are
> ordinarily _not usable_ on the public Internet. Registrant requests
> transfer despite said impairment.”
Is /25 "unusually small”? If smaller than /24 are allowed at all, they may
become rather popular in the near future (i.e. at the point in time when
ISPs will no longer provide static addresses to new business customers)
/John
John Curran
President and CEO
ARIN
More information about the ARIN-PPML
mailing list