Re: [IANAxfer@apnic] Key elements of the transition of IANA stewardship
On Sep 12, 2014, at 6:46 AM, Avri Doria <avri@acm.org> wrote:
> Both of the contentful, if somewhat derisive, answers sort of skirted
> the questions by telling me anyone can use any numbers they want. I
> am asking about whether they can register numbers that are within the
> current set of number that IANA + the RIRs call the Internet (using
> legacy v4 and not yet assigned v6 allocations) . Not a separate
> private net of some sort. That is well known.
Avri -
The IETF specifies protocols, and sometimes a protocol will need a
set of unique identifiers. When that is the case, the IETF includes
an "IANA Considerations" section in the specification, so that the
IANA will create and administer a registry for identifiers of that
type. The IETF also arranges for an IANA operator to follow such
instructions. This is all very nice of the IETF and it makes their
protocol specifications more useable since there is (by default)
a commonly recognized registry of values. You can read all about
IANA Considerations sections in RFC 5226 (aka IETF BCP 24). When
it comes to registries which pose "policy issues" (e.g. DNS root,
IP addresses), the IETF has recognized that there will be addition
policies set by the affected community to address such policy issues,
and that the IANA will follow those policies to the extent that they
do not conflict IETF's technical requirements for the same registries.
(This is all well documented in the ICANN/IETF MOU, i.e. RFC 2860)
For their part, the RIRs agreed at ICANN's formation to work with
ICANN for the creation of global address policies, and agreed on
a global policy development process with ICANN which utilizes the
regional RIR policy development processes as globally coordinated
by a ASO Advisory Council which has predominantly community-elected
members. These global address policy proposals, once the materially
same text is approved in each region, is sent to the ICANN Board for
review and ratification. All of this is spelt out in the ICANN/ASO
and ICANN/NRO agreements available on the ICANN, ASO, and NRO websites.
> I find the answer that if you prove you need them then IANA will give
> the v6 addresses interesting.
The IANA follows IETF guidance with respect to technical requirements
for every registry, and additionally follows ratified global address
policy (developed per the global development process described above)
for administration of the IPv4, IPv6, and ASN registries. IETF RFC 7249
documents the present IANA number resource registries and source of
policy for each.
The Global Policy for IPv6 allocation is online at the ICANN web site
<https://www.icann.org/resources/pages/allocation-ipv6-rirs-2012-02-25-en>
and it provides for IANA to make allocations to RIRs such that each RIR
can meet its need for allocations within its region for the next 18 months.
Other global policies for IPv6 distribution are possible, but would need
to be developed and approved by the community in all 5 regions in order
to be ratified by the ICANN Board and then implemented by the IANA.
The RIRs and IANA implement a single unique Internet number registry
for each of the IPv4, IPv6, and ASN spaces; each of these spaces contains
IETF technical/reserved assignments for various protocol needs and more
"general purpose" assignments in accordance with the global and regional
policies as developed by the community. There is significant value in the
IETF arranging for administration of a single coordinated IANA registry for
each of these protocol spaces, but as noted earlier, that does not preclude
their protocols from working with privately-coordinated identifiers for
those who so choose.
Thanks!
/John
John Curran
President and CEO
ARIN