[arin-ppml] Revisiting Section 4.4 Micro allocations for C/I

Martin Hannigan hannigan at gmail.com
Wed Jun 27 07:37:20 EDT 2012


PPML:

At the time that we implemented the last Section 4.4 revisions, we
created a reserve pool (/16) for CI.  We had anticipated that some v4
would be needed post exhaustion for the various CI needs and the new
GTLD process underway at ICANN. What we didn't anticipate was the
relative "success" of that process which has resulted in an ask for
1930 new top level names across the five regions.

The way it affects this region is that there are 911 requests for new
entries in the root here:

    http://newgtlds.icann.org/en/program-status/statistics

There aren't going to be 911 successes. The estimate that I hear is
likely is 600 to 700. Assuming an assignment of a /24, we don't have
enough in the pool to serve the ones specific to this region (along
with the IX's)

We need to increase the pool to a /14 and make the term permanent. I
picked a /14 based on a worst case scenario of a /23 each and
including new IX deployments which I think are probably going to be
miniscule in North America as compared to new gTLD's.


Para 2 existing:

ARIN will place an equivalent of a /16 of IPv4 address space in a
reserve for Critical Infrastructure, as defined in section 4.4. If at
the end of the policy term there is unused address space remaining in
this pool, ARIN staff is authorized to utilize this space in a manner
consistent with community expectations.

Suggested Para 2 edited:

ARIN will place an equivalent of a /14 of IPv4 address space in a
reserve for Critical Infrastructure, as defined in section 4.4.

Thoughts?


Best,


-M<



More information about the ARIN-PPML mailing list