[ipv6-wg@ripe.net] FW: [arin-council] IANA to RIR IPv6 Allocation
For people not on the arin-council (not likely ;) or the ppml@arin lists: -----Forwarded Message----- From: "Sweeting, John" <John.Sweeting@teleglobe.com> To: 'ppml@arin.net' <ppml@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@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. 10. Meeting presenter: Elected AC Member or the President of ARIN. END OF TEMPLATE ################################################
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@arin lists:
All policy discussions for the RIPE region are now conducted at the RIPE policy working group maillist: address-policy-wg@ripe.net David Kessens ---
-----Forwarded Message----- From: "Sweeting, John" <John.Sweeting@teleglobe.com> To: 'ppml@arin.net' <ppml@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@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
Hi Jeroen, Was there a discussion of /8 vs /12? Tim 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@arin lists:
-----Forwarded Message----- From: "Sweeting, John" <John.Sweeting@teleglobe.com> To: 'ppml@arin.net' <ppml@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@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.
10. Meeting presenter: Elected AC Member or the President of ARIN.
END OF TEMPLATE ################################################
On Fri, 2004-08-20 at 12:38, Tim Chown wrote:
Hi Jeroen,
Was there a discussion of /8 vs /12?
Nope, that was on the address-wg@ripe and partially on the ipv6-wg@ripe lists. This is an announcement out of the of the blue from the arin side, I guess there has been discussion on arin-council, but that is afaik a closed list. ppml is the public policy mailing list, which indicates already that arin does things behind closed doors ;) Btw check the following url for the archives: http://www.arin.net/mailing_lists/ppml/index.html Greets, Jeroen
Jeroen, Before you comments about the ARIN policy process I suggest you read: http://www.arin.net/policy/ipep.html I think you will find two things that are immediately clear to even the casual observer: 1. This statement on the ppml is just the beginning of the process. It was posted by a member of the ARIN AC as an individual member and does not represent any discussion by the AC in regards to this policy. At this point it is not even a formal policy proposal that will be taken up for discussion at the ARIN meeting in Reston in October. 2. The next step in the process is for this proposal and any others to be discussed by the AC as described in the policy proposal document. I will not go any further in describing the process as it is available for your reading at the url I provided. Again I suggest you read it and I would be glad to know how this process does not promote an open discussion on any policy in the ARIN region. Your specific comments will be most welcome. Lastly, I invite you to participate in the discussion on the ARIN ppml. Your participation and that of anyone, anywhere in the world is most welcome. One does not need to be a member of ARIN to participate. Of course the ARIN meeting is an open meeting. It is open to anyone in the world who wishes to participate in the policy process. Ray
-----Original Message----- From: ipv6-wg-admin@ripe.net [mailto:ipv6-wg-admin@ripe.net] On Behalf Of Jeroen Massar Sent: Friday, August 20, 2004 7:07 AM To: Tim Chown Cc: ipv6-wg@ripe.net Subject: Re: [ipv6-wg@ripe.net] FW: [arin-council] IANA to RIR IPv6Allocation
On Fri, 2004-08-20 at 12:38, Tim Chown wrote:
Hi Jeroen,
Was there a discussion of /8 vs /12?
Nope, that was on the address-wg@ripe and partially on the ipv6-wg@ripe lists. This is an announcement out of the of the blue from the arin side, I guess there has been discussion on arin-council, but that is afaik a closed list. ppml is the public policy mailing list, which indicates already that arin does things behind closed doors ;)
Btw check the following url for the archives: http://www.arin.net/mailing_lists/ppml/index.html
Greets, Jeroen
On Fri, 2004-08-20 at 13:41, Ray Plzak wrote:
Jeroen,
Before you comments about the ARIN policy process I suggest you read: http://www.arin.net/policy/ipep.html
As I mentioned in the mail, I made an assumption based on the fact that the original post was already a forward from a closed list. Everywhere things happen behind closed doors and then come forward. If everything was discussed in public the latency of things would be even bigger. The policy outlined above is fine by me ;) <SNIP>
Lastly, I invite you to participate in the discussion on the ARIN ppml. Your participation and that of anyone, anywhere in the world is most welcome. One does not need to be a member of ARIN to participate. Of course the ARIN meeting is an open meeting. It is open to anyone in the world who wishes to participate in the policy process.
Which is why I forwarded the message to the ipv6-wg@ripe list so that people not following the ppml@arin list know that in the ARIN region action was being taken to get forward with the proposals. Greets, Jeroen
participants (4)
-
David Kessens -
Jeroen Massar -
Ray Plzak -
Tim Chown