sig-policy June 2010

sig-policy@lists.apnic.net

6 participants
6 discussions

Question on difference between v4 and v6 policy
by Jay Daley 06 Jul '10

06 Jul '10

Hello All I was hoping someone might be able to explain the following paragraph from the IPv6 allocation policy [1], section 5.5.1: >> RIRs/NIRs are not concerned about which address size an LIR/ISP actually assigns. Accordingly, RIRs/NIRs will not request the detailed information on IPv6 user networks as they did in IPv4, except for the cases described in Section 4.4 and for the purposes of measuring utilization as defined in this document. My first problem is that I am not clear on what is the detailed information that is not being requested. I assume it is that specified in 10.4 of the IPv4 allocation policy [2], which is basically the details of whom the assignment is made to but any confirmation would be welcome. My second problem, if I've understood the paragraph correctly, is that the reasoning does not make sense, leading me to doubt my understanding. As far as I can tell the leap from "we don't know what size you will choose to assign" to "so we won't ask for any data on who the assignment is to" is a complete non sequitur. Have I missed something? thanks in advance Jay [1] http://www.apnic.net/policy/ipv6-address-policy [2] http://www.apnic.net/policy/add-manage-policy -- Jay Daley Chief Executive .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 931 6977 mobile: +64 21 678840

2 5

Monthly List Reminder
by noreply＠apnic.net 30 Jun '10

30 Jun '10

Dear Subscriber, This is the monthly reminder of subscription information for the sig-policy list, hosted at APNIC. For subscription information including how to un-subscribe go to http://mailman.apnic.net/mailman/listinfo/sig-policy Thank you for participating in this discussion. Kind Regards, List administrator

1 0

(no subject)
by Imtiaz Sajid 16 Jun '10

16 Jun '10

BR, ----- Imtiaz Sajid AM Capacity Planning [cid:image001.jpg@01CB0D38.5B0D9EA0] P: +92-51-2814031-9 Ext: 6761 | C: +92-302 8549698 | F: +92 51-2814024 E: imtiaz.sajid(a)pk.link.net<mailto:imtiaz.sajid@pk.link.net> | W: www.link.net.pk<http://www.link.net.pk/> A: Baverly Center, F-6, Blue Area, Islamabad-Pakistan ________________________________ This e-mail communication and any attachments thereto contain information which is confidential and are intended only for the use of the individuals or entities named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of these documents is strictly prohibited and may be illegal. Please notify us of your receipt of this e-mail in error and delete the e-mail and any copies of it.

1 0

Re: [sig-policy] Global Policy for IPv4 Allocations by the IANA Post Exhaustion (Version 2)
by Louis Lee 08 Jun '10

08 Jun '10

On Sun, Jun 06, 2010 at 08:30:47PM -0700, Terence Zhang YH(CNNIC) wrote: > Thank you for sending the draft out, it's important to set up a > reclamation pool and relevant policy. Thank you, Terence. I am glad that you think so. > I may be out of the loop for a while, I am just wondering, Is > this global policy proposal related to APNIC policy proposal > " prop-069 Global policy proposal for the allocation of IPv4 > blocks to Regional Internet Registries " ? It is. Since the version that the ARIN region has passed is likely to be interpreted to be substantially different from the version that has already been endorsed by the APNIC EC and in other regions, the authors of this new proposal draft feel that prop-069 will fail as a global policy that can be passed onto the ICANN Board of Directors for ratification. Best regards, Louie -- Louis Lee Sr. Network Architect Equinix, Inc. ref: http://www.apnic.net/policy/proposals/prop-069 > ----- Original Message ----- > From: "Louis Lee" <louie(a)equinix.com> > To: "Policy SIG" <sig-policy(a)apnic.net> > Sent: Saturday, June 05, 2010 8:57 AM > Subject: [sig-policy] Global Policy for IPv4 Allocations by the IANA Post Exhaustion (Version 2) > > > > Global Policy for IPv4 Allocations by the IANA Post > > Exhaustion > > > > Rationale: > > > > This policy defines the process for the allocation of IPv4 > > addresses post "Exhaustion Phase"[1]. In order to fulfill > > the requirements of this policy, the IANA must set up a > > reclamation pool to hold addresses in and distribute from > > in compliance with this policy. This policy establishes > > the process by which IPv4 addresses can be returned to and > > re-issued from the IANA post Exhaustion Phase. [snipped]

