1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
<pre>Internet Engineering Task Force (IETF) C. Byrne
Request for Comments: 7335 T-Mobile US
Updates: <a href="./rfc6333">6333</a> August 2014
Category: Standards Track
ISSN: 2070-1721
<span class="h1">IPv4 Service Continuity Prefix</span>
Abstract
Dual-Stack Lite (DS-Lite), defined in <a href="./rfc6333">RFC 6333</a>, directs IANA to
reserve 192.0.0.0/29 for the Basic Bridging BroadBand (B4) element.
Per this memo, IANA has generalized that reservation to include other
cases where a non-routed IPv4 interface must be numbered as part of
an IPv6 transition solution.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7335">http://www.rfc-editor.org/info/rfc7335</a>.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Byrne Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7335">RFC 7335</a> IPv4 Service Continuity Prefix August 2014</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. The Case of 464XLAT . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-4">4</a>. Choosing 192.0.0.0/29 . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-7">7</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-8">8</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
DS-Lite [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] 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. IANA has 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-only 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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The Case of 464XLAT</span>
464XLAT [<a href="./rfc6877" title=""464XLAT: Combination of Stateful and Stateless Translation"">RFC6877</a>] describes an architecture for providing IPv4
communication over an IPv6-only access network. One of the methods
described in [<a href="./rfc6877" title=""464XLAT: Combination of Stateful and Stateless Translation"">RFC6877</a>] is for the customer-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.
<span class="grey">Byrne Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7335">RFC 7335</a> IPv4 Service Continuity Prefix August 2014</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Choosing 192.0.0.0/29</span>
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 [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>],
which is dedicated for DS-Lite. As defined in [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>], this subnet
is only present between the B4 and the Address Family Transition
Router (AFTR) and never emits packets 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 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 and 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.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
There are no new security considerations beyond what is described
[<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>] and [<a href="./rfc6877" title=""464XLAT: Combination of Stateful and Stateless Translation"">RFC6877</a>].
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has updated the IPv4 Special-Purpose Address Registry available
at (<a href="http://www.iana.org/assignments/iana-ipv4-special-registry/">http://www.iana.org/assignments/iana-ipv4-special-registry/</a>) as
follows:
OLD:
192.0.0.0/29 DS-Lite [<a href="./rfc6333" title=""Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion"">RFC6333</a>]
NEW:
192.0.0.0/29 IPv4 Service Continuity Prefix [<a href="./rfc7335">RFC7335</a>]
<span class="grey">Byrne Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7335">RFC 7335</a> IPv4 Service Continuity Prefix August 2014</span>
+----------------------+-----------------------------------+
| Attribute | Value |
+----------------------+-----------------------------------+
| Address Block | 192.0.0.0/29 |
| Name | IPv4 Service Continuity Prefix |
| RFC | <a href="./rfc7335">RFC 7335</a> |
| Allocation Date | June 2011 |
| Termination Date | N/A |
| Source | True |
| Destination | True |
| Forwardable | True |
| Global | False |
| Reserved-by-Protocol | False |
+----------------------+-----------------------------------+
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgements</span>
This document has been substantially improved by specific feedback
from Dave Thaler, Fred Baker, Wes George, Lorenzo Colitti, and
Mohamed Boucadair.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC6333">RFC6333</a>] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4
Exhaustion", <a href="./rfc6333">RFC 6333</a>, August 2011.
[<a id="ref-RFC6877">RFC6877</a>] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
Combination of Stateful and Stateless Translation", <a href="./rfc6877">RFC</a>
<a href="./rfc6877">6877</a>, April 2013.
Author's Address
Cameron Byrne
Bellevue, WA
USA
EMail: Cameron.Byrne@T-Mobile.com
Byrne Standards Track [Page 4]
</pre>
|
