[arin-ppml] ARIN-2011-5: Shared Transition Space for IPv4 Address Extension - Last Call

[Hale, William C]

I support this draft policy.

Bill 
________________________________________
From: arin-ppml-bounces at arin.net [arin-ppml-bounces at arin.net] On Behalf Of ARIN [info at arin.net]
Sent: Monday, April 18, 2011 2:06 PM
To: arin-ppml at arin.net
Subject: [arin-ppml] ARIN-2011-5: Shared Transition Space for IPv4 Address Extension - Last Call

The ARIN Advisory Council (AC) met on 13 April 2011 and decided to
send the following draft policy to last call:

   ARIN-2011-5: Shared Transition Space for IPv4 Address Extension

Feedback is encouraged during the last call period. All comments should
be provided to the Public Policy Mailing List. Last call for 2011-5 will
expire on 2 May 2011. After last call the AC will conduct their last
call review.

The draft policy text is below and available at:
https://www.arin.net/policy/proposals/

The ARIN Policy Development Process is available at:
https://www.arin.net/policy/pdp.html

Regards,

Communications and Member Services
American Registry for Internet Numbers (ARIN)


## * ##


Draft Policy ARIN-2011-5
Shared Transition Space for IPv4 Address Extension

Date: 20 January 2011

Policy statement:

Updates 4.10 of the NRPM:
A second contiguous /10 IPv4 block will be reserved to facilitate IPv4
address extension. This block will not be allocated or assigned to any
single organization, but is to be shared by Service Providers for
internal use for IPv4 address extension deployments until connected
networks fully support IPv6. Examples of such needs include: IPv4
addresses between home gateways and NAT444 translators.

Rationale:

The Internet community is rapidly consuming the remaining supply of
unallocated IPv4 addresses. During the transition period to IPv6, it is
imperative that Service Providers maintain IPv4 service for devices and
networks that are currently incapable of upgrading to IPv6.
Consumers must be able to reach the largely IPv4 Internet after
exhaustion. Without a means to share addresses, people or organizations
who gain Internet access for the first time, or those who switch
providers, or move to another area, will be unable to reach the IPv4
Internet.

Further, many CPE router devices used to provide residential or
small-medium business services have been optimized for IPv4 operation,
and typically require replacement in order to fully support the
transition to IPv6 (either natively or via one of many transition
technologies). In addition, various consumer devices including
IP-enabled televisions, gaming consoles, medical and family monitoring
devices, etc. are IPv4-only, and cannot be upgraded. While these will
eventually be replaced with dual-stack or IPv6 capable devices, this
transition will take many years. As these are typically consumer-owned
devices, service providers do not have control over the speed of their
replacement cycle. However, consumers have an expectation that they
will continue to receive IPv4 service, and that such devices will
continue to have IPv4 Internet connectivity after the IPv4 pool is
exhausted, even if the customer contracts for new service with a new
provider.

Until such customers replace their Home Gateways and all IPv4-only
devices with IPv6-capable devices, Service Providers will be required to
continue to offer IPv4 services through the use of an IPv4 address
sharing technology such as NAT444. A recent study showed that there is
no part of RFC1918 space which would not overlap with some IPv4
gateways, and therefore to prevent address conflicts, new address space
is needed.

Service providers are currently presented with three options for
obtaining sufficient IPv4 address space for NAT444/IPv4 extension
deployments: (1) Request allocations under the NRPM; (2) share address
space with other providers (this proposal); or (3) use address space
allocated to another entity (i.e. ‘squat’). Of the three options,
option 2 (this proposal) is preferable, as it will minimize the number
of addresses used for IPv4 extension deployments while preserving the
authority of IANA and RIRs.

Timetable for implementation: immediately




_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact info at arin.net if you experience any issues.
***************************************************************************************
The information contained in this message, including attachments, may contain
privileged or confidential information that is intended to be delivered only to the
person identified above. If you are not the intended recipient, or the person
responsible for delivering this message to the intended recipient, Windstream requests
that you immediately notify the sender and asks that you do not read the message or its
attachments, and that you delete them without copying or sending them to anyone else.