1 0

Re: [sig-policy] Global Policy for IPv4 Allocations by the IANA PostExhaustion (Version 2)
by Terence Zhang YH(CNNIC) 07 Jun '10

07 Jun '10

Louis, Thank you for sending the draft out, it's important to set up a reclamation pool and relevant policy. I may be out of the loop for a while, I am just wondering, Is this global policy proposal related to APNIC policy proposal " prop-069 Global policy proposal for the allocation of IPv4 blocks to Regional Internet Registries " ? Regards Terence Zhang CNNIC ----- Original Message ----- From: "Louis Lee" <louie(a)equinix.com> To: "Policy SIG" <sig-policy(a)apnic.net> Sent: Saturday, June 05, 2010 8:57 AM Subject: [sig-policy] Global Policy for IPv4 Allocations by the IANA PostExhaustion (Version 2) > Dear esteemed colleagues of the IP addressing community of > the APNIC region, > > If I may introduce myself to those of you who are not > acquainted with me, my name is Louie Lee, and I am the > senior network architect at Equinix US. Many of you > also know me from my work in the addressing community > as the Chair of the ASO Address Council since I have > attended several APNIC meetings. Many more of you are > well acquainted with Dr. Kenny Huang, who is an APNIC > representative to the ASO AC.. > > Kenny is co-sponsoring a global policy proposal with me and > several others in the global addressing community. I am > presenting the DRAFT TEXT of the policy proposal to your > community below in the hopes that you would provide public > and private comments. Near identical drafts are being > presented to the policy mailing lists in the other regions. > The goal is to try to produce a global policy proposal that > would not require substantial changes after it is formally > submitted for consideration in all 5 RIR regions. > > Your feedback would be greatly appreciated. > > Best regards, > Louie > -- > Louis Lee > Sr. Network Architect > New Service Development > Equinix, Inc. > louie(a)equinix.com > > > Global Policy for IPv4 Allocations by the IANA Post Exhaustion > > Rationale: > > This policy defines the process for the allocation of IPv4 > addresses post "Exhaustion Phase"[1]. In order to fulfill > the requirements of this policy, the IANA must set up a > reclamation pool to hold addresses in and distribute from > in compliance with this policy. This policy establishes > the process by which IPv4 addresses can be returned to and > re-issued from the IANA post Exhaustion Phase. > > The intent of this policy is as follows: > > * Includes all post Exhaustion Phase address space returned > to the IANA. > > * Allows allocations by the IANA from the Reclamation Pool > once the Exhaustion Phase has been completed. > > * Defines "need" as the basis for further IPv4 allocations > by the IANA. > > * Does not differentiate any class of IPv4 address space > unless defined by RFC 1918. > > * Encourages the return of IPv4 address space by making this > re-allocation process available. > > * Disallows transfers of addresses sourced from the > Reclamation Pool in the absence of an IPV4 Global Transfer > Policy to neutralize transfer process inequities across RIR > regions. > > * Applies to legacy IPv4 Address Space initially allocated > by the IANA to users including the allocations to RIRs. > > * Includes any length of fragments currently held by the > IANA now or in the future. > > 1. Reclamation Pool > > Upon adoption of this IPv4 address policy by the ICANN > Board of Directors, the IANA shall establish a Reclamation > Pool to be utilized post RIR IPv4 exhaustion as defined in > Section 5. As soon as the first RIR exhausts its inventory > of IP address space, this Reclamation Pool will be declared > active. > > 2. Returning Address Space to the IANA > > The IANA will accept into the Reclamation Pool all eligible > IPv4 address space that is offerred for return. Eligible > address space includes any addresses not previously > designated for special use by an IETF published RFC > explicitly offerred for return to the IANA by: > > a) The RIR to which the space is assigned > > b) The registrant of record where no RIR holds authority > > 3. Address Allocations from the Reclamation Pool by the IANA > > Allocations from the Reclamation Pool may begin once the > pool is declared active. Aggregates in the Reclamation Pool > may be divided on a CIDR boundary to the longest minimum > allocation or assignment of any of the RIRs in order to > complete these allocations. Addresses that are left over > will be held in the Reclamation Pool until additional IP > addresses are returned, or a minimum allocation unit is > achieved that allows continued allocations from the pool. > > 4. RIR Eligibility for Receiving Allocations from the > Reclamation Pool > > Upon the exhaustion of an RIR's free space pool, an RIR > will become eligible to request address space from the > IANA Reclamation Pool when it publicly announces via its > respective global announcements email list and by posting a > notice on its website that it has exhausted its supply of > IPv4 address space. Exhaustion is defined as an inventory of > less than the equivalent of a single /8 and the inability to > further assign address space to its customers in units equal > to or shorter than the longest of the RIR's policy defined > minimum allocation unit. Any RIR that is formed after this > policy has been adopted by the ICANN Board of Directors is > not eligible to utilize this policy to obtain IPv4 address > space from the IANA. > > 5. Reporting Requirements > > The IANA shall publish on at least a weekly basis a report > that is publicly available which at a minimum details all > address space that has been received and that has been > allocated. The IANA shall publish a Returned Address Space > Report which indicates what resources were returned, by whom > and when. The IANA shall publish an Allocations Report on at > least a weekly basis which at a minimum indicates what IPv4 > address space has been allocated, which RIR received the > allocation and when. The IANA shall publish a public report > confirming RIR eligibility subsequent to Section 4. > > 6. No Transfer Rights > > Address space assigned from the Reclamation Pool is not > subject to transfer outside of an ICANN Board adopted > globally adopted transfer policy. The definition of Global > Transfer Policy for the purpose of this policy is a global > policy that has been processed and adopted by ICANN in > compliance with the MoU [2] and attachments as agreed to in > October 2004 between ICANN and the RIRs. > > 7. Definitions > > IANA - Internet Assigned Numbers Authority or it's successor > > ICANN - Internet Corporation for Assigned Names and Numbers or it's successor > > RIR - Regional Internet Registry as recognized by ICANN > > MOU - Memorandum of Understanding between ICANN and the RIR's > > IPV4 - Internet Protocol Version Four, the target protocol of this Global Policy > > 8. References > > 1. http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm Global Policy for the Allocation of the Remaining IPv4 Address Space, IANA, Retrieved 27 April 2010 > > 2. http://www.nro.net/documents/aso-mou.html ICANN Address Supporting Organization (ASO) MoU , Retrieved 27 May 2010. > > * sig-policy: APNIC SIG on resource management policy * > _______________________________________________ > sig-policy mailing list > sig-policy(a)lists.apnic.net > http://mailman.apnic.net/mailman/listinfo/sig-policy

