[ipv6-wg at ripe.net] Re: IANA to RIR IPv6 Allocation

  I've got one comment here on
  section 7. paragraph 4. "Subsequent Allocation":

  While the wording might be sufficiently clear for a native speaker by
  referring to "set of administrative procedures....", I am missing clear
  guidance for the IANA that there should _not_ be any incentive or
  responsibilty to consult with other groups, entities or third parties
  (irrespective of their, say, credibility for e.g. protocol development
  or technical specifications) which would require extending that 30 day
  period.

  My proposal would be that IANA would have to perform the subsequent
  allocation within this 30 day period, even if they might not be able to
  obtain advice or an expertise (for whatever reason) from any other party
  they might have decided to ask for advice.

  Wilfried                                     ( https://cert.aco.net/ )
 _________________________________:_____________________________________
  Wilfried Woeber                 : e-mail: Woeber at CC.UniVie.ac.at
  UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33
  Universitaetsstrasse 7          : Fax: +43 1 4277 - 9 140
  A-1010 Vienna, Austria, Europe  : RIPE-DB: WW144, PGP keyID 0xF0ACB369
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ...there's no place like 127.0.0.1 (or ::1/128 ?)


From: David Kessens <david.kessens at nokia.com>
To: Jeroen Massar <jeroen at unfix.org>
Date: Fri, 20 Aug 2004 01:48:52 -0700
CC: ipv6-wg at ripe.net
Subject: Re: [ipv6-wg at ripe.net] FW: [arin-council] IANA to RIR IPv6 Allocation


Jeroen,

On Fri, Aug 20, 2004 at 09:25:59AM +0200, Jeroen Massar wrote:
> For people not on the arin-council (not likely ;) or the ppml at arin
> lists:

All policy discussions for the RIPE region are now conducted at the RIPE
policy working group maillist:

address-policy-wg at ripe.net

David Kessens
---

> -----Forwarded Message-----
> From: "Sweeting, John" <John.Sweeting at teleglobe.com>
> To: 'ppml at arin.net' <ppml at arin.net>
> Subject: [ppml] FW: [arin-council] IANA to RIR IPv6 Allocation
> Date: Thu, 19 Aug 2004 17:36:56 -0400
> 
> I am submitting the following proposal IAW ARIN's Internet Resource Policy
> Evaluation Process. In the interest of all I would like to disclose up front
> that the information used to prepare this template was provided by ARIN
> staff. 
> 
> 
> ############################################
> Template: ARIN-POLICY-PROPOSAL-TEMPLATE-1.0
> 
> 1. Policy Proposal Name: Allocation of IPv6 Address Space by the Internet
> Assigned Numbers Authority (IANA) Policy to Regional Internet Registries
> 
> 2. Author
> 
>  a. name: John Sweeting	
>  b. email: john.sweeting at teleglobe.com	
>  c. telephone: 703-766-3042
>  d. organization: ARIN Advisory Council
>  
> 3. Proposal Version: 1
> 
> 4. Submission Date: 8/17/04
> 
> 5. Proposal type: new, global
> 
> 6. Policy term: permanent
> 
> 7. Policy statement:
> 
> 1.  Minimum Allocation Size.
> 
> The minimum size of any allocation of IPv6 address space from IANA to an RIR
> is prefix length /12.  If this address space is not sufficient to meet the
> needs of an RIR for a projected 18 month period, IANA shall allocate to that
> RIR the address space for which it can provide justification.
> 
> 2.  Reservation of Unicast Address space.
> 
> 2.1 IANA.  By RFC 3513 the IANA has been allocated the range of IPv6
> addresses beginning at binary value 001 (prefix length /3) for its
> allocations of unicast address space.  In order to support regional
> aggregation of IPv6 address space IANA shall establish a reservation of a
> prefix length of /6 from this space for each established RIR and for each
> emerging RIR.  Allocations to each RIR will be from the appropriate
> reservation.
> 
> 2.2. RIRs.  Each RIR may apply its own respective chosen allocation and
> reservation strategy in order to meet the needs of its community and to
> ensure the efficiency and efficacy of its work.  Such reservations made by
> an RIR will be considered as being allocated by that RIR when that RIR
> applies for an allocation of address space from the IANA.
> 
> 3.  Initial Allocation.
> 
> 3.1. Upon implementation of this policy IANA shall allocate to each
> established RIR a /12 from the reservation established for each particular
> RIR.
> 
> 3.2. Upon recognition of an RIR by ICANN that RIR shall receive a /12 from
> the reservation set aside for that RIR.
> 
> 
> 4.  Subsequent Allocation.
> 
> An RIR shall be eligible for an allocation of at least a minimal allocation
> from the IANA when its current holdings are less than 50% of its 18 month
> requirement or when it has less than 180 days of holdings available.  The
> IANA shall evaluate the requested allocation using a set of administrative
> procedures that are mutually agreed to by the IANA and the NRO.  This set of
> procedures shall be enacted within 30 days of the implentation of this
> policy.
> 
> 
> 5.  Announcement of IANA allocations to the RIRs
> 
> When address space is allocated to a RIR, the IANA will send a detailed
> announcement to the receiving RIR. The IANA will also make announcements to
> all other RIRs, informing them of the recent allocation.
> 
> The IANA will make appropriate modifications to the "Internet Protocol V6
> Address Space" page of the IANA website and may make announcements to only
> its own global announcement lists.  The IANA announcements will be limited
> to which address ranges, the time of allocation and to which Registry they
> have been allocated.
> 
> 
> 8. Rationale:
> 
> The current IANA allocation policy for IPv6 is an interim policy that was
> promulgated in 1999.  Operational experience has demonstrated the current
> minimum allocation size is too small; that the built in reservation system
> that must be followed by the RIRs does not allow for efficient and effective
> management of the resource by the RIR; and does not provide for an well
> known evaluation criteria.  This document does not stipulate performance
> requirements in the provision of services by IANA to an RIR in accordance
> with the policy.  Such requirements should be specified by appropriate
> agreements between the NRO and ICANN.
> 
> 
> 9. Timetable for implementation: Thirty days after ratification by the ICANN
> Board of Directors in accordance with the global policy development process

_______________________________________________