[arin-ppml] Draft Policy 2011-9 (Global Proposal): Global Policy for post exhaustion IPv4 allocation mechanisms by the IANA

[David Farmer]

This is related to ARIN-2011-9 and was intended to go to PPML originally.

-------- Original Message --------
Subject: Re: [address-policy-wg] IANA implementation analysis of 
proposal 2011-01, "Global Policy Proposal for Post Exhaustion IPv4 
Allocation Mechanisms by IANA"
Date: Mon, 19 Sep 2011 00:07:57 -0700
From: S Moonesamy <sm+afrinic at elandsys.com>
To: address-policy-wg at ripe.net
CC: Philip Smith <pfsinoz at gmail.com>,    Alejandro Acosta 
<alejandro.acosta at bt.com>,    sig-policy at lists.apnic.net,    Masato 
Yamanishi <myamanis at bb.softbank.co.jp>,    Nicolas Antoniello 
<nantoniello at gmail.com>,    rpd at afrinic.net,    politicas at lacnic.net, 
  Douglas Onyango <ondouglas at yahoo.com>,    "GT RAMIREZ, Medel G." 
<medel at globetel.com.ph>,    arin-ppml at arin.net

At 06:08 05-08-2011, Emilio Madaio wrote:
>In order to provide a more comprehensive overview of the expected
>implementation aspects of proposal 2011-01, the RIPE NCC sought input
>from IANA staff.
>
>Below is the analysis produced by Leo Vegoda. We hope that this input
>will be useful to RIPE community discussion of this proposal.

[snip]

>IANA staff impact analysis of RIPE policy proposal 2011-01
>
>This analysis considers the impact of ratification of RIPE policy
>proposal 2011-01 (as a part of GPP-IPv4-2011) by the ICANN Board of Directors.
>
>1. The policy would require ICANN, as the IANA function operator, to
>establish a Recovered IPv4 Pool. The pool would have to include "any
>fragments that may be left over in the IANA".  In order to do this,
>ICANN staff would have to work closely with the five RIRs' staffs to
>make sure the initial pool included all fragments assigned to IANA.
>It is not clear whether this policy proposal is intended to
>supersede the IETF's right to make IPv4 assignments for "specialised
>address blocks (such as multicast or anycast blocks)" as documented
>in section 4.3 of RFC 2860. This should be clarified but that can
>probably be done by way of assertions from the NRO rather than a
>revision to the policy text. In the event that the policy is
>intended to supersede RFC 2860 there is a potential issue with the
>internal reservation of small blocks address blocks that have been
>informally reserved for IETF standards track work currently in progress.

The authors of proposal 2011-01 (GPP-IPv4-2011) do not intend to take
over the IETF's
role in assigning internet resources.

The IANA Staff analysis asks for an assertion from the NRO instead of
a revision to the policy text.  During discussions with the ARIN
Advisory Council, it was mentioned that the clarification requires a
text change to the proposal.  It was also mentioned that the ASO,
instead of the NRO, must provide the clarification.  To avoid any
doubt, the authors of the proposal would appreciate if the ASO or the
NRO, whichever is the appropriate party, can clarify that.

Regards,
S. Moonesamy



-- 
===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota	
2218 University Ave SE	    Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================