ARIN-prop-206 [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.
ARIN-prop-206 Implement IPv6 from IPv4 Without an Outage
Proposal Originator: Michael E. Mazarick
Date: 23 April 2014
Problem Statement:
Changing from IPv4 or any IP renumbering creates an outage when there is a transition of IPs, particularly to IPv6. By coordinating the IPv4 with the IPv6 and controlling the routing, it is possible to achieve an IPv4 to IPv6 transition without an outage.
Policy statement:
Although there is not a procedure that explicitly prohibits a coordinated IPv4/IPv6 allocation, there are several procedures in place that create an uncoordinated allocation between IPv4 and IPv6. Alternatives to Policy 4.10 (sparse allocation of IPv6 addresses). Another alternative is 2.9 because the prefix size between the IPv6 allocation has to be the same or a multiple of the IPv4 allocation. A system of “reservation” has been proposed so that an IPv6 block be available when going for the “next” IPv6 allocation. The proposal even is more “sparse” than existing procedure because it means that IPv6 allocations should be a “square” rather than a “line” of allocation because it becomes imperative not to get into someone else’s IPv6 space (based on their IPv4 allocation). There are probably several other allocation procedures that have to be modified/improved, but this is enough to get us started.
Comments:
Huawei has a patent #8,484,715 that achieves something very similar by deploying a system to achieve a transition without an outage. By utilizing a method of coordinating IPv4 and IPv6 address allocation and allowing Regional Internet Registrars to slightly modify their allocation of IPv6 addresses so it can be coordinated with an existing IPv4 addresses, the alternative allocation method would permit a transition from IPv4 to IPv6 without an outage.
a. Timetable for implementation: Since an organization has to have both IPv4 and IPv6 addresses to allocate, the best time is before the IPv4 depletion. It can be implemented after the depletion of IPv4 addresses, but the economics of developing the routing code to permit this transition action becomes much more unlikely. It is harder to achieve the economies of scale.
b. Anything else (nothing else at this time)
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.