Network Working Group J. Weil
Internet-Draft Time Warner Cable
Intended status: Informational V. Kuarsingh
Expires: March 23, 2012 Rogers Communications
C. Donley
CableLabs
C. Liljenstolpe
Telstra Corp
M. Azinger
Frontier Communications
September 20, 2011
IANA Reserved IPv4 Prefix for Shared Transition Space
draft-weil-shared-transition-space-request-05
Abstract
This document requests that an IPv4 /10 be reserved as Shared
Transition Space solely to facilitate deployment of IPv6 transition/
IPv4 coexistence technologies after IPv4 exhaustion.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 23, 2012.
Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Weil, et al. Expires March 23, 2012 [Page 1]
Internet-Draft Shared Transition Space Request September 2011
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Shared Transition Space . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . . 9
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Weil, et al. Expires March 23, 2012 [Page 2]
Internet-Draft Shared Transition Space Request September 2011
1. Introduction
Many operators are currently implementing their IPv6 transition
plans. During the transition, continued support for legacy IPv4-only
devices will be required. Also, some IPv6 transition technologies
require the use of IPv4 address space. In order to facilitate the
deployment of transition technologies and to support such legacy
IPv4-only devices and services, Service Providers require IPv4
address space that is separate from the range of IPv4 addresses used
by subscribers. This address space need not be unique to each
provider, but should be outside of [RFC1918] space. This document
requests that an IPv4 /10 be reserved as Shared Transition Space
solely to facilitate deployment of IPv6 transition/IPv4 coexistence
technologies.
Weil, et al. Expires March 23, 2012 [Page 3]
Internet-Draft Shared Transition Space Request September 2011
2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Weil, et al. Expires March 23, 2012 [Page 4]
Internet-Draft Shared Transition Space Request September 2011
3. Motivation
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. In order to provide IPv4 service to customers and/or devices
once the IPv4 address space is exhausted, Service Providers must
multiplex several subscribers behind a single IPv4 address using one
of several techniques, often using a Carrier Grade NAT (CGN)
[RFC6264]. For several IPv4 extension/IPv6 transition technologies
including NAT444 [I-D.shirasaki-nat444], 6RD[RFC5969], and 6to4-
PMT[I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel], addresses
between the CGN and subscriber home routers need not be globally
unique, only unique inside the CGN. Thus, providers need sufficient
non-[RFC1918] address space to deploy such technologies and avoid
overlap with customer use of private address space.
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 CPE 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
[I-D.shirasaki-nat444].
Additional use cases for Shared Transition Space are described in
[I-D.bdgks-arin-shared-transition-space].
Weil, et al. Expires March 23, 2012 [Page 5]
Internet-Draft Shared Transition Space Request September 2011
4. Shared Transition Space
This document proposes the assignment of a /10 as Shared Transition
Space. Shared Transition Space is IPv4 address space reserved for
Infrastructure Provider use with the purpose of facilitating IPv6
transition and IPv4 coexistence deployment. The requested block
SHOULD NOT be utilized for any purpose other than as "inside"
addresses in a carrier NAT environment (e.g., between the CGN and
customer CPE devices) or for other IPv4 to IPv6 transition
infrastructure. Network equipment manufacturers MUST NOT use the
assigned block in default or example device configurations.
Because Shared Transition addresses have no meaning outside of the
Infrastructure Provider, routing information about shared transition
space networks MUST NOT be propagated on interdomain links, and
packets with shared transition source or destination addresses SHOULD
NOT be forwarded across such links, except where required based on
business relationships such as hosted CGN service. Internet service
providers SHOULD filter out routing information about shared
transition space networks on ingress links. Reverse DNS queries for
Shared Transition Space addresses MUST NOT be forwarded to the global
DNS infrastructure.
Weil, et al. Expires March 23, 2012 [Page 6]
Internet-Draft Shared Transition Space Request September 2011
5. Security Considerations
This memo does not define any protocol, and raises no security
issues. Any addresses allocated as Shared Transition Space would not
be routable on the Internet.
Weil, et al. Expires March 23, 2012 [Page 7]
Internet-Draft Shared Transition Space Request September 2011
6. IANA Considerations
IANA is asked to record the allocation of an IPv4 /10 for use as
Shared Transition Space.
Weil, et al. Expires March 23, 2012 [Page 8]
Internet-Draft Shared Transition Space Request September 2011
7. References
7.1. Normative References
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6264] Jiang, S., Guo, D., and B. Carpenter, "An Incremental
Carrier-Grade NAT (CGN) for IPv6 Transition", RFC 6264,
June 2011.
7.2. Informative References
[I-D.bdgks-arin-shared-transition-space]
Barber, S., Delong, O., Grundemann, C., Kuarsingh, V., and
B. Schliesser, "ARIN Draft Policy 2011-5: Shared
Transition Space",
draft-bdgks-arin-shared-transition-space-01 (work in
progress), July 2011.
[I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel]
Kuarsingh, V., Lee, Y., and O. Vautrin, "6to4 Provider
Managed Tunnels",
draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-03
(work in progress), September 2011.
[I-D.shirasaki-nat444]
Yamagata, I., Shirasaki, Y., Nakagawa, A., Yamaguchi, J.,
and H. Ashida, "NAT444", draft-shirasaki-nat444-04 (work
in progress), July 2011.
[RFC5969] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4
Infrastructures (6rd) -- Protocol Specification",
RFC 5969, August 2010.
Weil, et al. Expires March 23, 2012 [Page 9]
Internet-Draft Shared Transition Space Request September 2011
Appendix A. Acknowledgments
Thanks to the following people (in alphabetical order) for their
guidance and feedback:
John Brzozowski
Isaiah Connell
Greg Davies
Kirk Erichsen
Wes George
Tony Hain
Philip Matthews
John Pomeroy
Barbara Stark
Jean-Francois Tremblay
Leo Vegoda
Steven Wright
Ikuhei Yamagata
Weil, et al. Expires March 23, 2012 [Page 10]
Internet-Draft Shared Transition Space Request September 2011
Authors' Addresses
Jason Weil
Time Warner Cable
13820 Sunrise Valley Drive
Herndon, VA 20171
USA
Email: jason.weil@twcable.com
Victor Kuarsingh
Rogers Communications
8200 Dixie Road
Brampton, ON L6T 0C1
Canada
Email: victor.kuarsingh@gmail.com
Chris Donley
CableLabs
858 Coal Creek Circle
Louisville, CO 80027
USA
Email: c.donley@cablelabs.com
Christopher Liljenstolpe
Telstra Corp
7/242 Exhibition Street
Melbourne, VIC 316
Australia
Phone: +61 3 8647 6389
Email: cdl@asgaard.org
Marla Azinger
Frontier Communications
Vancouver, WA
USA
Phone: +1.360.513.2293
Email: marla.azinger@frontiercorp.com
Weil, et al. Expires March 23, 2012 [Page 11]
