draft-ietf-v6ops-clatip-03.txt   draft-ietf-v6ops-clatip-04.txt 
INTERNET-DRAFT Cameron Byrne INTERNET-DRAFT Cameron Byrne
Updates: [RFC6333] (if approved) T-Mobile US Updates: 6333 (if approved) T-Mobile US
Intended Status: Standards Track June 11, 2014 Intended Status: Standards Track August 4, 2014
Expires: December 13, 2014 Expires: February 5, 2015
IPv4 Service Continuity Prefix IPv4 Service Continuity Prefix
draft-ietf-v6ops-clatip-03 draft-ietf-v6ops-clatip-04
Abstract Abstract
DS-Lite, defined in RFC 6333, directs IANA to reserve 192.0.0.0/29 DS-Lite, defined in RFC 6333, directs IANA to reserve 192.0.0.0/29
for the B4 element. This memo directs IANA to generalize that for the B4 element. This memo directs IANA to generalize that
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 as part of an IPv6 transition solution. must be numbered as part of an IPv6 transition solution.
Status of this Memo Status of this Memo
skipping to change at page 2, line 14 skipping to change at page 2, line 14
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3 3. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 4. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 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 shall list 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 "on the wire". packets "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. The Case of 464XLAT 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 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 client side translator (CLAT) to be
embedded in the host, such as a smartphone or a CPE (Customer 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.
3. 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 AFTR and never emits packets
from this prefix "on the wire". 464XLAT has the same need for a non- from this prefix "on the wire". 464XLAT has the same need for a non-
routed IPv4 prefix, and this same need may be common for other routed IPv4 prefix, and this same need may be common for other
similar solutions. It is most prudent and effective to generalize similar solutions. It is most prudent and effective to generalize
192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6 192.0.0.0/29 for the use of supporting IPv4 interfaces in IPv6
transition technologies rather than reserving a prefix for every transition technologies rather than reserving a prefix for every
possible solution. 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. It is important continuity solutions such as 464XLAT and DS-lite. A host MUST NOT
that a host never enable 2 active IPv4 continuity solutions enable two active IPv4 continuity solutions simultaneously in a way
simultaneously in a way that would cause a node to have overlapping that would cause a node to have overlapping 192.0.0.0/29 address
address from 192.0.0.0/29. space.
5. Security Considerations
4. Security Considerations
No new security considerations beyond what is described [RFC6333] and No new security considerations beyond what is described [RFC6333] and
[RFC6877]. [RFC6877].
5. IANA Considerations 6. IANA Considerations
This document requests IANA to update the IPv4 Special-Purpose This document requests IANA to update the IPv4 Special-Purpose
Address Registry available at (http://www.iana.org/assignments/iana- Address Registry available at (http://www.iana.org/assignments/iana-
ipv4-special-registry/iana-ipv4-special-registry) as follows: ipv4-special-registry/iana-ipv4-special-registry) as follows:
OLD: OLD:
192.0.0.0/29 DS-Lite [RFC6333] 192.0.0.0/29 DS-Lite [RFC6333]
NEW: NEW:
skipping to change at page 4, line 36 skipping to change at page 4, line 45
| RFC | RFC TBD | | RFC | RFC TBD |
| Allocation Date | June 2014 | | 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 |
+----------------------+-----------------------------------+ +----------------------+-----------------------------------+
6. 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.
7. References 8. References
7.1. Normative 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- [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", RFC6333, 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",
RFC6877, April 2013. RFC6877, April 2013.
Authors' Addresses Authors' Addresses
 End of changes. 11 change blocks. 
22 lines changed or deleted 33 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/