1 0

Global Policy for IPv4 Allocations by the IANA Post Exhaustion (Version 2)
by Louis Lee 05 Jun '10

05 Jun '10

Dear esteemed colleagues of the IP addressing community of the APNIC region, If I may introduce myself to those of you who are not acquainted with me, my name is Louie Lee, and I am the senior network architect at Equinix US. Many of you also know me from my work in the addressing community as the Chair of the ASO Address Council since I have attended several APNIC meetings. Many more of you are well acquainted with Dr. Kenny Huang, who is an APNIC representative to the ASO AC.. Kenny is co-sponsoring a global policy proposal with me and several others in the global addressing community. I am presenting the DRAFT TEXT of the policy proposal to your community below in the hopes that you would provide public and private comments. Near identical drafts are being presented to the policy mailing lists in the other regions. The goal is to try to produce a global policy proposal that would not require substantial changes after it is formally submitted for consideration in all 5 RIR regions. Your feedback would be greatly appreciated. Best regards, Louie -- Louis Lee Sr. Network Architect New Service Development Equinix, Inc. louie(a)equinix.com Global Policy for IPv4 Allocations by the IANA Post Exhaustion Rationale: This policy defines the process for the allocation of IPv4 addresses post "Exhaustion Phase"[1]. In order to fulfill the requirements of this policy, the IANA must set up a reclamation pool to hold addresses in and distribute from in compliance with this policy. This policy establishes the process by which IPv4 addresses can be returned to and re-issued from the IANA post Exhaustion Phase. The intent of this policy is as follows: * Includes all post Exhaustion Phase address space returned to the IANA. * Allows allocations by the IANA from the Reclamation Pool once the Exhaustion Phase has been completed. * Defines "need" as the basis for further IPv4 allocations by the IANA. * Does not differentiate any class of IPv4 address space unless defined by RFC 1918. * Encourages the return of IPv4 address space by making this re-allocation process available. * Disallows transfers of addresses sourced from the Reclamation Pool in the absence of an IPV4 Global Transfer Policy to neutralize transfer process inequities across RIR regions. * Applies to legacy IPv4 Address Space initially allocated by the IANA to users including the allocations to RIRs. * Includes any length of fragments currently held by the IANA now or in the future. 1. Reclamation Pool Upon adoption of this IPv4 address policy by the ICANN Board of Directors, the IANA shall establish a Reclamation Pool to be utilized post RIR IPv4 exhaustion as defined in Section 5. As soon as the first RIR exhausts its inventory of IP address space, this Reclamation Pool will be declared active. 2. Returning Address Space to the IANA The IANA will accept into the Reclamation Pool all eligible IPv4 address space that is offerred for return. Eligible address space includes any addresses not previously designated for special use by an IETF published RFC explicitly offerred for return to the IANA by: a) The RIR to which the space is assigned b) The registrant of record where no RIR holds authority 3. Address Allocations from the Reclamation Pool by the IANA Allocations from the Reclamation Pool may begin once the pool is declared active. Aggregates in the Reclamation Pool may be divided on a CIDR boundary to the longest minimum allocation or assignment of any of the RIRs in order to complete these allocations. Addresses that are left over will be held in the Reclamation Pool until additional IP addresses are returned, or a minimum allocation unit is achieved that allows continued allocations from the pool. 4. RIR Eligibility for Receiving Allocations from the Reclamation Pool Upon the exhaustion of an RIR's free space pool, an RIR will become eligible to request address space from the IANA Reclamation Pool when it publicly announces via its respective global announcements email list and by posting a notice on its website that it has exhausted its supply of IPv4 address space. Exhaustion is defined as an inventory of less than the equivalent of a single /8 and the inability to further assign address space to its customers in units equal to or shorter than the longest of the RIR's policy defined minimum allocation unit. Any RIR that is formed after this policy has been adopted by the ICANN Board of Directors is not eligible to utilize this policy to obtain IPv4 address space from the IANA. 5. Reporting Requirements The IANA shall publish on at least a weekly basis a report that is publicly available which at a minimum details all address space that has been received and that has been allocated. The IANA shall publish a Returned Address Space Report which indicates what resources were returned, by whom and when. The IANA shall publish an Allocations Report on at least a weekly basis which at a minimum indicates what IPv4 address space has been allocated, which RIR received the allocation and when. The IANA shall publish a public report confirming RIR eligibility subsequent to Section 4. 6. No Transfer Rights Address space assigned from the Reclamation Pool is not subject to transfer outside of an ICANN Board adopted globally adopted transfer policy. The definition of Global Transfer Policy for the purpose of this policy is a global policy that has been processed and adopted by ICANN in compliance with the MoU [2] and attachments as agreed to in October 2004 between ICANN and the RIRs. 7. Definitions IANA - Internet Assigned Numbers Authority or it's successor ICANN - Internet Corporation for Assigned Names and Numbers or it's successor RIR - Regional Internet Registry as recognized by ICANN MOU - Memorandum of Understanding between ICANN and the RIR's IPV4 - Internet Protocol Version Four, the target protocol of this Global Policy 8. References 1. http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm Global Policy for the Allocation of the Remaining IPv4 Address Space, IANA, Retrieved 27 April 2010 2. http://www.nro.net/documents/aso-mou.html ICANN Address Supporting Organization (ASO) MoU , Retrieved 27 May 2010.

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

sig-policy June 2010