idnits 2.17.1 draft-byrne-v6ops-clatip-01.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC6333]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 7 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 (December 28, 2013) is 3771 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 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: July 1, 2014 December 28, 2013 6 IPv6 Transitional Technology IPv4 Prefix 7 draft-byrne-v6ops-clatip-01 9 Abstract 11 DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the B4 12 element. This memo generalizes that reservation to include other 13 cases where a non-routed IPv4 interface must be numbered in an IPv6 14 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) 2013 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 . . . . . . . . . . . . . . . . . . . . . . 3 59 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 6.1 Normative References . . . . . . . . . . . . . . . . . . . 4 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1 Introduction 65 DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the B4 66 element. This memo generalizes that IANA reservation to include 67 other cases where a non-routed IPv4 interface must be numbered in an 68 IPv6 transition solutions. IANA shall list 192.0.0.0/29 to be 69 reserved for IPv6 Transitional Technology IPv4 Prefix. The result is 70 that 192.0.0.0/29 may be used in any system that requires IPv4 71 addresses for backward compatibility with IPv4 communications, but 72 does not emit IPv4 packets "on the wire". 74 2 The Case of 464XLAT 76 464XLAT [RFC6877] describes an architecture for providing IPv4 77 communication over an IPv6-only access network. One of the methods 78 described in [RFC6877] is for the client side translator (CLAT) to be 79 embedded in the host, such as a smartphone. In this scenario, the 80 host must have an IPv4 address configured to present to the network 81 stack and for applications to bind sockets. 83 3. Choosing 192.0.0.0/29 85 To avoid conflicts with any other network that may communicate with 86 the CLAT, a locally unique address must be assigned. 88 IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333], 89 which is dedicated for DS-lite. As defined in [RFC6333], this subnet 90 is only present between the B4 and the AFTR and never emits packets 91 from this prefix "on the wire". 464XLAT has the same need for a non- 92 routed IPv4 prefix. It is most prudent and effective to generalize 93 192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6 94 transition technologies rather than reserving a prefix for every 95 possible solution. 97 4 Security Considerations 99 No new security considerations beyond what is described [RFC6333] and 100 [RFC6877]. 102 5 IANA Considerations 104 IANA is directed to generalize the reservation of 192.0.0.0/29 from 105 DS-lite to "IPv6 Transitional Technology IPv4 Prefix". 107 6 References 108 6.1 Normative References 110 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 111 Stack Lite Broadband Deployments Following IPv4 112 Exhaustion", RFC6333, August 2011. 114 [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: 115 Combination of Stateful and Stateless Translation", 116 RFC6877, April 2013. 118 Authors' Addresses 120 Cameron Byrne 121 Bellevue, WA, USA 122 Email: Cameron.Byrne@T-Mobile.com