Network Working Group J.W. Weil
Internet-Draft Time Warner Cable
Intended status: Informational V.K. Kuarsingh
Expires: February 01, 2012 Rogers Communications
C.D. Donley
Telstra Corp
M.A. Azinger
Frontier Communications
August 2, 2011

IANA Reserved IPv4 Prefix for Shared Transition Space


This document requests a reserved IANA IPv4 address allocation as Shared Transition Space to support the deployment of IPv4 address sharing technologies post 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:/⁠/⁠⁠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 February 01, 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:/⁠/⁠⁠license-⁠info) in effect on the date of publication of this document. Please review these documents 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

Many operators are currently implementing their IPv6 transition plans. During the transition, continued support for heritage IPv4-only devices will be required. In order to facilitate the deployment of transition technologies to support such heritage 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.

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].

3. Applicability

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.

The applicability of and justification for Shared Transition Space is described in [I-D.bdgks-arin-shared-transition-space].

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. Internet service providers SHOULD filter out routing information about shared transition space networks on ingress links.

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.

6. IANA Considerations

IANA is asked to record the allocation of an IPv4 /10 for use as Shared Transition Space.

7. 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.
[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", Internet-Draft draft-bdgks-arin-shared-transition-space-00, July 2011.

Appendix A. Acknowledgements

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

Authors' Addresses

Jason Weil Time Warner Cable 13820 Sunrise Valley Drive Herndon, VA 20171 USA EMail:
Victor Kuarsingh Rogers Communications 8200 Dixie Road Brampton, ON L6T 0C1 Canada EMail:
Chris Donley CableLabs 858 Coal Creek Circle Louisville, CO 80027 USA EMail:
Christopher Liljenstolpe Telstra Corp 7/242 Exhibition Street Melbourne, VIC 316 AU Phone: +61 3 8647 6389 EMail:
Marla Azinger Frontier Communications Vancouver, WA US Phone: +1.360.513.2293 EMail: