ARIN-prop-276: Returned Addresses to the 4.10 Reserved Pool [Archived]
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.
Date: 16 June 2019
Proposal Originator: Mike Burns
Problem Statement:
Persistence of 4.1.8.1 (waiting list) due to unpredictable influxes of addresses is undesirable.
Policy Statement:
Change “4.10. Dedicated IPv4 Block to Facilitate IPv6 Deployment” to “4.10 Dedicated IPv4 Pool to Facilitate IPv6 Deployment”
Change" When ARIN receives its last /8 IPv4 allocation from IANA, a contiguous /10 IPv4 block will be set aside and dedicated to facilitate IPv6 deployment. Allocations and assignments from this block " to “In addition to the contiguous /10 IPv4 block set aside and dedicated to facilitate IPv6 deployment, all returns and revocations of IPv4 blocks will be added to the pool of space dedicated to the facilitation of IPv6 deployment. Allocations and assignments from this pool "
Change “This block will be subject to a minimum size allocation of /28 and a maximum size allocation of /24. ARIN should use sparse allocation when possible within that /10 block.” to “This pool will be subject to a minimum size allocation of /28 and a maximum sized allocation of /24. ARIN should use sparse allocation when possible within the pool.”
Timetable for Implementation: Immediate
OUT OF DATE?
Here in the Vault, information is published in its final form and then not changed or updated. As a result, some content, specifically links to other pages and other references, may be out-of-date or no longer available.