INTERNET-DRAFT CameronInternet Engineering Task Force (IETF) C. ByrneUpdates: 6333 (if approved)Request for Comments: 7335 T-Mobile USIntended Status: Standards TrackUpdates: 6333 August4,2014Expires: February 5, 2015Category: Standards Track ISSN: 2070-1721 IPv4 Service Continuity Prefixdraft-ietf-v6ops-clatip-04AbstractDS-Lite,Dual-Stack Lite (DS-Lite), defined in RFC 6333, directs IANA to reserve 192.0.0.0/29 for theB4Basic Bridging BroadBand (B4) element.This memo directsPer this memo, IANAto generalizehas generalized that reservation to include other cases where a non-routed IPv4 interface must be numbered as part of an IPv6 transition solution. Status ofthisThis Memo ThisInternet-Draftissubmitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsan Internet Standards Track document. This document is a product of the Internet Engineering Task Force(IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum(IETF). It represents the consensus ofsix monthsthe IETF community. It has received public review andmay be updated, replaced, or obsoletedhas been approved for publication byother documents at any time. Itthe Internet Engineering Steering Group (IESG). Further information on Internet Standards isinappropriate to use Internet-Drafts as reference material or to cite them other than as "workavailable inprogress." The listSection 2 of RFC 5741. Information about the currentInternet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The liststatus ofInternet-Draft Shadow Directories canthis document, any errata, and how to provide feedback on it may beaccessedobtained athttp://www.ietf.org/shadow.htmlhttp://www.rfc-editor.org/info/rfc7335. Copyrightand LicenseNotice Copyright (c) 2014 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 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 . . . . . . . . . . . . . . . . . . . . . . . . .32 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . .32 3. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . .32 4. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . .43 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . .43 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 8.References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1.Normative References . . . . . . . . . . . . . . . . . . .5 Authors' Addresses . . . . . . . . . . . . . . . .. .. . . . . . 54 1. Introduction DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the Basic Bridging BroadBand (B4) element. This memo generalizes that IANA reservation to include other cases where a non-routed IPv4 interface must be numbered in an IPv6 transition solution. IANAshall listhas listed the address block 192.0.0.0/29 reserved for IPv4 Service Continuity Prefix. The result is that 192.0.0.0/29 may be used in any system that requires IPv4 addresses for backward compatibility with IPv4 communications in an IPv6-onlynetwork,network but does not emit IPv4 packets "on the wire". This generalization does not impact the use of the IPv4 Service Continuity Prefix in a DS-Lite context. 2. Conventions 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 [RFC2119]. 3. The Case of 464XLAT 464XLAT [RFC6877] describes an architecture for providing IPv4 communication over an IPv6-only access network. One of the methods described in [RFC6877] is for theclient sidecustomer-side translator (CLAT) to be embedded in the host, such as a smartphone or a CPE (Customer Premises Equipment). In such scenarios, the host must have an IPv4 address configured to present to the host network stack and for applications to bind IPv4 sockets. 4. Choosing 192.0.0.0/29 To avoid conflicts with any other network that may communicate with the CLAT or other IPv6 transition solution, a locally unique IPv4 address must be assigned. IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333], which is dedicated for DS-Lite. As defined in [RFC6333], this subnet is only present between the B4 and theAFTRAddress Family Transition Router (AFTR) and never emits packets from this prefix "on the wire". 464XLAT has the same need for anon- routednon-routed IPv4 prefix, and this same need may be common for other similar solutions. It is most prudent and effective to generalize 192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6 transition technologies rather than reserving a prefix for every possible solution. With this memo, 192.0.0.0/29 is now generalized across multiple IPv4 continuity solutions such as 464XLAT andDS-lite.DS-Lite. A host MUST NOT enable two active IPv4 continuity solutions simultaneously in a way that would cause a node to have overlapping 192.0.0.0/29 address space. 5. Security ConsiderationsNoThere are no new security considerations beyond what is described [RFC6333] and [RFC6877]. 6. IANA ConsiderationsThis document requestsIANAto updatehas updated the IPv4 Special-Purpose Address Registry available at(http://www.iana.org/assignments/iana- ipv4-special-registry/iana-ipv4-special-registry)(http://www.iana.org/assignments/iana-ipv4-special-registry/) as follows: OLD: 192.0.0.0/29 DS-Lite [RFC6333] NEW: 192.0.0.0/29 IPv4 Service Continuity Prefix[RFC-to-be-xxx][RFC7335] +----------------------+-----------------------------------+ | Attribute | Value | +----------------------+-----------------------------------+ | Address Block | 192.0.0.0/29 | | Name | IPv4 Service Continuity Prefix | | RFC | RFCTBD7335 | | Allocation Date | June20142011 | | Termination Date | N/A | | Source | True | | Destination | True | | Forwardable | True | | Global | False | | Reserved-by-Protocol | False | +----------------------+-----------------------------------+ 7. Acknowledgements This document has been substantially improved by specific feedback from Dave Thaler, Fred Baker, Wes George, Lorenzo Colitti, and Mohamed Boucadair. 8.References 8.1.Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion",RFC6333,RFC 6333, August 2011. [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: Combination of Stateful and Stateless Translation",RFC6877,RFC 6877, April 2013.Authors' AddressesAuthor's Address Cameron Byrne Bellevue,WA,WA USAEmail:EMail: Cameron.Byrne@T-Mobile.com