This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Suggested updates to 2010-05 (Global Policy for IPv4 Allocation by the IANA post exhaustion)
- Previous message (by thread): [address-policy-wg] Address Policy WG Minutes from RIPE 60 / Prague
- Next message (by thread): [address-policy-wg] Suggested updates to 2010-05 (Global Policy for IPv4 Allocation by the IANA post exhaustion)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Chris Grundemann
cgrundemann at gmail.com
Sun Sep 19 20:12:56 CEST 2010
Hello APWG, After receiving great feedback in several regions, the original authors of the proposal have discussed all of the feedback received and our suggested revisions are below: Problem #1: The allocation method was unfair. The intent was never for a single RIR to be able to be allocated all available address space in mass quantities. We do however want any available address space to be utilized if there is need. We've addressed what we would characterize as a mechanical issue. --new text: Section 3. Address Allocations from the Reclamation Pool by the IANA Allocations from the Reclamation Pool may begin once the pool is declared active. Addresses in the Reclamation Pool must be allocated on a CIDR boundary. Allocations from the Reclamation Pool are subject to a minimum allocation unit equal to the minimum allocation unit of all RIRs and a maximum allocation unit of one /8. The Reclamation Pool will be divided on CIDR boundaries and distributed evenly to all eligible RIRs once each quarter. Any remainder not evenly divisible by the number of eligible RIRs based on a CIDR boundary equal to or larger than the minimum allocation unit will remain in the Reclamation Pool. Addresses that are left over will be held in the Reclamation Pool until additional IP addresses can be returned to rejoin addresses on CIDR boundaries to the Reclamation Pool or a minimum allocation unit is set to allow allocation from existing inventory. Problem #2: Without excluding transition space, some RIR's would never be eligible. To address this, we've defined a /10 exemption for any/all pools of address space set-aside by any RIR. --new text Section 4. RIR Eligibility for Receiving Allocations from the Reclamation Pool Upon the exhaustion of an RIR's free space pool and after receiving their final /8 from the IANA[3], 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 any RIR's policy defined minimum allocation unit. Up to one /10 or equivalent of IPv4 address space specifically reserved for any special purpose by an RIR will not be counted against that RIR when determining eligibility unless that space was received from the IANA reclamation pool. Any RIR that is formed after the ICANN Board of Directors has ratified this policy is not eligible to utilize this policy to obtain IPv4 address space from the IANA. These revisions are being proposed in all regions in order to maintain consistency in the policy text on the global level. Thank you for your consideration. ~Chris -- @ChrisGrundemann weblog.chrisgrundemann.com www.burningwiththebush.com www.coisoc.org
- Previous message (by thread): [address-policy-wg] Address Policy WG Minutes from RIPE 60 / Prague
- Next message (by thread): [address-policy-wg] Suggested updates to 2010-05 (Global Policy for IPv4 Allocation by the IANA post exhaustion)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]