idnits 2.17.1 draft-ietf-v6ops-clatip-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 9 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 5, 2014) is 3637 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Cameron Byrne 3 Intended Status: Informational T-Mobile US 4 Expires: November 6, 2014 May 5, 2014 6 IPv4 Service Continuity Prefix 7 draft-ietf-v6ops-clatip-00 9 Abstract 11 DS-Lite, defined in RFC 6333, directs IANA to reserve 192.0.0.0/29 12 for the B4 element. This memo directs IANA to generalize that 13 reservation to include other cases where a non-routed IPv4 interface 14 must be numbered as part of an IPv6 transition solution. 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/1id-abstracts.html 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 Copyright and License Notice 39 Copyright (c) 2014 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2 The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3 57 4 Security Considerations . . . . . . . . . . . . . . . . . . . . 3 58 5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 59 6 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 60 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 7.1 Normative References . . . . . . . . . . . . . . . . . . . 4 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 64 1 Introduction 66 DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the B4 67 element. This memo generalizes that IANA reservation to include 68 other cases where a non-routed IPv4 interface must be numbered in an 69 IPv6 transition solution. IANA shall list the address block 70 192.0.0.0/29 reserved for IPv4 Service Continuity Prefix. The result 71 is that 192.0.0.0/29 may be used in any system that requires IPv4 72 addresses for backward compatibility with IPv4 communications in an 73 IPv6-only network, but does not emit IPv4 packets "on the wire". 75 2 The Case of 464XLAT 77 464XLAT [RFC6877] describes an architecture for providing IPv4 78 communication over an IPv6-only access network. One of the methods 79 described in [RFC6877] is for the client side translator (CLAT) to be 80 embedded in the host, such as a smartphone. In this scenario, the 81 host must have an IPv4 address configured to present to the host 82 network stack and for applications to bind sockets. 84 3. Choosing 192.0.0.0/29 86 To avoid conflicts with any other network that may communicate with 87 the CLAT or other IPv6 transition solution, a locally unique IPv4 88 address must be assigned. 90 IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333], 91 which is dedicated for DS-lite. As defined in [RFC6333], this subnet 92 is only present between the B4 and the AFTR and never emits packets 93 from this prefix "on the wire". 464XLAT has the same need for a non- 94 routed IPv4 prefix, and this same need may be common for other 95 similar solutions. It is most prudent and effective to generalize 96 192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6 97 transition technologies rather than reserving a prefix for every 98 possible solution. 100 With this memo, 192.0.0.0/29 is now generalized across multiple IPv4 101 continuity solutions such as 464XLAT and DS-lite. It is important 102 that a host never be deployed with 2 active IPv4 continuity solutions 103 simultaneously in a way that would cause a node to have overlapping 104 address from 192.0.0.0/29. 106 4 Security Considerations 108 No new security considerations beyond what is described [RFC6333] and 109 [RFC6877]. 111 5 IANA Considerations 113 IANA is directed to generalize the reservation of 192.0.0.0/29 from 114 DS-lite to "IPv4 Service Continuity Prefix". 116 6 Acknowledgements 118 This document has been substantially improved by specific feedback 119 from Dave Thaler, Fred Baker, Wes George, Lorenzo Colitti, and 120 Mohamed Boucadair. 122 7 References 124 7.1 Normative References 126 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 127 Stack Lite Broadband Deployments Following IPv4 128 Exhaustion", RFC6333, August 2011. 130 [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: 131 Combination of Stateful and Stateless Translation", 132 RFC6877, April 2013. 134 Authors' Addresses 136 Cameron Byrne 137 Bellevue, WA, USA 138 Email: Cameron.Byrne@T-Mobile.com