draft-ietf-v6ops-clatip-04.txt   rfc7335.txt 
INTERNET-DRAFT Cameron Byrne Internet Engineering Task Force (IETF) C. Byrne
Updates: 6333 (if approved) T-Mobile US Request for Comments: 7335 T-Mobile US
Intended Status: Standards Track August 4, 2014 Updates: 6333 August 2014
Expires: February 5, 2015 Category: Standards Track
ISSN: 2070-1721
IPv4 Service Continuity Prefix IPv4 Service Continuity Prefix
draft-ietf-v6ops-clatip-04
Abstract Abstract
DS-Lite, defined in RFC 6333, directs IANA to reserve 192.0.0.0/29 Dual-Stack Lite (DS-Lite), defined in RFC 6333, directs IANA to
for the B4 element. This memo directs IANA to generalize that reserve 192.0.0.0/29 for the Basic Bridging BroadBand (B4) element.
reservation to include other cases where a non-routed IPv4 interface Per this memo, IANA has generalized that reservation to include other
must be numbered as part of an IPv6 transition solution. cases where a non-routed IPv4 interface must be numbered as part of
an IPv6 transition solution.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
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 of six months This is an Internet Standards Track document.
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."
The list of current Internet-Drafts can be accessed at This document is a product of the Internet Engineering Task Force
http://www.ietf.org/1id-abstracts.html (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
The list of Internet-Draft Shadow Directories can be accessed at Information about the current status of this document, any errata,
http://www.ietf.org/shadow.html and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7335.
Copyright and License Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . 3 3. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . 2
4. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3 4. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 8. Normative References . . . . . . . . . . . . . . . . . . . . . 4
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the Basic DS-Lite [RFC6333] directs IANA to reserve 192.0.0.0/29 for the Basic
Bridging BroadBand (B4) element. This memo generalizes that IANA Bridging BroadBand (B4) element. This memo generalizes that IANA
reservation to include other cases where a non-routed IPv4 interface reservation to include other cases where a non-routed IPv4 interface
must be numbered in an IPv6 transition solution. IANA shall list the must be numbered in an IPv6 transition solution. IANA has listed the
address block 192.0.0.0/29 reserved for IPv4 Service Continuity 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 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 that requires IPv4 addresses for backward compatibility with IPv4
communications in an IPv6-only network, but does not emit IPv4 communications in an IPv6-only network but does not emit IPv4 packets
packets "on the wire". "on the wire".
This generalization does not impact the use of the IPv4 Service This generalization does not impact the use of the IPv4 Service
Continuity Prefix in a DS-Lite context. Continuity Prefix in a DS-Lite context.
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. The Case of 464XLAT 3. The Case of 464XLAT
464XLAT [RFC6877] describes an architecture for providing IPv4 464XLAT [RFC6877] describes an architecture for providing IPv4
communication over an IPv6-only access network. One of the methods communication over an IPv6-only access network. One of the methods
described in [RFC6877] is for the client side translator (CLAT) to be described in [RFC6877] is for the customer-side translator (CLAT) to
embedded in the host, such as a smartphone or a CPE (Customer be embedded in the host, such as a smartphone or a CPE (Customer
Premises Equipment). In such scenarios, the host must have an IPv4 Premises Equipment). In such scenarios, the host must have an IPv4
address configured to present to the host network stack and for address configured to present to the host network stack and for
applications to bind IPv4 sockets. applications to bind IPv4 sockets.
4. Choosing 192.0.0.0/29 4. Choosing 192.0.0.0/29
To avoid conflicts with any other network that may communicate with To avoid conflicts with any other network that may communicate with
the CLAT or other IPv6 transition solution, a locally unique IPv4 the CLAT or other IPv6 transition solution, a locally unique IPv4
address must be assigned. address must be assigned.
IANA has defined a well-known range, 192.0.0.0/29, in [RFC6333], 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 which is dedicated for DS-Lite. As defined in [RFC6333], this subnet
is only present between the B4 and the AFTR and never emits packets is only present between the B4 and the Address Family Transition
from this prefix "on the wire". 464XLAT has the same need for a non- Router (AFTR) and never emits packets from this prefix "on the wire".
routed IPv4 prefix, and this same need may be common for other 464XLAT has the same need for a non-routed IPv4 prefix, and this same
similar solutions. It is most prudent and effective to generalize need may be common for other similar solutions. It is most prudent
192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6 and effective to generalize 192.0.0.0/29 for the use of supporting
transition technologies rather than reserving a prefix for every IPv4 interfaces in IPv6 transition technologies rather than reserving
possible solution. a prefix for every possible solution.
With this memo, 192.0.0.0/29 is now generalized across multiple IPv4 With this memo, 192.0.0.0/29 is now generalized across multiple IPv4
continuity solutions such as 464XLAT and DS-lite. A host MUST NOT continuity solutions such as 464XLAT and DS-Lite. A host MUST NOT
enable two active IPv4 continuity solutions simultaneously in a way enable two active IPv4 continuity solutions simultaneously in a way
that would cause a node to have overlapping 192.0.0.0/29 address that would cause a node to have overlapping 192.0.0.0/29 address
space. space.
5. Security Considerations 5. Security Considerations
No new security considerations beyond what is described [RFC6333] and There are no new security considerations beyond what is described
[RFC6877]. [RFC6333] and [RFC6877].
6. IANA Considerations 6. IANA Considerations
This document requests IANA to update the IPv4 Special-Purpose IANA has updated the IPv4 Special-Purpose Address Registry available
Address Registry available at (http://www.iana.org/assignments/iana- at (http://www.iana.org/assignments/iana-ipv4-special-registry/) as
ipv4-special-registry/iana-ipv4-special-registry) as follows: follows:
OLD: OLD:
192.0.0.0/29 DS-Lite [RFC6333] 192.0.0.0/29 DS-Lite [RFC6333]
NEW: NEW:
192.0.0.0/29 IPv4 Service Continuity Prefix [RFC-to-be-xxx] 192.0.0.0/29 IPv4 Service Continuity Prefix [RFC7335]
+----------------------+-----------------------------------+
+----------------------+-----------------------------------+ | Attribute | Value |
| Attribute | Value | +----------------------+-----------------------------------+
+----------------------+-----------------------------------+ | Address Block | 192.0.0.0/29 |
| Address Block | 192.0.0.0/29 | | Name | IPv4 Service Continuity Prefix |
| Name | IPv4 Service Continuity Prefix | | RFC | RFC 7335 |
| RFC | RFC TBD | | Allocation Date | June 2011 |
| Allocation Date | June 2014 | | Termination Date | N/A |
| Termination Date | N/A | | Source | True |
| Source | True | | Destination | True |
| Destination | True | | Forwardable | True |
| Forwardable | True | | Global | False |
| Global | False | | Reserved-by-Protocol | False |
| Reserved-by-Protocol | False | +----------------------+-----------------------------------+
+----------------------+-----------------------------------+
7. Acknowledgements 7. Acknowledgements
This document has been substantially improved by specific feedback This document has been substantially improved by specific feedback
from Dave Thaler, Fred Baker, Wes George, Lorenzo Colitti, and from Dave Thaler, Fred Baker, Wes George, Lorenzo Colitti, and
Mohamed Boucadair. Mohamed Boucadair.
8. References 8. Normative References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC6333, August 2011. Exhaustion", RFC 6333, August 2011.
[RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
Combination of Stateful and Stateless Translation", Combination of Stateful and Stateless Translation", RFC
RFC6877, April 2013. 6877, April 2013.
Authors' Addresses Author's Address
Cameron Byrne Cameron Byrne
Bellevue, WA, USA Bellevue, WA
Email: Cameron.Byrne@T-Mobile.com USA
EMail: Cameron.Byrne@T-Mobile.com
 End of changes. 29 change blocks. 
82 lines changed or deleted 71 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/