| 1 |
<pre>Internet Engineering Task Force (IETF) R. Despres |
| 2 |
Request for Comments: 7600 RD-IPtech |
| 3 |
Category: Experimental S. Jiang, Ed. |
| 4 |
ISSN: 2070-1721 Huawei Technologies Co., Ltd |
| 5 |
R. Penno |
| 6 |
Cisco Systems, Inc. |
| 7 |
Y. Lee |
| 8 |
Comcast |
| 9 |
G. Chen |
| 10 |
China Mobile |
| 11 |
M. Chen |
| 12 |
BBIX, Inc. |
| 13 |
July 2015 |
| 14 |
|
| 15 |
|
| 16 |
<span class="h1">IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)</span> |
| 17 |
|
| 18 |
Abstract |
| 19 |
|
| 20 |
This document specifies a stateless solution for service providers to |
| 21 |
progressively deploy IPv6-only network domains while still offering |
| 22 |
IPv4 service to customers. The solution's distinctive properties are |
| 23 |
that TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during |
| 24 |
domain traversal and that IPv4 fragmentation rules are fully |
| 25 |
preserved end to end. Each customer can be assigned one public IPv4 |
| 26 |
address, several public IPv4 addresses, or a shared address with a |
| 27 |
restricted port set. |
| 28 |
|
| 29 |
Status of This Memo |
| 30 |
|
| 31 |
This document is not an Internet Standards Track specification; it is |
| 32 |
published for examination, experimental implementation, and |
| 33 |
evaluation. |
| 34 |
|
| 35 |
This document defines an Experimental Protocol for the Internet |
| 36 |
community. This document is a product of the Internet Engineering |
| 37 |
Task Force (IETF). It represents the consensus of the IETF |
| 38 |
community. It has received public review and has been approved for |
| 39 |
publication by the Internet Engineering Steering Group (IESG). Not |
| 40 |
all documents approved by the IESG are a candidate for any level of |
| 41 |
Internet Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 42 |
|
| 43 |
Information about the current status of this document, any errata, |
| 44 |
and how to provide feedback on it may be obtained at |
| 45 |
<a href="http://www.rfc-editor.org/info/rfc7600">http://www.rfc-editor.org/info/rfc7600</a>. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Despres, et al. Experimental [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2015 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 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 |
<span class="grey">Despres, et al. Experimental [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-5">5</a> |
| 117 |
<a href="#section-3">3</a>. The 4rd Model ...................................................<a href="#page-7">7</a> |
| 118 |
<a href="#section-4">4</a>. Protocol Specifications .........................................<a href="#page-9">9</a> |
| 119 |
<a href="#section-4.1">4.1</a>. NAT44 on CE ................................................<a href="#page-9">9</a> |
| 120 |
<a href="#section-4.2">4.2</a>. Mapping Rules and Other Domain Parameters .................<a href="#page-10">10</a> |
| 121 |
4.3. Reversible Packet Translations at Domain Entries |
| 122 |
and Exits .................................................<a href="#page-11">11</a> |
| 123 |
4.4. Address Mapping from CE IPv6 Prefixes to 4rd IPv4 |
| 124 |
Prefixes ..................................................<a href="#page-17">17</a> |
| 125 |
4.5. Address Mapping from 4rd IPv4 Addresses to 4rd |
| 126 |
IPv6 Addresses ............................................<a href="#page-19">19</a> |
| 127 |
<a href="#section-4.6">4.6</a>. Fragmentation Processing ..................................<a href="#page-23">23</a> |
| 128 |
<a href="#section-4.6.1">4.6.1</a>. Fragmentation at Domain Entry ......................<a href="#page-23">23</a> |
| 129 |
4.6.2. Ports of Fragments Addressed to |
| 130 |
Shared-Address CEs .................................<a href="#page-24">24</a> |
| 131 |
<a href="#section-4.6.3">4.6.3</a>. Packet Identifications from Shared-Address CEs .....<a href="#page-26">26</a> |
| 132 |
<a href="#section-4.7">4.7</a>. TOS and Traffic Class Processing ..........................<a href="#page-26">26</a> |
| 133 |
<a href="#section-4.8">4.8</a>. Tunnel-Generated ICMPv6 Error Messages ....................<a href="#page-27">27</a> |
| 134 |
<a href="#section-4.9">4.9</a>. Provisioning 4rd Parameters to CEs ........................<a href="#page-27">27</a> |
| 135 |
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-30">30</a> |
| 136 |
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-31">31</a> |
| 137 |
<a href="#section-7">7</a>. Relationship with Previous Works ...............................<a href="#page-31">31</a> |
| 138 |
<a href="#section-8">8</a>. References .....................................................<a href="#page-33">33</a> |
| 139 |
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-33">33</a> |
| 140 |
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-34">34</a> |
| 141 |
<a href="#appendix-A">Appendix A</a>. Textual Representation of Mapping Rules ...............<a href="#page-37">37</a> |
| 142 |
<a href="#appendix-B">Appendix B</a>. Configuring Multiple Mapping Rules ....................<a href="#page-37">37</a> |
| 143 |
<a href="#appendix-C">Appendix C</a>. Adding Shared IPv4 Addresses to an IPv6 Network .......<a href="#page-39">39</a> |
| 144 |
<a href="#appendix-C.1">C.1</a>. With CEs within CPEs .......................................<a href="#page-39">39</a> |
| 145 |
<a href="#appendix-C.2">C.2</a>. With Some CEs behind Third-Party Router CPEs ..............<a href="#page-41">41</a> |
| 146 |
<a href="#appendix-D">Appendix D</a>. Replacing Dual-Stack Routing with IPv6-Only Routing ...<a href="#page-42">42</a> |
| 147 |
<a href="#appendix-E">Appendix E</a>. Adding IPv6 and 4rd Service to a Net-10 Network .......<a href="#page-43">43</a> |
| 148 |
Acknowledgements ..................................................<a href="#page-44">44</a> |
| 149 |
Authors' Addresses ................................................<a href="#page-44">44</a> |
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Despres, et al. Experimental [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
For service providers to progressively deploy IPv6-only network |
| 172 |
domains while still offering IPv4 service to customers, the need for |
| 173 |
a stateless solution, i.e., one where no per-customer state is needed |
| 174 |
in IPv4-IPv6 gateway nodes of the provider, has been discussed in |
| 175 |
[<a href="#ref-Solutions-4v6">Solutions-4v6</a>]. This document specifies one such solution, named |
| 176 |
"4rd" for IPv4 Residual Deployment. Its distinctive properties are |
| 177 |
that TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during |
| 178 |
domain traversal and that IPv4 fragmentation rules are fully |
| 179 |
preserved end to end. |
| 180 |
|
| 181 |
Using this solution, IPv4 packets are transparently tunneled across |
| 182 |
IPv6 networks (the reverse of IPv6 Rapid Deployment on IPv4 |
| 183 |
Infrastructures (6rd) [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>], in which IPv6 packets are |
| 184 |
statelessly tunneled across IPv4 networks). |
| 185 |
|
| 186 |
While IPv6 headers are too long to be mapped into IPv4 headers (which |
| 187 |
is why 6rd requires encapsulation of full IPv6 packets in IPv4 |
| 188 |
packets), IPv4 headers can be reversibly translated into IPv6 headers |
| 189 |
in such a way that, during IPv6 domain traversal, UDP packets having |
| 190 |
checksums and TCP packets are valid IPv6 packets. IPv6-only |
| 191 |
middleboxes that perform deep packet inspection can operate on them, |
| 192 |
in particular for port inspection and web caches. |
| 193 |
|
| 194 |
In order to deal with the IPv4 address shortage, customers can be |
| 195 |
assigned shared public IPv4 addresses with statically assigned |
| 196 |
restricted port sets. As such, it is a particular application of the |
| 197 |
Address plus Port (A+P) approach [<a href="./rfc6346" title=""The Address plus Port (A+P) Approach to the IPv4 Address Shortage"">RFC6346</a>]. |
| 198 |
|
| 199 |
Deploying 4rd in networks that have enough public IPv4 addresses, |
| 200 |
customer sites can also be assigned full public IPv4 addresses. 4rd |
| 201 |
also supports scenarios where a set of public IPv4 addresses are |
| 202 |
assigned to customer sites. |
| 203 |
|
| 204 |
The design of 4rd builds on a number of previous proposals made for |
| 205 |
IPv4-via-IPv6 transition technologies (<a href="#section-7">Section 7</a>). |
| 206 |
|
| 207 |
In some use cases, IPv4-only applications of 4rd-capable customer |
| 208 |
nodes can also work with stateful NAT64s [<a href="./rfc6146" title=""Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers"">RFC6146</a>], provided these |
| 209 |
are upgraded to support 4rd tunnels in addition to their IP/ICMP |
| 210 |
translation [<a href="./rfc6145" title=""IP/ICMP Translation Algorithm"">RFC6145</a>]. The advantage is then a more complete IPv4 |
| 211 |
transparency than with double translation. |
| 212 |
|
| 213 |
How the 4rd model fits in the Internet architecture is summarized in |
| 214 |
<a href="#section-3">Section 3</a>. The protocol specifications are detailed in <a href="#section-4">Section 4</a>. |
| 215 |
Sections <a href="#section-5">5</a> and <a href="#section-6">6</a> deal with security considerations and IANA |
| 216 |
considerations, respectively. Previous proposals that influenced |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Despres, et al. Experimental [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 223 |
|
| 224 |
|
| 225 |
this specification are listed in <a href="#section-7">Section 7</a>. A few typical 4rd use |
| 226 |
cases are presented in Appendices A, B, C, D, and E. |
| 227 |
|
| 228 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 229 |
|
| 230 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 231 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 232 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 233 |
|
| 234 |
ISP: Internet Service Provider. In this document, the service it |
| 235 |
offers can be DSL, fiber-optics, cable, or mobile. The ISP can |
| 236 |
also be a private-network operator. |
| 237 |
|
| 238 |
4rd (IPv4 Residual Deployment): An extension of the IPv4 service |
| 239 |
where public IPv4 addresses can be statically shared among |
| 240 |
several customer sites, each one being assigned an exclusive |
| 241 |
port set. This service is supported across IPv6-routing |
| 242 |
domains. |
| 243 |
|
| 244 |
4rd domain (or Domain): An ISP-operated IPv6 network across which |
| 245 |
4rd is supported according to the present specification. |
| 246 |
|
| 247 |
Tunnel packet: An IPv6 packet that transparently conveys an IPv4 |
| 248 |
packet across a 4rd domain. Its header has enough information |
| 249 |
to reconstitute the IPv4 header at Domain exit. Its payload is |
| 250 |
the original IPv4 payload. |
| 251 |
|
| 252 |
CE (Customer Edge): A customer-side tunnel endpoint. It can be in a |
| 253 |
node that is a host, a router, or both. |
| 254 |
|
| 255 |
BR (Border Relay): An ISP-side tunnel endpoint. Because its |
| 256 |
operation is stateless (neither per CE nor per session state), |
| 257 |
it can be replicated in as many nodes as needed for scalability. |
| 258 |
|
| 259 |
4rd IPv6 address: IPv6 address used as the destination of a Tunnel |
| 260 |
packet sent to a CE or a BR. |
| 261 |
|
| 262 |
NAT64+: An ISP NAT64 [<a href="./rfc6146" title=""Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers"">RFC6146</a>] that is upgraded to support 4rd |
| 263 |
tunneling when IPv6 addresses it deals with are 4rd IPv6 |
| 264 |
addresses. |
| 265 |
|
| 266 |
4rd IPv4 address: A public IPv4 address or, in the case of a shared |
| 267 |
public IPv4 address, a public transport address (public IPv4 |
| 268 |
address plus port number). |
| 269 |
|
| 270 |
PSID (Port-Set Identifier): A flexible-length field that |
| 271 |
algorithmically identifies a port set. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Despres, et al. Experimental [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 279 |
|
| 280 |
|
| 281 |
4rd IPv4 prefix: A flexible-length prefix that may be a public IPv4 |
| 282 |
prefix, a public IPv4 address, or a public IPv4 address followed |
| 283 |
by a PSID. |
| 284 |
|
| 285 |
Mapping rule: A set of parameters that are used by BRs and CEs to |
| 286 |
derive 4rd IPv6 addresses from 4rd IPv4 addresses. Mapping |
| 287 |
rules are also used by each CE to derive a 4rd IPv4 prefix from |
| 288 |
an IPv6 prefix that has been delegated to it. |
| 289 |
|
| 290 |
EA bits (Embedded Address bits): Bits that are the same in a 4rd |
| 291 |
IPv4 address and in the 4rd IPv6 address derived from it. |
| 292 |
|
| 293 |
BR Mapping rule: The Mapping rule that is applicable to off-domain |
| 294 |
IPv4 addresses (addresses reachable via BRs). It can also apply |
| 295 |
to some or all CE-assigned IPv4 addresses. |
| 296 |
|
| 297 |
CE Mapping rule: A Mapping rule that is applicable only to |
| 298 |
CE-assigned IPv4 addresses (shared or not). |
| 299 |
|
| 300 |
NAT64+ Mapping rule: The Mapping rule that is applicable to IPv4 |
| 301 |
addresses reachable via a NAT64+. |
| 302 |
|
| 303 |
CNP (Checksum Neutrality Preserver): A field of 4rd IPv6 addresses |
| 304 |
that ensures that TCP-like checksums do not change when IPv4 |
| 305 |
addresses are replaced with 4rd IPv6 addresses. |
| 306 |
|
| 307 |
4rd Tag: A 16-bit tag whose value allows 4rd CEs, BRs, and NAT64+s |
| 308 |
to distinguish 4rd IPv6 addresses from other IPv6 addresses. |
| 309 |
|
| 310 |
|
| 311 |
|
| 312 |
|
| 313 |
|
| 314 |
|
| 315 |
|
| 316 |
|
| 317 |
|
| 318 |
|
| 319 |
|
| 320 |
|
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Despres, et al. Experimental [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The 4rd Model</span> |
| 338 |
|
| 339 |
4rd Domain |
| 340 |
+-----------------------------+ |
| 341 |
| IPv6 routing | |
| 342 |
| Enforced ingress filtering | +---------- |
| 343 |
... | | | |
| 344 |
| +------+ |
| 345 |
Customer site | |BR(s) | IPv4 |
| 346 |
+------------+ | BR IPv6 prefix --> |and/or| Internet |
| 347 |
| dual-stack | | |N4T64+| |
| 348 |
| +--+ | +------+ |
| 349 |
| |CE+-+ <-- a CE IPv6 prefix | | |
| 350 |
| +--+ | | +---------- |
| 351 |
| | | | |
| 352 |
+------------+ | <--IPv4 tunnels--> +------------ |
| 353 |
=> Derived | (Mesh or hub-and-spoke | |
| 354 |
4rd IPv4 prefix| topologies) | IPv6 |
| 355 |
| | Internet |
| 356 |
... | | |
| 357 |
| +------------ |
| 358 |
+-----------------------------+ |
| 359 |
<== one or several Mapping rules |
| 360 |
(e.g., announced to CEs in stateless DHCPv6) |
| 361 |
|
| 362 |
Figure 1: The 4rd Model in the Internet Architecture |
| 363 |
|
| 364 |
How the 4rd model fits in the Internet architecture is represented in |
| 365 |
Figure 1. |
| 366 |
|
| 367 |
A 4rd domain is an IPv6 network that includes one or several 4rd BRs |
| 368 |
or NAT64+s at its border with the public IPv4 Internet and that can |
| 369 |
advertise its IPv4-IPv6 Mapping rule(s) to CEs according to |
| 370 |
<a href="#section-4.9">Section 4.9</a>. |
| 371 |
|
| 372 |
BRs of a 4rd Domain are all identical as far as 4rd is concerned. In |
| 373 |
a 4rd CE, the IPv4 packets that need to reach a BR will be |
| 374 |
transformed (as detailed in <a href="#section-4.3">Section 4.3</a>) into IPv6 packets that have |
| 375 |
the same anycast IPv6 prefix, which is the 80-bit BR prefix, in their |
| 376 |
destination addresses. They are then routed to any of the BRs. The |
| 377 |
80-bit BR IPv6 prefix is an arbitrarily chosen /64 prefix from the |
| 378 |
IPv6 address space of the network operator and appended with 0x0300 |
| 379 |
(16-bit 4rd Tag; see R-9 in <a href="#section-4.5">Section 4.5</a>). |
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Despres, et al. Experimental [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 391 |
|
| 392 |
|
| 393 |
Using the Mapping rule that applies, each CE derives its 4rd IPv4 |
| 394 |
prefix from its delegated IPv6 prefix, or one of them if it has |
| 395 |
several; see <a href="#section-4.4">Section 4.4</a> for details. If the obtained IPv4 prefix |
| 396 |
has more than 32 bits, the assigned IPv4 address is shared among |
| 397 |
several CEs. Bits beyond the first 32 specify a set of ports whose |
| 398 |
use is reserved for the CE. |
| 399 |
|
| 400 |
IPv4 traffic is automatically tunneled across the Domain, in either |
| 401 |
mesh topology or hub-and-spoke topology [<a href="./rfc4925" title=""Softwire Problem Statement"">RFC4925</a>]. By default, IPv4 |
| 402 |
traffic between two CEs follows a direct IPv6 route between them |
| 403 |
(mesh topology). If the ISP configures the hub-and-spoke option, |
| 404 |
each IPv4 packet from one CE to another is routed via a BR. |
| 405 |
|
| 406 |
During Domain traversal, each tunneled TCP/UDP IPv4 packet looks like |
| 407 |
a valid TCP/UDP IPv6 packet. Thus, TCP/UDP access control lists that |
| 408 |
apply to IPv6, and possibly some other functions using deep packet |
| 409 |
inspection, also apply to IPv4. |
| 410 |
|
| 411 |
In order for IPv4 anti-spoofing protection in CEs and BRs to remain |
| 412 |
effective when combined with 4rd tunneling, ingress filtering |
| 413 |
[<a href="./rfc3704" title=""Ingress Filtering for Multihomed Networks"">RFC3704</a>] has to be in effect in IPv6 (see R-12 and <a href="#section-5">Section 5</a>). |
| 414 |
|
| 415 |
If an ISP wishes to support dynamic IPv4 address sharing in addition |
| 416 |
to or in place of 4rd stateless address sharing, it can do so by |
| 417 |
means of a stateful NAT64. By upgrading this NAT to add support for |
| 418 |
4rd tunnels, which makes it a NAT64+, CEs that are assigned no static |
| 419 |
IPv4 space can benefit from complete IPv4 transparency between the CE |
| 420 |
and the NAT64. (Without this NAT64 upgrade, IPv4 traffic is |
| 421 |
translated to IPv6 and back to IPv4, during which time the DF = |
| 422 |
MF = 1 combination for IPv4, as recommended for host fragmentation in |
| 423 |
<a href="./rfc4821#section-8">Section 8 of [RFC4821]</a>, is lost.) |
| 424 |
|
| 425 |
IPv4 packets are kept unchanged by Domain traversal, except that: |
| 426 |
|
| 427 |
o The IPv4 Time To Live (TTL), unless it is 1 or 255 at Domain |
| 428 |
entry, decreases during Domain traversal by the number of |
| 429 |
traversed routers. This is acceptable because it is undetectable |
| 430 |
end to end and also because TTL values that can be used with some |
| 431 |
protocols to test the adjacency of communicating routers are |
| 432 |
preserved [<a href="./rfc4271" title=""A Border Gateway Protocol 4 (BGP-4)"">RFC4271</a>] [<a href="./rfc5082" title=""The Generalized TTL Security Mechanism (GTSM)"">RFC5082</a>]. The effect on the traceroute |
| 433 |
utility, which uses TTL expiry to discover routers of end-to-end |
| 434 |
paths, is noted in <a href="#section-4.3">Section 4.3</a>. |
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Despres, et al. Experimental [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 447 |
|
| 448 |
|
| 449 |
o IPv4 packets whose lengths are <= 68 octets always have their |
| 450 |
"Don't Fragment" (DF) flags set to 1 at Domain exit even if they |
| 451 |
had DF = 0 at Domain entry. This is acceptable because these |
| 452 |
packets are too short to be fragmented [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>] and so their DF |
| 453 |
bits have no meaning. Besides, both [<a href="./rfc1191" title=""Path MTU discovery"">RFC1191</a>] and [<a href="./rfc4821" title=""Packetization Layer Path MTU Discovery"">RFC4821</a>] |
| 454 |
recommend that sources always set DF to 1. |
| 455 |
|
| 456 |
o Unless the Tunnel Traffic Class option applies to a Domain |
| 457 |
(<a href="#section-4.2">Section 4.2</a>), IPv4 packets may have their Type of Service (TOS) |
| 458 |
fields modified after Domain traversal (<a href="#section-4.7">Section 4.7</a>). |
| 459 |
|
| 460 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Protocol Specifications</span> |
| 461 |
|
| 462 |
This section describes detailed 4rd protocol specifications. They |
| 463 |
are mainly organized by functions. As a brief summary: |
| 464 |
|
| 465 |
o A 4rd CE MUST follow R-1, R-2, R-3, R-4, R-6, R-7, R-8, R-9, R-10, |
| 466 |
R-11, R-12, R-13, R-14, R-16, R-17, R-18, R-19, R-20, R-21, R-22, |
| 467 |
R-23, R-24, R-25, R-26, and R-27. |
| 468 |
|
| 469 |
o A 4rd BR MUST follow R-2, R-3, R-4, R-5, R-6, R-9, R-12, R-13, |
| 470 |
R-14, R-15, R-19, R-20, R-21, R-22, and R-24. |
| 471 |
|
| 472 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. NAT44 on CE</span> |
| 473 |
|
| 474 |
R-1: A CE node that is assigned a shared public IPv4 address MUST |
| 475 |
include a NAT44 [<a href="./rfc3022" title=""Traditional IP Network Address Translator (Traditional NAT)"">RFC3022</a>]. This NAT44 MUST only use external |
| 476 |
ports that are in the CE-assigned port set. |
| 477 |
|
| 478 |
NOTE: This specification only concerns IPv4 communication between |
| 479 |
IPv4-capable endpoints. For communication between IPv4-only |
| 480 |
endpoints and IPv6-only remote endpoints, the "Bump-in-the-Host" |
| 481 |
(BIH) specification [<a href="./rfc6535" title=""Dual-Stack Hosts Using "">RFC6535</a>] can be used. It can coexist in a node |
| 482 |
with the CE function, including scenarios where the IPv4-only |
| 483 |
function is a NAT44 [<a href="./rfc3022" title=""Traditional IP Network Address Translator (Traditional NAT)"">RFC3022</a>]. |
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Despres, et al. Experimental [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 503 |
|
| 504 |
|
| 505 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Mapping Rules and Other Domain Parameters</span> |
| 506 |
|
| 507 |
R-2: CEs and BRs MUST be configured with the following Domain |
| 508 |
parameters: |
| 509 |
|
| 510 |
A. One or several Mapping rules, each one comprising the |
| 511 |
following: |
| 512 |
|
| 513 |
1. Rule IPv4 prefix |
| 514 |
|
| 515 |
2. EA-bits length |
| 516 |
|
| 517 |
3. Rule IPv6 prefix |
| 518 |
|
| 519 |
4. Well-Known Ports (WKPs) authorized (OPTIONAL) |
| 520 |
|
| 521 |
B. Domain Path MTU (PMTU) |
| 522 |
|
| 523 |
C. Hub-and-spoke topology (Yes or No) |
| 524 |
|
| 525 |
D. Tunnel Traffic Class (OPTIONAL) |
| 526 |
|
| 527 |
"Rule IPv4 prefix" is used to find, by a longest match, which Mapping |
| 528 |
rule applies to a 4rd IPv4 address (<a href="#section-4.5">Section 4.5</a>). A Mapping rule |
| 529 |
whose Rule IPv4 prefix is longer than /0 is a CE Mapping rule. BR |
| 530 |
and NAT64+ Mapping rules, which must apply to all off-domain IPv4 |
| 531 |
addresses, have /0 as their Rule IPv4 prefixes. |
| 532 |
|
| 533 |
"EA-bits length" is the number of bits that are common to 4rd IPv4 |
| 534 |
addresses and 4rd IPv6 addresses derived from them. In a CE Mapping |
| 535 |
rule, it is also the number of bits that are common to a CE-delegated |
| 536 |
IPv6 prefix and the 4rd IPv4 prefix derived from it. BR and NAT64+ |
| 537 |
Mapping rules have EA-bits lengths equal to 32. |
| 538 |
|
| 539 |
"Rule IPv6 prefix" is the prefix that is used as a substitute for the |
| 540 |
Rule IPv4 prefix when a 4rd IPv6 address is derived from a 4rd IPv4 |
| 541 |
address (<a href="#section-4.5">Section 4.5</a>). In a BR Mapping rule or a NAT64+ Mapping |
| 542 |
rule, it MUST be a /80 prefix whose bits 64-79 are the 4rd Tag. |
| 543 |
|
| 544 |
"WKPs authorized" may be set for Mapping rules that assign shared |
| 545 |
IPv4 addresses to CEs. (These rules are those whose length of the |
| 546 |
Rule IPv4 prefix plus the EA-bits length exceeds 32.) If set, |
| 547 |
well-known ports may be assigned to some CEs having particular IPv6 |
| 548 |
prefixes. If not set, fairness is privileged: all IPv6 prefixes |
| 549 |
concerned with the Mapping rule have port sets having identical |
| 550 |
values (no port set includes any of the well-known ports). |
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Despres, et al. Experimental [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 559 |
|
| 560 |
|
| 561 |
"Domain PMTU" is the IPv6 Path MTU that the ISP can guarantee for all |
| 562 |
of its IPv6 paths between CEs and between BRs and CEs. It MUST be at |
| 563 |
least 1280 octets [<a href="./rfc2460" title=""Internet Protocol, Version 6 (IPv6) Specification"">RFC2460</a>]. |
| 564 |
|
| 565 |
"Hub-and-spoke topology", if set to Yes, requires CEs to tunnel all |
| 566 |
IPv4 packets via BRs. If set to No, CE-to-CE packets take the same |
| 567 |
routes as native IPv6 packets between the same CEs (mesh topology). |
| 568 |
|
| 569 |
"Tunnel Traffic Class", if provided, is the IPv6 traffic class that |
| 570 |
BRs and CEs MUST set in Tunnel packets. In this case, evolutions of |
| 571 |
the IPv6 traffic class that may occur during Domain traversal are not |
| 572 |
reflected in TOS fields of IPv4 packets at Domain exit (<a href="#section-4.7">Section 4.7</a>). |
| 573 |
|
| 574 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. Reversible Packet Translations at Domain Entries and Exits</span> |
| 575 |
|
| 576 |
R-3: Domain-entry nodes that receive IPv4 packets with IPv4 options |
| 577 |
MUST discard these packets and return ICMPv4 error messages to |
| 578 |
signal IPv4-option incompatibility (Type = 12, Code = 0, |
| 579 |
Pointer = 20) [<a href="./rfc792" title=""Internet Control Message Protocol"">RFC792</a>]. This limitation is acceptable because |
| 580 |
there are a lot of firewalls in the current IPv4 Internet that |
| 581 |
also filter IPv4 packets with IPv4 options. |
| 582 |
|
| 583 |
R-4: Domain-entry nodes that receive IPv4 packets without IPv4 |
| 584 |
options MUST convert them to Tunnel packets, with or without |
| 585 |
IPv6 fragment headers, depending on what is needed to ensure |
| 586 |
IPv4 transparency (Figure 2). Domain-exit nodes MUST convert |
| 587 |
them back to IPv4 packets. |
| 588 |
|
| 589 |
An IPv6 fragmentation header MUST be included at tunnel entry |
| 590 |
(Figure 2) if and only if one or several of the following |
| 591 |
conditions hold: |
| 592 |
|
| 593 |
* The Tunnel Traffic Class option applies to the Domain. |
| 594 |
|
| 595 |
* TTL = 1 OR TTL = 255. |
| 596 |
|
| 597 |
* The IPv4 packet is already fragmented, or may be fragmented |
| 598 |
later on, i.e., if MF = 1 OR offset > 0 OR (total length > |
| 599 |
68 AND DF = 0). |
| 600 |
|
| 601 |
In order to optimize cases where fragmentation headers are |
| 602 |
unnecessary, the NAT44 of a CE that has one SHOULD send packets |
| 603 |
with TTL = 254. |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Despres, et al. Experimental [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 615 |
|
| 616 |
|
| 617 |
R-5: In Domains whose chosen topology is hub-and-spoke, BRs that |
| 618 |
receive 4rd IPv6 packets whose embedded destination IPv4 |
| 619 |
addresses match a CE Mapping rule MUST do the equivalent of |
| 620 |
reversibly translating their headers to IPv4 and then |
| 621 |
reversibly translate them back to IPv6 as though packets would |
| 622 |
be entering the Domain. |
| 623 |
|
| 624 |
(A) Without IPv6 fragment header |
| 625 |
IPv4 packet Tunnel packet |
| 626 |
+--------------------+ : : +--------------------+ |
| 627 |
20| IPv4 Header | : <==> : | IPv6 Header | 40 |
| 628 |
+--------------------+ : : +--------------------+ |
| 629 |
| IP Payload | <==> | IP Payload | |
| 630 |
| | Layer 4 | | |
| 631 |
+--------------------+ unchanged +--------------------+ |
| 632 |
|
| 633 |
|
| 634 |
(B) With IPv6 fragment header |
| 635 |
Tunnel packet |
| 636 |
: +--------------------+ |
| 637 |
IPv4 packet : | IPv6 Header | 40 |
| 638 |
+--------------------+ : : +--------------------+ |
| 639 |
20| IPv4 Header | : <==> : |IPv6 Fragment Header| 8 |
| 640 |
+--------------------+ : : +--------------------+ |
| 641 |
| IP Payload | <==> | IP Payload | |
| 642 |
| | Layer 4 | | |
| 643 |
+--------------------+ unchanged +--------------------+ |
| 644 |
|
| 645 |
Figure 2: Reversible Packet Translation |
| 646 |
|
| 647 |
|
| 648 |
|
| 649 |
|
| 650 |
|
| 651 |
|
| 652 |
|
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Despres, et al. Experimental [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 671 |
|
| 672 |
|
| 673 |
R-6: Values to be set in IPv6 header fields at Domain entry are |
| 674 |
detailed in Table 1 (no fragment header) and Table 2 (with |
| 675 |
fragment header). Those to be set in IPv4 header fields at |
| 676 |
Domain exit are detailed in Table 3 (no fragment header) and |
| 677 |
Table 4 (with fragment header). |
| 678 |
|
| 679 |
To convey IPv4 header information that has no equivalent in |
| 680 |
IPv6, some ad hoc fields are placed in IPv6 flow labels and in |
| 681 |
Identification fields of IPv6 fragment headers, as detailed in |
| 682 |
Figure 3. |
| 683 |
|
| 684 |
|0 |4 19| |
| 685 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 686 |
| 0 | Addr_Prot_Cksm | |
| 687 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 688 |
IPv6 Flow Label |
| 689 |
|
| 690 |
0 1 2 |8 |16 31| |
| 691 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 692 |
|.|.|.| 0 | IPv4_TOS | IPv4_ID | |
| 693 |
/-+-\-\-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 694 |
/ \ TTL_255 IPv6 Identification Field |
| 695 |
IPv4_DF TTL_1 (in fragment header if needed) |
| 696 |
|
| 697 |
Figure 3: 4rd Identification Fields of IPv6 Fragment Headers |
| 698 |
|
| 699 |
|
| 700 |
+---------------------+----------------------------------------+ |
| 701 |
| IPv6 Field | Value (fields from IPv4 header) | |
| 702 |
+---------------------+----------------------------------------+ |
| 703 |
| Version | 6 | |
| 704 |
| Traffic Class | TOS | |
| 705 |
| Addr_Prot_Cksm | Sum of addresses and Protocol (Note 1) | |
| 706 |
| Payload length | Total length - 20 | |
| 707 |
| Next header | Protocol | |
| 708 |
| Hop limit | Time to Live | |
| 709 |
| Source address | See <a href="#section-4.5">Section 4.5</a> | |
| 710 |
| Destination address | See <a href="#section-4.5">Section 4.5</a> | |
| 711 |
+---------------------+----------------------------------------+ |
| 712 |
|
| 713 |
Table 1: IPv4-to-IPv6 Reversible Header Translation |
| 714 |
(without Fragment Header) |
| 715 |
|
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Despres, et al. Experimental [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 727 |
|
| 728 |
|
| 729 |
+-----------------+----------------------------------------------+ |
| 730 |
| IPv6 Field | Value (fields from IPv4 header) | |
| 731 |
+-----------------+----------------------------------------------+ |
| 732 |
| Version | 6 | |
| 733 |
| Traffic Class | TOS OR Tunnel Traffic Class (<a href="#section-4.7">Section 4.7</a>) | |
| 734 |
| Addr_Prot_Cksm | Sum of addresses and Protocol (Note 1) | |
| 735 |
| Payload length | Total length - 12 | |
| 736 |
| Next header | 44 (fragment header) | |
| 737 |
| Hop limit | IF Time to Live = 1 or 255 THEN 254 | |
| 738 |
| | ELSE Time to Live (Note 2) | |
| 739 |
| Source address | See <a href="#section-4.5">Section 4.5</a> | |
| 740 |
| Dest. address | See <a href="#section-4.5">Section 4.5</a> | |
| 741 |
| 2nd next header | Protocol | |
| 742 |
| Fragment offset | IPv4 fragment offset | |
| 743 |
| M | More Fragments flag (MF) | |
| 744 |
| IPv4_DF | Don't Fragment flag (DF) | |
| 745 |
| TTL_1 | IF Time to Live = 1 THEN 1 ELSE 0 (Note 2) | |
| 746 |
| TTL_255 | IF Time to Live = 255 THEN 1 ELSE 0 (Note 2) | |
| 747 |
| IPv4_TOS | Type of Service (TOS) | |
| 748 |
| IPv4_ID | Identification | |
| 749 |
+-----------------+----------------------------------------------+ |
| 750 |
|
| 751 |
Table 2: IPv4-to-IPv6 Reversible Header Translation |
| 752 |
(with Fragment Header) |
| 753 |
|
| 754 |
|
| 755 |
+-----------------+------------------------------------+ |
| 756 |
| IPv4 Field | Value (fields from IPv6 header) | |
| 757 |
+-----------------+------------------------------------+ |
| 758 |
| Version | 4 | |
| 759 |
| Header length | 5 | |
| 760 |
| TOS | Traffic Class | |
| 761 |
| Total length | Payload length + 20 | |
| 762 |
| Identification | 0 | |
| 763 |
| DF | 1 | |
| 764 |
| MF | 0 | |
| 765 |
| Fragment offset | 0 | |
| 766 |
| Time to Live | Hop count | |
| 767 |
| Protocol | Next header | |
| 768 |
| Header checksum | Computed as per [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>] (Note 3) | |
| 769 |
| Source address | Bits 80-111 of source address | |
| 770 |
| Dest. address | Bits 80-111 of destination address | |
| 771 |
+-----------------+------------------------------------+ |
| 772 |
|
| 773 |
Table 3: IPv6-to-IPv4 Reversible Header Translation |
| 774 |
(without Fragment Header) |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Despres, et al. Experimental [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 783 |
|
| 784 |
|
| 785 |
+-----------------------+-----------------------------------------+ |
| 786 |
| IPv4 Field | Value (fields from IPv6 header) | |
| 787 |
+-----------------------+-----------------------------------------+ |
| 788 |
| Version | 4 | |
| 789 |
| Header length | 5 | |
| 790 |
| TOS | Traffic Class OR IPv4_TOS (<a href="#section-4.7">Section 4.7</a>) | |
| 791 |
| Total length | Payload length + 12 | |
| 792 |
| Identification | IPv4_ID | |
| 793 |
| DF | IPv4_DF | |
| 794 |
| MF | M | |
| 795 |
| Fragment offset | Fragment offset | |
| 796 |
| Time to Live (Note 2) | IF TTL_255 = 1 THEN 255 | |
| 797 |
| | ELSEIF TTL_1 = 1 THEN 1 | |
| 798 |
| | ELSE hop count | |
| 799 |
| Protocol | 2nd next header | |
| 800 |
| Header checksum | Computed as per [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>] (Note 3) | |
| 801 |
| Source address | Bits 80-111 of source address | |
| 802 |
| Destination address | Bits 80-111 of destination address | |
| 803 |
+-----------------------+-----------------------------------------+ |
| 804 |
|
| 805 |
Table 4: IPv6-to-IPv4 Reversible Header Translation |
| 806 |
(with Fragment Header) |
| 807 |
|
| 808 |
NOTE 1: The need to save in the IPv6 header a checksum of both IPv4 |
| 809 |
addresses and the IPv4 protocol field results from the following |
| 810 |
facts: (1) header checksums, present in IPv4 but not in IPv6, protect |
| 811 |
addresses or protocol integrity; (2) in IPv4, ICMP messages and |
| 812 |
null-checksum UDP datagrams depend on this protection because, unlike |
| 813 |
other datagrams, they have no other address-and-protocol integrity |
| 814 |
protection. The sum MUST be performed in ordinary two's complement |
| 815 |
arithmetic. |
| 816 |
|
| 817 |
IP-layer Packet length is another field covered by the IPv4 header |
| 818 |
checksum. It is not included in the saved checksum because (1) doing |
| 819 |
so would have conflicted with [<a href="./rfc6437" title=""IPv6 Flow Label Specification"">RFC6437</a>] (flow labels must be the same |
| 820 |
in all packets of each flow); (2) ICMPv4 messages have good enough |
| 821 |
protection with their own checksums; (3) the UDP length field |
| 822 |
provides to null-checksum UDP datagrams the same level of protection |
| 823 |
after Domain traversal as without Domain traversal (consistency |
| 824 |
between IP-layer and UDP-layer lengths can be checked). |
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Despres, et al. Experimental [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 839 |
|
| 840 |
|
| 841 |
NOTE 2: TTL treatment has been chosen to permit adjacency tests |
| 842 |
between two IPv4 nodes situated at both ends of a 4rd tunnel. TTL |
| 843 |
values to be preserved for this are TTL = 255 and TTL = 1. For other |
| 844 |
values, TTL decreases between two IPv4 nodes as though the traversed |
| 845 |
IPv6 routers were IPv4 routers. |
| 846 |
|
| 847 |
The effect of this TTL treatment on IPv4 traceroute is specific: |
| 848 |
(1) the number of routers of the end-to-end path includes traversed |
| 849 |
IPv6 routers; (2) IPv6 routers of a Domain are listed after IPv4 |
| 850 |
routers of Domain entry and exit; (3) the IPv4 address shown for an |
| 851 |
IPv6 router is the IPv6-only dummy IPv4 address (<a href="#section-4.8">Section 4.8</a>); |
| 852 |
(4) the response time indicated for an IPv6 router is that of the |
| 853 |
next router. |
| 854 |
|
| 855 |
NOTE 3: Provided the sum of obtained IPv4 addresses and protocol |
| 856 |
matches Addr_Prot_Cksm. If not, the packet MUST be silently |
| 857 |
discarded. |
| 858 |
|
| 859 |
|
| 860 |
|
| 861 |
|
| 862 |
|
| 863 |
|
| 864 |
|
| 865 |
|
| 866 |
|
| 867 |
|
| 868 |
|
| 869 |
|
| 870 |
|
| 871 |
|
| 872 |
|
| 873 |
|
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Despres, et al. Experimental [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Address Mapping from CE IPv6 Prefixes to 4rd IPv4 Prefixes</span> |
| 898 |
|
| 899 |
+--------------------------------------+ |
| 900 |
| CE IPv6 prefix | |
| 901 |
+--------------------------+-----------+ |
| 902 |
: Longest match : : |
| 903 |
: with a Rule IPv6 prefix : : |
| 904 |
: || : EA-bits : |
| 905 |
: \/ : length : |
| 906 |
+--------------------------+ | : |
| 907 |
| Rule IPv6 prefix |<----'---->: |
| 908 |
+--------------------------+ : |
| 909 |
|| : : |
| 910 |
\/ : : |
| 911 |
+-----------------+-----------+ |
| 912 |
|Rule IPv4 prefix | EA bits | |
| 913 |
+-----------------+-----------+ |
| 914 |
: : |
| 915 |
+-----------------------------+ |
| 916 |
| CE 4rd IPv4 prefix | |
| 917 |
+-----------------------------+ |
| 918 |
________/ \_________ : |
| 919 |
/ \ : |
| 920 |
: ____:________________/ \__ |
| 921 |
: / : \ |
| 922 |
: <= 32 : : > 32 : |
| 923 |
+----------------+ +-----------------+----+ |
| 924 |
|IPv4 prfx or add| OR | IPv4 address |PSID| |
| 925 |
+----------------+ +-----------------+----+ |
| 926 |
: 32 : || : |
| 927 |
\/ |
| 928 |
(by default) (If WKPs authorized) |
| 929 |
: : : : |
| 930 |
+---+----+---------+ +----+-------------+ |
| 931 |
Ports in |> 0|PSID|any value| OR |PSID| any value | |
| 932 |
the CE port set +---+----+---------+ +----+-------------+ |
| 933 |
: 4 : 12 : : 16 : |
| 934 |
|
| 935 |
Figure 4: From CE IPv6 Prefix to 4rd IPv4 Address and Port Set |
| 936 |
|
| 937 |
R-7: A CE whose delegated IPv6 prefix matches the Rule IPv6 prefix |
| 938 |
of one or several Mapping rules MUST select the CE Mapping rule |
| 939 |
for which the match is the longest. It then derives its 4rd |
| 940 |
IPv4 prefix as shown in Figure 4: (1) The CE replaces the Rule |
| 941 |
IPv6 prefix with the Rule IPv4 prefix. The result is the CE |
| 942 |
4rd IPv4 prefix. (2) If this CE 4rd IPv4 prefix has less than |
| 943 |
32 bits, the CE takes it as its assigned IPv4 prefix. If it |
| 944 |
has exactly 32 bits, the CE takes it as its IPv4 address. If |
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Despres, et al. Experimental [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 951 |
|
| 952 |
|
| 953 |
it has more than 32 bits, the CE MUST take the first 32 bits as |
| 954 |
its shared public IPv4 address and bits beyond the first 32 as |
| 955 |
its Port-Set identifier (PSID). Ports of its restricted port |
| 956 |
set are by default those that have any non-zero value in their |
| 957 |
first 4 bits (the PSID offset), followed by the PSID, and |
| 958 |
followed by any values in remaining bits. If the WKP |
| 959 |
authorized option applies to the Mapping rule, there is no |
| 960 |
4-bit offset before the PSID so that all ports can be assigned. |
| 961 |
|
| 962 |
NOTE: The choice of the default PSID position in port fields |
| 963 |
has been guided by the following objectives: (1) for fairness, |
| 964 |
avoid having any of the well-known ports 0-1023 in the port set |
| 965 |
specified by any PSID value; (2) for compatibility with RTP/ |
| 966 |
RTCP [<a href="./rfc4961" title=""Symmetric RTP / RTP Control Protocol (RTCP)"">RFC4961</a>], include in each port set pairs of consecutive |
| 967 |
ports; (3) in order to facilitate operation and training, have |
| 968 |
the PSID at a fixed position in port fields; (4) in order to |
| 969 |
facilitate documentation in hexadecimal notation, and to |
| 970 |
facilitate maintenance, have this position nibble-aligned. |
| 971 |
Ports that are excluded from assignment to CEs are 0-4095, |
| 972 |
instead of just 0-1023, in a trade-off to favor nibble |
| 973 |
alignment of PSIDs and overall simplicity. |
| 974 |
|
| 975 |
R-8: A CE whose delegated IPv6 prefix has its longest match with the |
| 976 |
Rule IPv6 prefix of the BR Mapping rule MUST take as its IPv4 |
| 977 |
address the 32 bits that, in the delegated IPv6 prefix, follow |
| 978 |
this Rule IPv6 prefix. If this is the case while the hub-and- |
| 979 |
spoke option applies to the Domain, or if the Rule IPv6 prefix |
| 980 |
is not a /80, there is a configuration error in the Domain. An |
| 981 |
implementation-dependent administrative action MAY be taken. |
| 982 |
|
| 983 |
A CE whose delegated IPv6 prefix does not match the Rule IPv6 |
| 984 |
prefix of either any CE Mapping rule or the BR Mapping rule, |
| 985 |
and is in a Domain that has a NAT64+ Mapping rule, MUST be |
| 986 |
noted as having the unspecified IPv4 address. |
| 987 |
|
| 988 |
|
| 989 |
|
| 990 |
|
| 991 |
|
| 992 |
|
| 993 |
|
| 994 |
|
| 995 |
|
| 996 |
|
| 997 |
|
| 998 |
|
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Despres, et al. Experimental [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>. Address Mapping from 4rd IPv4 Addresses to 4rd IPv6 Addresses</span> |
| 1010 |
|
| 1011 |
: 32 : : 16 : \ |
| 1012 |
+----------------------------+ +---------------+ | |
| 1013 |
| IPv4 address | |Port_or_ICMP_ID| | Shared-address |
| 1014 |
+----------------------------+ +---+------+----+ | case |
| 1015 |
: Longest match : : 4 : PSID : | (PSID length |
| 1016 |
: with a Rule IPv4 prefix : :length: | of the rule > 0) |
| 1017 |
: || : : : | with WKPs |
| 1018 |
: \/ : : : | not authorized |
| 1019 |
+----------------+-----------+ +------+ | (PSID offset = 4) |
| 1020 |
|Rule IPv4 prefix|IPv4 suffix| | PSID | | |
| 1021 |
+----------------+-----------+ +------+ | |
| 1022 |
: || \_______ \____ | | | |
| 1023 |
: \/ \ \| / | |
| 1024 |
+--------------------------+--------+-----+ / |
| 1025 |
| Rule IPv6 prefix | EA bits | |
| 1026 |
+--------------------------+--------------+ |
| 1027 |
: : |
| 1028 |
+-----------------------------------------+ |
| 1029 |
| IPv6 prefix | |
| 1030 |
+-----------------------------------------+ |
| 1031 |
:\_______________________________ / \ |
| 1032 |
: ___________________\______/ \_______________ |
| 1033 |
: / \ \ |
| 1034 |
: / (CE Mapping rule) \ (BR Mapping rule) \ |
| 1035 |
: <= 64 : : 112 : |
| 1036 |
+----------+---+---+------+---+ +--------------+---+------+---+ |
| 1037 |
|CE v6 prfx| 0 |tag|v4 add|CNP| |BR IPv6 prefix|tag|v4 add|CNP| |
| 1038 |
+----------+-|-+---+------+---+ +--------------+---+------+---+ |
| 1039 |
: <= 64 : | :16 : 32 :16 : : 64 :16 : 32 :16 : |
| 1040 |
| |
| 1041 |
Padding to /64 |
| 1042 |
|
| 1043 |
Figure 5: From 4rd IPv4 Address to 4rd IPv6 Address |
| 1044 |
|
| 1045 |
|
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Despres, et al. Experimental [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
R-9: BRs, and CEs that are assigned public IPv4 addresses, shared or |
| 1066 |
not, MUST derive 4rd IPv6 addresses from 4rd IPv4 addresses via |
| 1067 |
the steps below or their functional equivalent (Figure 5 |
| 1068 |
details the shared public IPv4 address case): |
| 1069 |
|
| 1070 |
NOTE: The rules for forming 4rd-specific Interface Identifiers |
| 1071 |
(IIDs) are to obey [<a href="./rfc7136" title=""Significance of IPv6 Interface Identifiers"">RFC7136</a>]: |
| 1072 |
|
| 1073 |
"Specifications of other forms of 64-bit IIDs MUST specify how |
| 1074 |
all 64 bits are set." |
| 1075 |
|
| 1076 |
and |
| 1077 |
|
| 1078 |
"the whole IID value MUST be viewed as an opaque bit string by |
| 1079 |
third parties, except possibly in the local context." |
| 1080 |
|
| 1081 |
(1) If hub-and-spoke topology does not apply to the Domain, or |
| 1082 |
if it applies but the IPv6 address to be derived is a |
| 1083 |
source address from a CE or a destination address from a |
| 1084 |
BR, find the CE Mapping rule whose Rule IPv4 prefix has |
| 1085 |
the longest match with the IPv4 address. |
| 1086 |
|
| 1087 |
If no Mapping rule is thus obtained, take the BR Mapping |
| 1088 |
rule. |
| 1089 |
|
| 1090 |
If the obtained Mapping rule assigns IPv4 prefixes to CEs, |
| 1091 |
i.e., if the length of the Rule IPv4 prefix plus EA-bits |
| 1092 |
length is 32 - k, with k >= 0, delete the last k bits of |
| 1093 |
the IPv4 address. |
| 1094 |
|
| 1095 |
Otherwise, if the length of the Rule IPv4 prefix plus the |
| 1096 |
EA-bits length is 32 + k, with k > 0, take k as the PSID |
| 1097 |
length and append to the IPv4 address the PSID copied from |
| 1098 |
bits p to p+3 of the Port_or_ICMP_ID field where (1) p, |
| 1099 |
the PSID offset, is 4 by default and 0 if the WKPs |
| 1100 |
authorized option applies to the rule; (2) the |
| 1101 |
Port_or_ICMP_ID field is in bits of the IP payload that |
| 1102 |
depend on whether the address is source or destination, on |
| 1103 |
whether the packet is ICMP or not, and, if it is ICMP, |
| 1104 |
whether it is an error message or an Echo message. This |
| 1105 |
field is: |
| 1106 |
|
| 1107 |
a. If the packet Protocol is not ICMP, the port field |
| 1108 |
associated with the address (bits 0-15 for a source |
| 1109 |
address and bits 16-31 for a destination address). |
| 1110 |
|
| 1111 |
b. If the packet is an ICMPv4 Echo or Echo reply message, |
| 1112 |
the ICMPv4 Identification field (bits 32-47). |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Despres, et al. Experimental [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
c. If the packet is an ICMPv4 error message, the port |
| 1122 |
field associated with the address in the returned |
| 1123 |
packet header (bits 240-255 for a source address and |
| 1124 |
bits 224-239 for a destination address). |
| 1125 |
|
| 1126 |
NOTE 1: Using Identification fields of ICMP messages as |
| 1127 |
port fields permits the exchange of Echo requests and Echo |
| 1128 |
replies between shared-address CEs and IPv4 hosts having |
| 1129 |
exclusive IPv4 addresses. Echo exchanges between two |
| 1130 |
shared-address CEs remain impossible, but this is a |
| 1131 |
limitation inherent in address sharing (one reason among |
| 1132 |
many to use IPv6). |
| 1133 |
|
| 1134 |
NOTE 2: When the PSID is taken in the port fields of the |
| 1135 |
IPv4 payload, implementation is kept independent from any |
| 1136 |
particular Layer 4 protocol having such port fields by not |
| 1137 |
checking that the protocol is indeed one that has such |
| 1138 |
port fields. A packet may consequently go, in the case of |
| 1139 |
a source mistake, from a BR to a shared-address CE with a |
| 1140 |
protocol that is not supported by this CE. In this case, |
| 1141 |
the CE NAT44 returns an ICMPv4 "protocol unreachable" |
| 1142 |
error message. The IPv4 source is thus appropriately |
| 1143 |
informed of its mistake. |
| 1144 |
|
| 1145 |
(2) In the result, replace the Rule IPv4 prefix with the Rule |
| 1146 |
IPv6 prefix. |
| 1147 |
|
| 1148 |
(3) If the result is shorter than a /64, append to the result |
| 1149 |
a null padding up to 64 bits, followed by the 4rd Tag |
| 1150 |
(0x0300), and followed by the IPv4 address. |
| 1151 |
|
| 1152 |
NOTE: The 4rd Tag is a 4rd-specific mark. Its function is |
| 1153 |
to ensure that 4rd IPv6 addresses are recognizable by CEs |
| 1154 |
without any interference with the choice of subnet |
| 1155 |
prefixes in CE sites. (These choices may have been done |
| 1156 |
before 4rd is enabled.) |
| 1157 |
|
| 1158 |
For this, the 4rd Tag has its "u" and "g" bits [<a href="./rfc4291" title=""IP Version 6 Addressing Architecture"">RFC4291</a>] |
| 1159 |
both set to 1, so that they maximally differ from these |
| 1160 |
existing IPv6 address schemas. So far, u = g = 1 has not |
| 1161 |
been used in any IPv6 addressing architecture. |
| 1162 |
|
| 1163 |
With the 4rd Tag, IPv6 packets can be routed to the 4rd |
| 1164 |
function within a CE node based on a /80 prefix that no |
| 1165 |
native IPv6 address can contain. |
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Despres, et al. Experimental [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
(4) Add to the result a Checksum Neutrality Preserver (CNP). |
| 1178 |
Its value, in one's complement arithmetic, is the opposite |
| 1179 |
of the sum of 16-bit fields of the IPv6 address other than |
| 1180 |
the IPv4 address and the CNP themselves (i.e., five |
| 1181 |
consecutive fields in address bits 0-79). |
| 1182 |
|
| 1183 |
NOTE: The CNP guarantees that Tunnel packets are valid |
| 1184 |
IPv6 packets for all Layer 4 protocols that use the same |
| 1185 |
checksum algorithm as TCP. This guarantee does not depend |
| 1186 |
on where the checksum fields of these protocols are placed |
| 1187 |
in IP payloads. (Today, such protocols are UDP [<a href="./rfc768" title=""User Datagram Protocol"">RFC768</a>], |
| 1188 |
TCP [<a href="./rfc793" title=""Transmission Control Protocol"">RFC793</a>], UDP-Lite [<a href="./rfc3828" title=""The Lightweight User Datagram Protocol (UDP-Lite)"">RFC3828</a>], and the Datagram |
| 1189 |
Congestion Control Protocol (DCCP) [<a href="./rfc5595" title=""The Datagram Congestion Control Protocol (DCCP) Service Codes"">RFC5595</a>]. Should new |
| 1190 |
ones be specified, BRs will support them without needing |
| 1191 |
an update.) |
| 1192 |
|
| 1193 |
R-10: A 4rd-capable CE SHOULD, and a 4rd-enabled CE MUST, always |
| 1194 |
prohibit all addresses that use its advertised prefix and have |
| 1195 |
an IID starting with 0x0300 (4rd Tag), by using Duplicate |
| 1196 |
Address Detection [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>]. |
| 1197 |
|
| 1198 |
R-11: A CE that is assigned the unspecified IPv4 address (see |
| 1199 |
<a href="#section-4.4">Section 4.4</a>) MUST use, for packets tunneled between itself and |
| 1200 |
the Domain NAT64+, addresses as detailed in Figure 6: part (a) |
| 1201 |
for its IPv6 source, and part (b) as IPv6 destinations that |
| 1202 |
depend on IPv4 destinations. A NAT64+, being NAT64 conforming |
| 1203 |
[<a href="./rfc6146" title=""Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers"">RFC6146</a>], MUST accept IPv6 packets whose destination conforms |
| 1204 |
to Figure 6(b) (4rd Tag instead of "u" and 0x00 octets). In |
| 1205 |
its Binding Information Base, it MUST remember whether a |
| 1206 |
mapping was created with a "u" or 4rd-tag destination. In the |
| 1207 |
IPv4-to-IPv6 direction, it MUST use 4rd tunneling, with source |
| 1208 |
address conforming to Figure 6(b), when using a mapping that |
| 1209 |
was created with a 4rd-tag destination. |
| 1210 |
|
| 1211 |
+---------------------+---------+-------+-------------+------+ |
| 1212 |
(a) | CE IPv6 prefix | 0 |4rd Tag| 0 | CNP | |
| 1213 |
+---------------------+---------+-------+-------------+------+ |
| 1214 |
: <= 64 : >= 0 : 16 : 32 : 16 : |
| 1215 |
4rd IPv6 address of a CE having no public IPv4 address |
| 1216 |
|
| 1217 |
<----------- Rule IPv6 prefix --------->: |
| 1218 |
+-------------------------------+-------+-------------+------+ |
| 1219 |
(b) | NAT64+ IPv6 prefix |4rd Tag|IPv4 address | CNP | |
| 1220 |
+-------------------------------+-------+-------------+------+ |
| 1221 |
: 64 : 16 : 32 : 16 : |
| 1222 |
4rd IPv6 address of a host reachable via a NAT64+ |
| 1223 |
|
| 1224 |
Figure 6: Rules for CE and NAT64+ |
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Despres, et al. Experimental [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
R-12: For anti-spoofing protection, CEs and BRs MUST check that the |
| 1234 |
IPv6 source address of each received Tunnel packet is that |
| 1235 |
which, according to R-9, is derived from the source 4rd IPv4 |
| 1236 |
address. For this, the IPv4 address used to obtain the source |
| 1237 |
4rd IPv4 address is that embedded in the IPv6 source address |
| 1238 |
(in its bits 80-111). (This verification is needed because |
| 1239 |
IPv6 ingress filtering [<a href="./rfc3704" title=""Ingress Filtering for Multihomed Networks"">RFC3704</a>] applies only to IPv6 prefixes, |
| 1240 |
without any guarantee that Tunnel packets are built as |
| 1241 |
specified in R-9.) |
| 1242 |
|
| 1243 |
R-13: For additional protection against packet corruption at a link |
| 1244 |
layer that might be undetected at this layer during Domain |
| 1245 |
traversal, CEs and BRs SHOULD verify that source and |
| 1246 |
destination IPv6 addresses have not been modified. This can be |
| 1247 |
done by checking that they remain checksum neutral (see the |
| 1248 |
Note above regarding the CNP). |
| 1249 |
|
| 1250 |
<span class="h3"><a class="selflink" id="section-4.6" href="#section-4.6">4.6</a>. Fragmentation Processing</span> |
| 1251 |
|
| 1252 |
<span class="h4"><a class="selflink" id="section-4.6.1" href="#section-4.6.1">4.6.1</a>. Fragmentation at Domain Entry</span> |
| 1253 |
|
| 1254 |
R-14: If an IPv4 packet enters a CE or BR with a size such that the |
| 1255 |
derived Tunnel packet would be longer than the Domain PMTU, the |
| 1256 |
packet has to be either discarded or fragmented. The |
| 1257 |
Domain-entry node MUST discard it if the packet has DF = 1, |
| 1258 |
with an ICMP error message returned to the source. It MUST |
| 1259 |
fragment it otherwise, with the payload of each fragment not |
| 1260 |
exceeding PMTU - 48. The first fragment has its offset equal |
| 1261 |
to the received offset. Subsequent fragments have offsets |
| 1262 |
increased by the lengths of the payloads of previous fragments. |
| 1263 |
Functionally, fragmentation is supposed to be done in IPv4 |
| 1264 |
before applying reversible header translation to each fragment; |
| 1265 |
see <a href="#section-4.3">Section 4.3</a>. |
| 1266 |
|
| 1267 |
|
| 1268 |
|
| 1269 |
|
| 1270 |
|
| 1271 |
|
| 1272 |
|
| 1273 |
|
| 1274 |
|
| 1275 |
|
| 1276 |
|
| 1277 |
|
| 1278 |
|
| 1279 |
|
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Despres, et al. Experimental [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
<span class="h4"><a class="selflink" id="section-4.6.2" href="#section-4.6.2">4.6.2</a>. Ports of Fragments Addressed to Shared-Address CEs</span> |
| 1290 |
|
| 1291 |
Because ports are available only in the first fragments of IPv4 |
| 1292 |
fragmented packets, a BR needs a mechanism to send to the right |
| 1293 |
shared-address CEs all fragments of fragmented packets. |
| 1294 |
|
| 1295 |
For this, a BR MAY systematically reassemble fragmented IPv4 packets |
| 1296 |
before tunneling them. But this consumes large memory space, creates |
| 1297 |
opportunities for denial-of-service-attacks, and can significantly |
| 1298 |
increase forwarding delays. This is the reason for the following |
| 1299 |
requirement: |
| 1300 |
|
| 1301 |
R-15: BRs SHOULD support an algorithm whereby received IPv4 packets |
| 1302 |
can be forwarded on the fly. The following is an example of |
| 1303 |
such an algorithm: |
| 1304 |
|
| 1305 |
(1) At BR initialization, if at least one CE Mapping rule |
| 1306 |
deals with one or more shared public IPv4 addresses (i.e., |
| 1307 |
length of Rule IPv4 prefix + EA-bits length > 32), the BR |
| 1308 |
initializes an empty "IPv4 packet table" whose entries |
| 1309 |
have the following items: |
| 1310 |
|
| 1311 |
- IPv4 source |
| 1312 |
|
| 1313 |
- IPv4 destination |
| 1314 |
|
| 1315 |
- IPv4 identification |
| 1316 |
|
| 1317 |
- Destination port |
| 1318 |
|
| 1319 |
(2) When the BR receives an IPv4 packet whose matching Mapping |
| 1320 |
rule deals with one or more shared public IPv4 addresses |
| 1321 |
(i.e., length of Rule IPv4 prefix + EA-bits length > 32), |
| 1322 |
the BR searches the table for an entry whose IPv4 source, |
| 1323 |
IPv4 destination, and IPv4 identification are those of the |
| 1324 |
received packet. The BR then performs actions as detailed |
| 1325 |
in Table 5, depending on which conditions hold. |
| 1326 |
|
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
|
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Despres, et al. Experimental [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
+-----------------------------+---+---+---+---+---+---+---+---+ |
| 1346 |
| - CONDITIONS - | | | | | | | | | |
| 1347 |
| First Fragment (offset = 0) | Y | Y | Y | Y | N | N | N | N | |
| 1348 |
| Last fragment (MF = 0) | Y | Y | N | N | Y | Y | N | N | |
| 1349 |
| An entry has been found | Y | N | Y | N | Y | N | Y | N | |
| 1350 |
| ------------------------- | | | | | | | | | |
| 1351 |
| - RESULTING ACTIONS - | | | | | | | | | |
| 1352 |
| Create a new entry | - | - | - | X | - | - | - | - | |
| 1353 |
| Use port of the entry | - | - | - | - | X | - | X | - | |
| 1354 |
| Update port of the entry | - | - | X | - | - | - | - | - | |
| 1355 |
| Delete the entry | X | - | - | - | X | - | - | - | |
| 1356 |
| Forward the packet | X | X | X | X | X | - | X | - | |
| 1357 |
+-----------------------------+---+---+---+---+---+---+---+---+ |
| 1358 |
|
| 1359 |
Table 5: BR Actions |
| 1360 |
|
| 1361 |
(3) The BR performs garbage collection for table entries that |
| 1362 |
remain unchanged for longer than some limit. This limit, |
| 1363 |
which is normally longer than the maximum time normally |
| 1364 |
needed to reassemble a packet, is not critical. It should |
| 1365 |
not, however, be longer than 15 seconds [<a href="./rfc791" title=""Internet Protocol"">RFC791</a>]. |
| 1366 |
|
| 1367 |
R-16: For the above algorithm to be effective, CEs that are assigned |
| 1368 |
shared public IPv4 addresses MUST NOT interleave fragments of |
| 1369 |
several fragmented packets. |
| 1370 |
|
| 1371 |
R-17: CEs that are assigned IPv4 prefixes and are in nodes that route |
| 1372 |
public IPv4 addresses rather than only using NAT44s MUST have |
| 1373 |
the same behavior as that described just above for BRs. |
| 1374 |
|
| 1375 |
|
| 1376 |
|
| 1377 |
|
| 1378 |
|
| 1379 |
|
| 1380 |
|
| 1381 |
|
| 1382 |
|
| 1383 |
|
| 1384 |
|
| 1385 |
|
| 1386 |
|
| 1387 |
|
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Despres, et al. Experimental [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
<span class="h4"><a class="selflink" id="section-4.6.3" href="#section-4.6.3">4.6.3</a>. Packet Identifications from Shared-Address CEs</span> |
| 1402 |
|
| 1403 |
When packets go from CEs that share the same IPv4 address to a common |
| 1404 |
destination, a precaution is needed to guarantee that packet |
| 1405 |
identifications set by sources are different. Otherwise, packet |
| 1406 |
reassembly at the destination could be confused because it is based |
| 1407 |
only on source IPv4 address and Identification. The probability of |
| 1408 |
such confusing situations may in theory be very low, but a safe |
| 1409 |
solution is needed in order to avoid creating new attack |
| 1410 |
opportunities. |
| 1411 |
|
| 1412 |
R-18: A CE that is assigned a shared public IPv4 address MUST only |
| 1413 |
use packet identifications that have the CE PSID in their |
| 1414 |
bits 0 to PSID length - 1. |
| 1415 |
|
| 1416 |
R-19: A BR or a CE that receives a packet from a shared-address CE |
| 1417 |
MUST check that bits 0 to PSID length - 1 of their packet |
| 1418 |
identifications are equal to the PSID found in the source 4rd |
| 1419 |
IPv4 address. |
| 1420 |
|
| 1421 |
<span class="h3"><a class="selflink" id="section-4.7" href="#section-4.7">4.7</a>. TOS and Traffic Class Processing</span> |
| 1422 |
|
| 1423 |
IPv4 TOS and IPv6 traffic class have the same semantic, that of the |
| 1424 |
differentiated services field, or DS field, specified in [<a href="./rfc2474" title=""Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers"">RFC2474</a>] |
| 1425 |
and [<a href="./rfc6040" title=""Tunnelling of Explicit Congestion Notification"">RFC6040</a>]. Their first 6 bits contain a differentiated services |
| 1426 |
codepoint (DSCP), and their last 2 bits can convey explicit |
| 1427 |
congestion notifications (ECNs), which both may evolve during Domain |
| 1428 |
traversal. [<a href="./rfc2983" title=""Differentiated Services and Tunnels"">RFC2983</a>] discusses how the DSCP can be handled by tunnel |
| 1429 |
endpoints. The Tunnel Traffic Class option provides permission to |
| 1430 |
ignore DS-field evolutions occurring during Domain traversal, if the |
| 1431 |
desired behavior is that of generic tunnels conforming to [<a href="./rfc2473" title=""Generic Packet Tunneling in IPv6 Specification"">RFC2473</a>]. |
| 1432 |
|
| 1433 |
R-20: Unless the Tunnel Traffic Class option is configured for the |
| 1434 |
Domain, BRs and CEs MUST copy the IPv4 TOS into the IPv6 |
| 1435 |
traffic class at Domain entry and copy back the IPv6 traffic |
| 1436 |
class into the IPv4 TOS at Domain exit. |
| 1437 |
|
| 1438 |
R-21: If the Tunnel Traffic Class option is configured for a Domain, |
| 1439 |
BRs and CEs MUST at Domain entry take the configured Tunnel |
| 1440 |
Traffic Class as the IPv6 traffic class and copy the received |
| 1441 |
IPv4 TOS into the IPv4_TOS of the fragment header (Figure 3). |
| 1442 |
At Domain exit, they MUST copy back the IPv4_TOS of the |
| 1443 |
fragment header into the IPv4 TOS. |
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Despres, et al. Experimental [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
<span class="h3"><a class="selflink" id="section-4.8" href="#section-4.8">4.8</a>. Tunnel-Generated ICMPv6 Error Messages</span> |
| 1458 |
|
| 1459 |
If a Tunnel packet is discarded on its way across a 4rd domain |
| 1460 |
because of an unreachable destination, an ICMPv6 error message is |
| 1461 |
returned to the IPv6 source. For the IPv4 source of the discarded |
| 1462 |
packet to be informed of packet loss, the ICMPv6 message has to be |
| 1463 |
converted into an ICMPv4 message. |
| 1464 |
|
| 1465 |
R-22: If a CE or BR receives an ICMPv6 error message [<a href="./rfc4443" title=""Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"">RFC4443</a>], it |
| 1466 |
MUST synthesize an ICMPv4 error packet [<a href="./rfc792" title=""Internet Control Message Protocol"">RFC792</a>]. This packet |
| 1467 |
MUST contain the first 8 octets of the discarded packet's IP |
| 1468 |
payload. The reserved IPv4 dummy address (192.0.0.8/32; see |
| 1469 |
<a href="#section-6">Section 6</a>) MUST be used as its source address. |
| 1470 |
|
| 1471 |
As described in [<a href="./rfc6145" title=""IP/ICMP Translation Algorithm"">RFC6145</a>], ICMPv6 Type = 1 and Code = 0 |
| 1472 |
(Destination Unreachable, No route to destination) MUST be |
| 1473 |
translated into ICMPv4 Type = 3 and Code = 0 (Destination |
| 1474 |
Unreachable, Net unreachable), and ICMPv6 Type = 3 and Code = 0 |
| 1475 |
(Time Exceeded, Hop limit exceeded in transit) MUST be |
| 1476 |
translated into ICMPv4 Type = 11 and Code = 0 (Time Exceeded, |
| 1477 |
time to live exceeded in transit). |
| 1478 |
|
| 1479 |
<span class="h3"><a class="selflink" id="section-4.9" href="#section-4.9">4.9</a>. Provisioning 4rd Parameters to CEs</span> |
| 1480 |
|
| 1481 |
Domain parameters listed in <a href="#section-4.2">Section 4.2</a> are subject to the following |
| 1482 |
constraints: |
| 1483 |
|
| 1484 |
R-23: Each Domain MUST have a BR Mapping rule and/or a NAT64+ Mapping |
| 1485 |
rule. The BR Mapping rule is only used by CEs that are |
| 1486 |
assigned public IPv4 addresses, shared or not. The NAT64+ |
| 1487 |
Mapping rule is only used by CEs that are assigned the |
| 1488 |
unspecified IPv4 address (<a href="#section-4.4">Section 4.4</a>) and therefore need an |
| 1489 |
ISP NAT64 to reach IPv4 destinations. |
| 1490 |
|
| 1491 |
R-24: Each CE and each BR MUST support up to 32 Mapping rules. |
| 1492 |
|
| 1493 |
Support for up to 32 Mapping rules ensures that independently |
| 1494 |
acquired CEs and BR nodes can always interwork. |
| 1495 |
|
| 1496 |
ISPs that need Mapping rules for more IPv4 prefixes than this |
| 1497 |
number SHOULD split their networks into multiple Domains. |
| 1498 |
Communication between these domains can be done in IPv4 or by |
| 1499 |
some other implementation-dependent, but equivalent, means. |
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Despres, et al. Experimental [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
R-25: For mesh topologies, where CE-CE paths don't go via BRs, all |
| 1514 |
Mapping rules of the Domain MUST be sent to all CEs. For |
| 1515 |
hub-and-spoke topologies, where all CE-CE paths go via BRs, |
| 1516 |
each CE MAY be sent only the BR Mapping rule of the Domain |
| 1517 |
plus, if different, the CE Mapping rule that applies to its CE |
| 1518 |
IPv6 prefix. |
| 1519 |
|
| 1520 |
R-26: In a Domain where the chosen topology is hub-and-spoke, all CEs |
| 1521 |
MUST have IPv6 prefixes that match a CE Mapping rule. |
| 1522 |
(Otherwise, packets sent to CEs whose IPv6 prefixes would match |
| 1523 |
only the BR Mapping rule would, with longest-match selected |
| 1524 |
routes, be routed directly to these CEs. This would be |
| 1525 |
contrary to the hub-and-spoke requirement.) |
| 1526 |
|
| 1527 |
R-27: CEs MUST be able to acquire parameters of 4rd domains |
| 1528 |
(<a href="#section-4.2">Section 4.2</a>) in DHCPv6 [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>]. Formats of DHCPv6 options |
| 1529 |
to be used are detailed in Figures 7, 8, and 9, with field |
| 1530 |
values specified after each figure. |
| 1531 |
|
| 1532 |
0 1 2 3 |
| 1533 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1534 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1535 |
| option = OPTION_4RD | option-length | |
| 1536 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1537 |
| encapsulated 4rd rule options | |
| 1538 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1539 |
|
| 1540 |
Figure 7: DHCPv6 Option for 4rd |
| 1541 |
|
| 1542 |
o option code: 97, OPTION_4RD (see <a href="#section-6">Section 6</a>) |
| 1543 |
|
| 1544 |
o option-length: the length of encapsulated options, in octets |
| 1545 |
|
| 1546 |
|
| 1547 |
|
| 1548 |
|
| 1549 |
|
| 1550 |
|
| 1551 |
|
| 1552 |
|
| 1553 |
|
| 1554 |
|
| 1555 |
|
| 1556 |
|
| 1557 |
|
| 1558 |
|
| 1559 |
|
| 1560 |
|
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Despres, et al. Experimental [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
o encapsulated 4rd rule options: The OPTION_4RD DHCPv6 option |
| 1570 |
contains at least one encapsulated OPTION_4RD_MAP_RULE option and |
| 1571 |
a maximum of one encapsulated OPTION_4RD_NON_MAP_RULE option. |
| 1572 |
Since DHCP servers normally send whatever options the operator |
| 1573 |
configures, operators are advised to configure these options |
| 1574 |
appropriately. DHCP servers MAY check to see that the |
| 1575 |
configuration follows these rules and notify the operator in an |
| 1576 |
implementation-dependent manner if the settings for these options |
| 1577 |
aren't valid. The length of encapsulated options is in octets. |
| 1578 |
|
| 1579 |
0 1 2 3 |
| 1580 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1581 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1582 |
| option = OPTION_4RD_MAP_RULE | option-length | |
| 1583 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1584 |
| prefix4-len | prefix6-len | ea-len |W| Reserved | |
| 1585 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1586 |
| rule-ipv4-prefix | |
| 1587 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1588 |
| | |
| 1589 |
+ + |
| 1590 |
| rule-ipv6-prefix | |
| 1591 |
+ + |
| 1592 |
| | |
| 1593 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1594 |
|
| 1595 |
Figure 8: Encapsulated Option for Mapping-Rule Parameters |
| 1596 |
|
| 1597 |
o option code: 98, encapsulated OPTION_4RD_MAP_RULE option (see |
| 1598 |
<a href="#section-6">Section 6</a>) |
| 1599 |
|
| 1600 |
o option-length: 20 |
| 1601 |
|
| 1602 |
o prefix4-len: number of bits of the Rule IPv4 prefix |
| 1603 |
|
| 1604 |
o prefix6-len: number of bits of the Rule IPv6 prefix |
| 1605 |
|
| 1606 |
o ea-len: EA-bits length |
| 1607 |
|
| 1608 |
o W: WKP authorized, = 1 if set |
| 1609 |
|
| 1610 |
o rule-ipv4-prefix: Rule IPv4 prefix, left-aligned |
| 1611 |
|
| 1612 |
o rule-ipv6-prefix: Rule IPv6 prefix, left-aligned |
| 1613 |
|
| 1614 |
|
| 1615 |
|
| 1616 |
|
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Despres, et al. Experimental [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
0 1 2 3 |
| 1626 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1627 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1628 |
|option =OPTION_4RD_NON_MAP_RULE| option-length | |
| 1629 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1630 |
|H| 0 |T| traffic-class | domain-pmtu | |
| 1631 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1632 |
|
| 1633 |
Figure 9: Encapsulated Option for Non-Mapping-Rule Parameters |
| 1634 |
of 4rd Domains |
| 1635 |
|
| 1636 |
o option code: 99, encapsulated OPTION_4RD_NON_MAP_RULE option (see |
| 1637 |
<a href="#section-6">Section 6</a>) |
| 1638 |
|
| 1639 |
o option-length: 4 |
| 1640 |
|
| 1641 |
o H: Hub-and-spoke topology (= 1 if Yes) |
| 1642 |
|
| 1643 |
o T: Traffic Class flag (= 1 if a Tunnel Traffic Class is provided) |
| 1644 |
|
| 1645 |
o traffic-class: Tunnel Traffic Class |
| 1646 |
|
| 1647 |
o domain-pmtu: Domain PMTU (at least 1280 octets) |
| 1648 |
|
| 1649 |
Means other than DHCPv6 that may prove useful to provide 4rd |
| 1650 |
parameters to CEs are off-scope for this document. The same or |
| 1651 |
similar parameter formats would, however, be recommended to |
| 1652 |
facilitate training and operation. |
| 1653 |
|
| 1654 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 1655 |
|
| 1656 |
Spoofing attacks |
| 1657 |
|
| 1658 |
With IPv6 ingress filtering in effect in the Domain [<a href="./rfc3704" title=""Ingress Filtering for Multihomed Networks"">RFC3704</a>], as |
| 1659 |
required in <a href="#section-3">Section 3</a> (Figure 1 in particular), and with |
| 1660 |
consistency checks between 4rd IPv4 and IPv6 addresses |
| 1661 |
(<a href="#section-4.5">Section 4.5</a>), no spoofing opportunity in IPv4 is introduced by |
| 1662 |
4rd: being able to use as source IPv6 address only one that has |
| 1663 |
been allocated to him, a customer can only provide as source 4rd |
| 1664 |
IPv4 address that which derives this IPv6 address according to |
| 1665 |
<a href="#section-4.5">Section 4.5</a>, i.e., one that his ISP has allocated to him. |
| 1666 |
|
| 1667 |
Routing loop attacks |
| 1668 |
|
| 1669 |
Routing loop attacks that may exist in some "automatic tunneling" |
| 1670 |
scenarios are documented in [<a href="./rfc6324" title=""Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations"">RFC6324</a>]. No opportunities for |
| 1671 |
routing loop attacks have been identified with 4rd. |
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Despres, et al. Experimental [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Fragmentation-related attacks |
| 1682 |
|
| 1683 |
As discussed in <a href="#section-4.6">Section 4.6</a>, each BR of a Domain that assigns |
| 1684 |
shared public IPv4 addresses should maintain a dynamic table of |
| 1685 |
fragmented packets that go to these shared-address CEs. |
| 1686 |
|
| 1687 |
This leaves BRs vulnerable to denial-of-service attacks from hosts |
| 1688 |
that would send very large numbers of first fragments and would |
| 1689 |
never send last fragments having the same packet identifications. |
| 1690 |
This vulnerability is inherent in IPv4 address sharing, be it |
| 1691 |
static or dynamic. Compared to what it is with algorithms that |
| 1692 |
reassemble IPv4 packets in BRs, it is, however, significantly |
| 1693 |
mitigated by the algorithm provided in <a href="#section-4.6.2">Section 4.6.2</a>, as that |
| 1694 |
algorithm uses much less memory space. |
| 1695 |
|
| 1696 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 1697 |
|
| 1698 |
IANA has allocated the following: |
| 1699 |
|
| 1700 |
o Encapsulated options OPTION_4RD (97), OPTION_4RD_MAP_RULE (98), |
| 1701 |
and OPTION_4RD_NON_MAP_RULE (99). These options have been |
| 1702 |
recorded in the option code space of the "Dynamic Host |
| 1703 |
Configuration Protocol for IPv6 (DHCPv6)" registry. See |
| 1704 |
<a href="#section-4.9">Section 4.9</a> of this document and <a href="./rfc3315#section-24.3">Section 24.3 of [RFC3315]</a>). |
| 1705 |
|
| 1706 |
Value | Description | Reference |
| 1707 |
-----------+-------------------------+--------------- |
| 1708 |
97 | OPTION_4RD | this document |
| 1709 |
98 | OPTION_4RD_MAP_RULE | this document |
| 1710 |
99 | OPTION_4RD_NON_MAP_RULE | this document |
| 1711 |
|
| 1712 |
o Reserved IPv4 address 192.0.0.8/32 to be used as the "IPv4 dummy |
| 1713 |
address" (<a href="#section-4.8">Section 4.8</a>). |
| 1714 |
|
| 1715 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Relationship with Previous Works</span> |
| 1716 |
|
| 1717 |
The present specification has been influenced by many previous IETF |
| 1718 |
drafts, in particular those accessible at |
| 1719 |
<<a href="http://tools.ietf.org/html/draft-xxxx">http://tools.ietf.org/html/draft-xxxx</a>>, where "xxxx" refers to the |
| 1720 |
following (listed in order, by date of their first versions): |
| 1721 |
|
| 1722 |
o bagnulo-behave-nat64 (2008-06-10) |
| 1723 |
|
| 1724 |
o xli-behave-ivi (2008-07-06) |
| 1725 |
|
| 1726 |
o despres-sam-scenarios (2008-09-28) |
| 1727 |
|
| 1728 |
o boucadair-port-range (2008-10-23) |
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Despres, et al. Experimental [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
o ymbk-aplusp (2008-10-27) |
| 1738 |
|
| 1739 |
o xli-behave-divi (2009-10-19) |
| 1740 |
|
| 1741 |
o thaler-port-restricted-ip-issues (2010-02-28) |
| 1742 |
|
| 1743 |
o cui-softwire-host-4over6 (2010-07-06) |
| 1744 |
|
| 1745 |
o dec-stateless-4v6 (2011-03-05) |
| 1746 |
|
| 1747 |
o matsushima-v6ops-transition-experience (2011-03-07) |
| 1748 |
|
| 1749 |
o despres-intarea-4rd (2011-03-07) |
| 1750 |
|
| 1751 |
o deng-aplusp-experiment-results (2011-03-07) |
| 1752 |
|
| 1753 |
o operators-softwire-stateless-4v6-motivation (2011-05-05) |
| 1754 |
|
| 1755 |
o xli-behave-divi-pd (2011-07-04) |
| 1756 |
|
| 1757 |
o murakami-softwire-4rd (2011-07-04) |
| 1758 |
|
| 1759 |
o murakami-softwire-4v6-translation (2011-07-04) |
| 1760 |
|
| 1761 |
o despres-softwire-4rd-addmapping (2011-08-19) |
| 1762 |
|
| 1763 |
o boucadair-softwire-stateless-requirements (2011-09-08) |
| 1764 |
|
| 1765 |
o chen-softwire-4v6-add-format (2011-10-12) |
| 1766 |
|
| 1767 |
o mawatari-softwire-464xlat (2011-10-16) |
| 1768 |
|
| 1769 |
o mdt-softwire-map-dhcp-option (2011-10-24) |
| 1770 |
|
| 1771 |
o mdt-softwire-mapping-address-and-port (2011-10-24) |
| 1772 |
|
| 1773 |
o mdt-softwire-map-translation (2012-01-10) |
| 1774 |
|
| 1775 |
o mdt-softwire-map-encapsulation (2012-01-27) |
| 1776 |
|
| 1777 |
|
| 1778 |
|
| 1779 |
|
| 1780 |
|
| 1781 |
|
| 1782 |
|
| 1783 |
|
| 1784 |
|
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Despres, et al. Experimental [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span> |
| 1794 |
|
| 1795 |
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Normative References</span> |
| 1796 |
|
| 1797 |
[<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, |
| 1798 |
DOI 10.17487/RFC0791, September 1981, |
| 1799 |
<<a href="http://www.rfc-editor.org/info/rfc791">http://www.rfc-editor.org/info/rfc791</a>>. |
| 1800 |
|
| 1801 |
[<a id="ref-RFC792">RFC792</a>] Postel, J., "Internet Control Message Protocol", STD 5, |
| 1802 |
<a href="./rfc792">RFC 792</a>, DOI 10.17487/RFC0792, September 1981, |
| 1803 |
<<a href="http://www.rfc-editor.org/info/rfc792">http://www.rfc-editor.org/info/rfc792</a>>. |
| 1804 |
|
| 1805 |
[<a id="ref-RFC793">RFC793</a>] Postel, J., "Transmission Control Protocol", STD 7, |
| 1806 |
<a href="./rfc793">RFC 793</a>, DOI 10.17487/RFC0793, September 1981, |
| 1807 |
<<a href="http://www.rfc-editor.org/info/rfc793">http://www.rfc-editor.org/info/rfc793</a>>. |
| 1808 |
|
| 1809 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1810 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, DOI 10.17487/ |
| 1811 |
<a href="./rfc2119">RFC2119</a>, March 1997, |
| 1812 |
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>. |
| 1813 |
|
| 1814 |
[<a id="ref-RFC2460">RFC2460</a>] Deering, S. and R. Hinden, "Internet Protocol, Version 6 |
| 1815 |
(IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, DOI 10.17487/RFC2460, |
| 1816 |
December 1998, |
| 1817 |
<<a href="http://www.rfc-editor.org/info/rfc2460">http://www.rfc-editor.org/info/rfc2460</a>>. |
| 1818 |
|
| 1819 |
[<a id="ref-RFC2474">RFC2474</a>] Nichols, K., Blake, S., Baker, F., and D. Black, |
| 1820 |
"Definition of the Differentiated Services Field (DS |
| 1821 |
Field) in the IPv4 and IPv6 Headers", <a href="./rfc2474">RFC 2474</a>, |
| 1822 |
DOI 10.17487/RFC2474, December 1998, |
| 1823 |
<<a href="http://www.rfc-editor.org/info/rfc2474">http://www.rfc-editor.org/info/rfc2474</a>>. |
| 1824 |
|
| 1825 |
[<a id="ref-RFC2983">RFC2983</a>] Black, D., "Differentiated Services and Tunnels", |
| 1826 |
<a href="./rfc2983">RFC 2983</a>, DOI 10.17487/RFC2983, October 2000, |
| 1827 |
<<a href="http://www.rfc-editor.org/info/rfc2983">http://www.rfc-editor.org/info/rfc2983</a>>. |
| 1828 |
|
| 1829 |
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, |
| 1830 |
C., and M. Carney, "Dynamic Host Configuration Protocol |
| 1831 |
for IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, DOI 10.17487/RFC3315, |
| 1832 |
July 2003, |
| 1833 |
<<a href="http://www.rfc-editor.org/info/rfc3315">http://www.rfc-editor.org/info/rfc3315</a>>. |
| 1834 |
|
| 1835 |
[<a id="ref-RFC4291">RFC4291</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing |
| 1836 |
Architecture", <a href="./rfc4291">RFC 4291</a>, DOI 10.17487/RFC4291, |
| 1837 |
February 2006, |
| 1838 |
<<a href="http://www.rfc-editor.org/info/rfc4291">http://www.rfc-editor.org/info/rfc4291</a>>. |
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Despres, et al. Experimental [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
[<a id="ref-RFC4443">RFC4443</a>] Conta, A., Deering, S., and M. Gupta, Ed., "Internet |
| 1850 |
Control Message Protocol (ICMPv6) for the Internet |
| 1851 |
Protocol Version 6 (IPv6) Specification", <a href="./rfc4443">RFC 4443</a>, |
| 1852 |
DOI 10.17487/RFC4443, March 2006, |
| 1853 |
<<a href="http://www.rfc-editor.org/info/rfc4443">http://www.rfc-editor.org/info/rfc4443</a>>. |
| 1854 |
|
| 1855 |
[<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless |
| 1856 |
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, |
| 1857 |
DOI 10.17487/RFC4862, September 2007, |
| 1858 |
<<a href="http://www.rfc-editor.org/info/rfc4862">http://www.rfc-editor.org/info/rfc4862</a>>. |
| 1859 |
|
| 1860 |
[<a id="ref-RFC4925">RFC4925</a>] Li, X., Ed., Dawkins, S., Ed., Ward, D., Ed., and A. |
| 1861 |
Durand, Ed., "Softwire Problem Statement", <a href="./rfc4925">RFC 4925</a>, |
| 1862 |
DOI 10.17487/RFC4925, July 2007, |
| 1863 |
<<a href="http://www.rfc-editor.org/info/rfc4925">http://www.rfc-editor.org/info/rfc4925</a>>. |
| 1864 |
|
| 1865 |
[<a id="ref-RFC5082">RFC5082</a>] Gill, V., Heasley, J., Meyer, D., Savola, P., Ed., and C. |
| 1866 |
Pignataro, "The Generalized TTL Security Mechanism |
| 1867 |
(GTSM)", <a href="./rfc5082">RFC 5082</a>, DOI 10.17487/RFC5082, October 2007, |
| 1868 |
<<a href="http://www.rfc-editor.org/info/rfc5082">http://www.rfc-editor.org/info/rfc5082</a>>. |
| 1869 |
|
| 1870 |
[<a id="ref-RFC6040">RFC6040</a>] Briscoe, B., "Tunnelling of Explicit Congestion |
| 1871 |
Notification", <a href="./rfc6040">RFC 6040</a>, DOI 10.17487/RFC6040, |
| 1872 |
November 2010, |
| 1873 |
<<a href="http://www.rfc-editor.org/info/rfc6040">http://www.rfc-editor.org/info/rfc6040</a>>. |
| 1874 |
|
| 1875 |
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span> |
| 1876 |
|
| 1877 |
[<a id="ref-NAT444">NAT444</a>] Yamagata, I., Shirasaki, Y., Nakagawa, A., Yamaguchi, J., |
| 1878 |
and H. Ashida, "NAT444", Work in Progress, |
| 1879 |
<a href="./draft-shirasaki-nat444-06">draft-shirasaki-nat444-06</a>, July 2012. |
| 1880 |
|
| 1881 |
[<a id="ref-RFC768">RFC768</a>] Postel, J., "User Datagram Protocol", STD 6, <a href="./rfc768">RFC 768</a>, |
| 1882 |
DOI 10.17487/RFC0768, August 1980, |
| 1883 |
<<a href="http://www.rfc-editor.org/info/rfc768">http://www.rfc-editor.org/info/rfc768</a>>. |
| 1884 |
|
| 1885 |
[<a id="ref-RFC1191">RFC1191</a>] Mogul, J. and S. Deering, "Path MTU discovery", <a href="./rfc1191">RFC 1191</a>, |
| 1886 |
DOI 10.17487/RFC1191, November 1990, |
| 1887 |
<<a href="http://www.rfc-editor.org/info/rfc1191">http://www.rfc-editor.org/info/rfc1191</a>>. |
| 1888 |
|
| 1889 |
[<a id="ref-RFC1918">RFC1918</a>] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., |
| 1890 |
and E. Lear, "Address Allocation for Private Internets", |
| 1891 |
<a href="https://www.rfc-editor.org/bcp/bcp5">BCP 5</a>, <a href="./rfc1918">RFC 1918</a>, DOI 10.17487/RFC1918, February 1996, |
| 1892 |
<<a href="http://www.rfc-editor.org/info/rfc1918">http://www.rfc-editor.org/info/rfc1918</a>>. |
| 1893 |
|
| 1894 |
|
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Despres, et al. Experimental [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
[<a id="ref-RFC2473">RFC2473</a>] Conta, A. and S. Deering, "Generic Packet Tunneling in |
| 1906 |
IPv6 Specification", <a href="./rfc2473">RFC 2473</a>, DOI 10.17487/RFC2473, |
| 1907 |
December 1998, |
| 1908 |
<<a href="http://www.rfc-editor.org/info/rfc2473">http://www.rfc-editor.org/info/rfc2473</a>>. |
| 1909 |
|
| 1910 |
[<a id="ref-RFC3022">RFC3022</a>] Srisuresh, P. and K. Egevang, "Traditional IP Network |
| 1911 |
Address Translator (Traditional NAT)", <a href="./rfc3022">RFC 3022</a>, |
| 1912 |
DOI 10.17487/RFC3022, January 2001, |
| 1913 |
<<a href="http://www.rfc-editor.org/info/rfc3022">http://www.rfc-editor.org/info/rfc3022</a>>. |
| 1914 |
|
| 1915 |
[<a id="ref-RFC3704">RFC3704</a>] Baker, F. and P. Savola, "Ingress Filtering for Multihomed |
| 1916 |
Networks", <a href="https://www.rfc-editor.org/bcp/bcp84">BCP 84</a>, <a href="./rfc3704">RFC 3704</a>, DOI 10.17487/RFC3704, |
| 1917 |
March 2004, |
| 1918 |
<<a href="http://www.rfc-editor.org/info/rfc3704">http://www.rfc-editor.org/info/rfc3704</a>>. |
| 1919 |
|
| 1920 |
[<a id="ref-RFC3828">RFC3828</a>] Larzon, L-A., Degermark, M., Pink, S., Jonsson, L-E., Ed., |
| 1921 |
and G. Fairhurst, Ed., "The Lightweight User Datagram |
| 1922 |
Protocol (UDP-Lite)", <a href="./rfc3828">RFC 3828</a>, DOI 10.17487/RFC3828, |
| 1923 |
July 2004, |
| 1924 |
<<a href="http://www.rfc-editor.org/info/rfc3828">http://www.rfc-editor.org/info/rfc3828</a>>. |
| 1925 |
|
| 1926 |
[<a id="ref-RFC4271">RFC4271</a>] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., |
| 1927 |
"A Border Gateway Protocol 4 (BGP-4)", <a href="./rfc4271">RFC 4271</a>, |
| 1928 |
DOI 10.17487/RFC4271, January 2006, |
| 1929 |
<<a href="http://www.rfc-editor.org/info/rfc4271">http://www.rfc-editor.org/info/rfc4271</a>>. |
| 1930 |
|
| 1931 |
[<a id="ref-RFC4821">RFC4821</a>] Mathis, M. and J. Heffner, "Packetization Layer Path MTU |
| 1932 |
Discovery", <a href="./rfc4821">RFC 4821</a>, DOI 10.17487/RFC4821, March 2007, |
| 1933 |
<<a href="http://www.rfc-editor.org/info/rfc4821">http://www.rfc-editor.org/info/rfc4821</a>>. |
| 1934 |
|
| 1935 |
[<a id="ref-RFC4961">RFC4961</a>] Wing, D., "Symmetric RTP / RTP Control Protocol (RTCP)", |
| 1936 |
<a href="https://www.rfc-editor.org/bcp/bcp131">BCP 131</a>, <a href="./rfc4961">RFC 4961</a>, DOI 10.17487/RFC4961, July 2007, |
| 1937 |
<<a href="http://www.rfc-editor.org/info/rfc4961">http://www.rfc-editor.org/info/rfc4961</a>>. |
| 1938 |
|
| 1939 |
[<a id="ref-RFC5595">RFC5595</a>] Fairhurst, G., "The Datagram Congestion Control Protocol |
| 1940 |
(DCCP) Service Codes", <a href="./rfc5595">RFC 5595</a>, DOI 10.17487/RFC5595, |
| 1941 |
September 2009, |
| 1942 |
<<a href="http://www.rfc-editor.org/info/rfc5595">http://www.rfc-editor.org/info/rfc5595</a>>. |
| 1943 |
|
| 1944 |
[<a id="ref-RFC5969">RFC5969</a>] Townsley, W. and O. Troan, "IPv6 Rapid Deployment on IPv4 |
| 1945 |
Infrastructures (6rd) -- Protocol Specification", <a href="./rfc5969">RFC</a> |
| 1946 |
<a href="./rfc5969">5969</a>, DOI 10.17487/RFC5969, August 2010, |
| 1947 |
<<a href="http://www.rfc-editor.org/info/rfc5969">http://www.rfc-editor.org/info/rfc5969</a>>. |
| 1948 |
|
| 1949 |
[<a id="ref-RFC6145">RFC6145</a>] Li, X., Bao, C., and F. Baker, "IP/ICMP Translation |
| 1950 |
Algorithm", <a href="./rfc6145">RFC 6145</a>, DOI 10.17487/RFC6145, April 2011, |
| 1951 |
<<a href="http://www.rfc-editor.org/info/rfc6145">http://www.rfc-editor.org/info/rfc6145</a>>. |
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Despres, et al. Experimental [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
[<a id="ref-RFC6146">RFC6146</a>] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful |
| 1962 |
NAT64: Network Address and Protocol Translation from IPv6 |
| 1963 |
Clients to IPv4 Servers", <a href="./rfc6146">RFC 6146</a>, DOI 10.17487/RFC6146, |
| 1964 |
April 2011, |
| 1965 |
<<a href="http://www.rfc-editor.org/info/rfc6146">http://www.rfc-editor.org/info/rfc6146</a>>. |
| 1966 |
|
| 1967 |
[<a id="ref-RFC6324">RFC6324</a>] Nakibly, G. and F. Templin, "Routing Loop Attack Using |
| 1968 |
IPv6 Automatic Tunnels: Problem Statement and Proposed |
| 1969 |
Mitigations", <a href="./rfc6324">RFC 6324</a>, DOI 10.17487/RFC6324, August 2011, |
| 1970 |
<<a href="http://www.rfc-editor.org/info/rfc6324">http://www.rfc-editor.org/info/rfc6324</a>>. |
| 1971 |
|
| 1972 |
[<a id="ref-RFC6346">RFC6346</a>] Bush, R., Ed., "The Address plus Port (A+P) Approach to |
| 1973 |
the IPv4 Address Shortage", <a href="./rfc6346">RFC 6346</a>, DOI 10.17487/ |
| 1974 |
<a href="./rfc6346">RFC6346</a>, August 2011, |
| 1975 |
<<a href="http://www.rfc-editor.org/info/rfc6346">http://www.rfc-editor.org/info/rfc6346</a>>. |
| 1976 |
|
| 1977 |
[<a id="ref-RFC6437">RFC6437</a>] Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme, |
| 1978 |
"IPv6 Flow Label Specification", <a href="./rfc6437">RFC 6437</a>, |
| 1979 |
DOI 10.17487/RFC6437, November 2011, |
| 1980 |
<<a href="http://www.rfc-editor.org/info/rfc6437">http://www.rfc-editor.org/info/rfc6437</a>>. |
| 1981 |
|
| 1982 |
[<a id="ref-RFC6535">RFC6535</a>] Huang, B., Deng, H., and T. Savolainen, "Dual-Stack Hosts |
| 1983 |
Using "Bump-in-the-Host" (BIH)", <a href="./rfc6535">RFC 6535</a>, |
| 1984 |
DOI 10.17487/RFC6535, February 2012, |
| 1985 |
<<a href="http://www.rfc-editor.org/info/rfc6535">http://www.rfc-editor.org/info/rfc6535</a>>. |
| 1986 |
|
| 1987 |
[<a id="ref-RFC6887">RFC6887</a>] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and |
| 1988 |
P. Selkirk, "Port Control Protocol (PCP)", <a href="./rfc6887">RFC 6887</a>, |
| 1989 |
DOI 10.17487/RFC6887, April 2013, |
| 1990 |
<<a href="http://www.rfc-editor.org/info/rfc6887">http://www.rfc-editor.org/info/rfc6887</a>>. |
| 1991 |
|
| 1992 |
[<a id="ref-RFC7136">RFC7136</a>] Carpenter, B. and S. Jiang, "Significance of IPv6 |
| 1993 |
Interface Identifiers", <a href="./rfc7136">RFC 7136</a>, DOI 10.17487/RFC7136, |
| 1994 |
February 2014, |
| 1995 |
<<a href="http://www.rfc-editor.org/info/rfc7136">http://www.rfc-editor.org/info/rfc7136</a>>. |
| 1996 |
|
| 1997 |
[<a id="ref-Solutions-4v6">Solutions-4v6</a>] |
| 1998 |
Boucadair, M., Ed., Matsushima, S., Lee, Y., Bonness, O., |
| 1999 |
Borges, I., and G. Chen, "Motivations for Carrier-side |
| 2000 |
Stateless IPv4 over IPv6 Migration Solutions", Work in |
| 2001 |
Progress, <a href="./draft-ietf-softwire-stateless-4v6-motivation-05">draft-ietf-softwire-stateless-4v6-motivation-05</a>, |
| 2002 |
November 2012. |
| 2003 |
|
| 2004 |
|
| 2005 |
|
| 2006 |
|
| 2007 |
|
| 2008 |
|
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
<span class="grey">Despres, et al. Experimental [Page 36]</span></pre> |
| 2013 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span> |
| 2014 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2015 |
|
| 2016 |
|
| 2017 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Textual Representation of Mapping Rules</span> |
| 2018 |
|
| 2019 |
In the sections that follow, each Mapping rule will be represented as |
| 2020 |
follows, using 0bXXX to represent binary number XXX; square brackets |
| 2021 |
("[ ]") indicate optional items: |
| 2022 |
|
| 2023 |
{Rule IPv4 prefix, EA-bits length, Rule IPv6 prefix |
| 2024 |
[, WKPs authorized]} |
| 2025 |
|
| 2026 |
EXAMPLES: |
| 2027 |
{0.0.0.0/0, 32, 2001:db8:0:1:300::/80} |
| 2028 |
a BR Mapping rule |
| 2029 |
{198.16.0.0/14, 22, 2001:db8:4000::/34} |
| 2030 |
a CE Mapping rule |
| 2031 |
{0.0.0.0/0, 32, 2001:db8:0:1::/80} |
| 2032 |
a NAT64+ Mapping rule |
| 2033 |
{198.16.0.0/14, 22, 2001:db8:4000::/34, Yes} |
| 2034 |
a CE Mapping rule |
| 2035 |
and hub-and-spoke topology |
| 2036 |
|
| 2037 |
<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>. Configuring Multiple Mapping Rules</span> |
| 2038 |
|
| 2039 |
As far as Mapping rules are concerned, the simplest deployment model |
| 2040 |
is that in which the Domain has only one rule (the BR Mapping rule). |
| 2041 |
To assign an IPv4 address to a CE in this model, an IPv6 /112 is |
| 2042 |
assigned to it, comprising the BR /64 prefix, the 4rd Tag, and the |
| 2043 |
IPv4 address. However, this model has the following limitations: (1) |
| 2044 |
shared IPv4 addresses are not supported; (2) IPv6 prefixes used for |
| 2045 |
4rd are too long to also be used for native IPv6 addresses; (3) if |
| 2046 |
the IPv4 address space of the ISP is split with many disjoint IPv4 |
| 2047 |
prefixes, the IPv6 routing plan must be as complex as an IPv4 routing |
| 2048 |
plan based on these prefixes. |
| 2049 |
|
| 2050 |
With more Mapping rules, CE prefixes used for 4rd can be those used |
| 2051 |
for native IPv6. How to choose CE Mapping rules for a particular |
| 2052 |
deployment does not need to be standardized. |
| 2053 |
|
| 2054 |
The following is only a particular pragmatic approach that can be |
| 2055 |
used for various deployment scenarios. It is applied in some of the |
| 2056 |
use cases that follow. |
| 2057 |
|
| 2058 |
(1) Select a "Common_IPv6_prefix" that will appear at the beginning |
| 2059 |
of all 4rd CE IPv6 prefixes. |
| 2060 |
|
| 2061 |
(2) Choose all IPv4 prefixes to be used, and assign one of them to |
| 2062 |
each CE Mapping rule i. |
| 2063 |
|
| 2064 |
|
| 2065 |
|
| 2066 |
|
| 2067 |
|
| 2068 |
<span class="grey">Despres, et al. Experimental [Page 37]</span></pre> |
| 2069 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span> |
| 2070 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2071 |
|
| 2072 |
|
| 2073 |
(3) For each CE Mapping rule i, do the following: |
| 2074 |
|
| 2075 |
A. Choose the length of its Rule IPv6 prefix (possibly the same |
| 2076 |
for all CE Mapping rules). |
| 2077 |
|
| 2078 |
B. Determine its PSID_length(i). A CE Mapping rule that |
| 2079 |
assigns shared addresses with a sharing ratio of 2^Ki has |
| 2080 |
PSID_length = Ki. A CE Mapping rule that assigns IPv4 |
| 2081 |
prefixes of length L < 32 is considered to have a negative |
| 2082 |
PSID_length (PSID_length = L - 32). |
| 2083 |
|
| 2084 |
C. Derive EA-bits length(i) = 32 - L(Rule IPv4 prefix(i)) + |
| 2085 |
PSID_length(i). |
| 2086 |
|
| 2087 |
D. Derive the length of Rule_code(i), the prefix to be appended |
| 2088 |
to the common prefix to get the Rule IPv6 prefix of rule i: |
| 2089 |
|
| 2090 |
L(Rule_code(i)) = L(CE IPv6 prefix(i)) |
| 2091 |
- L(Common_IPv6_prefix) |
| 2092 |
- (32 - L(Rule IPv4 prefix(i))) |
| 2093 |
- PSID_length(i) |
| 2094 |
|
| 2095 |
E. Derive Rule_code(i) with the following constraints: (1) its |
| 2096 |
length is L(Rule_code(i)); (2) it does not overlap with any |
| 2097 |
of the previously obtained Rule_codes (for instance, 010 and |
| 2098 |
01011 do overlap, while 00, 011, and 010 do not); (3) it has |
| 2099 |
the lowest possible value as a fractional binary number (for |
| 2100 |
instance, 0100 < 10 < 11011 < 111). Thus, rules whose |
| 2101 |
Rule_code lengths are 4, 3, 5, and 2 give Rule_codes 0000, |
| 2102 |
001, 00010, and 01. |
| 2103 |
|
| 2104 |
|
| 2105 |
|
| 2106 |
|
| 2107 |
|
| 2108 |
|
| 2109 |
|
| 2110 |
|
| 2111 |
|
| 2112 |
|
| 2113 |
|
| 2114 |
|
| 2115 |
|
| 2116 |
|
| 2117 |
|
| 2118 |
|
| 2119 |
|
| 2120 |
|
| 2121 |
|
| 2122 |
|
| 2123 |
|
| 2124 |
<span class="grey">Despres, et al. Experimental [Page 38]</span></pre> |
| 2125 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span> |
| 2126 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2127 |
|
| 2128 |
|
| 2129 |
F. Take Rule IPv6 prefix(i) = the Common_IPv6_prefix followed |
| 2130 |
by Rule_code(i). |
| 2131 |
|
| 2132 |
:<--------------------- L(CE IPv6 prefix(i)) --------------------->: |
| 2133 |
: : |
| 2134 |
: 32 - L(Rule IPv4 prefix(i)) PSID_length(i): |
| 2135 |
: \ | : |
| 2136 |
: :<---------'--------><--'-->: |
| 2137 |
: : || : |
| 2138 |
: : \/ : |
| 2139 |
: :<------->:<--- EA-bits length(i) --->: |
| 2140 |
: L(Rule_code(i)) |
| 2141 |
: : : |
| 2142 |
+----------------------------+---------+ |
| 2143 |
| Common_IPv6_prefix |Rule_code| |
| 2144 |
| | (i) | |
| 2145 |
+----------------------------+---------+ |
| 2146 |
:<------ L(Rule IPv6 prefix(i)) ------>: |
| 2147 |
|
| 2148 |
Figure 10: Diagram of One Pragmatic Approach |
| 2149 |
|
| 2150 |
<span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">Appendix C</a>. Adding Shared IPv4 Addresses to an IPv6 Network</span> |
| 2151 |
|
| 2152 |
<span class="h3"><a class="selflink" id="appendix-C.1" href="#appendix-C.1">C.1</a>. With CEs within CPEs</span> |
| 2153 |
|
| 2154 |
Here, we consider an ISP that offers IPv6-only service to up to 2^20 |
| 2155 |
customers. Each customer is delegated a /56, starting with common |
| 2156 |
prefix 2001:db8:0::/36. The ISP wants to add public IPv4 service for |
| 2157 |
customers that are 4rd capable. It prefers to do so with stateless |
| 2158 |
operation in its nodes but has significantly fewer IPv4 addresses |
| 2159 |
than IPv6 addresses, so a sharing ratio is necessary. |
| 2160 |
|
| 2161 |
The only IPv4 prefixes it can use are 192.8.0.0/15, 192.4.0.0/16, |
| 2162 |
192.2.0.0/16, and 192.1.0.0/16 (neither overlapping nor |
| 2163 |
aggregatable). This gives 2^(32 - 15) + 3 * 2^(32 - 16) IPv4 |
| 2164 |
addresses, i.e., 2^18 + 2^16. For the 2^20 customers to have the |
| 2165 |
same sharing ratio, the number of IPv4 addresses to be shared has to |
| 2166 |
be a power of 2. The ISP can therefore give up using one of its |
| 2167 |
/16s, say the last one. (Whether or not it could be motivated to |
| 2168 |
return it to its Internet Registry is off-scope for this document.) |
| 2169 |
The sharing ratio to apply is then 2^20 / 2^18 = 2^2 = 4, giving a |
| 2170 |
PSID length of 2. |
| 2171 |
|
| 2172 |
|
| 2173 |
|
| 2174 |
|
| 2175 |
|
| 2176 |
|
| 2177 |
|
| 2178 |
|
| 2179 |
|
| 2180 |
<span class="grey">Despres, et al. Experimental [Page 39]</span></pre> |
| 2181 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span> |
| 2182 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2183 |
|
| 2184 |
|
| 2185 |
Applying the principles of <a href="#appendix-B">Appendix B</a> with L(Common_IPv6_prefix) = |
| 2186 |
36, L(PSID) = 2 for all rules, and L(CE IPv6 prefix(i)) = 56 for all |
| 2187 |
rules, Rule_codes and Rule IPv6 prefixes are as follows: |
| 2188 |
|
| 2189 |
+--------------+--------+-----------+-----------+-------------------+ |
| 2190 |
| CE Rule IPv4 | EA | Rule-Code | Code | CE Rule IPv6 | |
| 2191 |
| prefix | bits | length | (binary) | prefix | |
| 2192 |
| | length | | | | |
| 2193 |
+--------------+--------+-----------+-----------+-------------------+ |
| 2194 |
| 192.8.0.0/15 | 19 | 1 | 0 | 2001:db8:0::/37 | |
| 2195 |
| 192.4.0.0/16 | 18 | 2 | 10 | 2001:db8:800::/38 | |
| 2196 |
| 192.2.0.0/16 | 18 | 2 | 11 | 2001:db8:c00::/38 | |
| 2197 |
+--------------+--------+-----------+-----------+-------------------+ |
| 2198 |
|
| 2199 |
Mapping rules are then the following: |
| 2200 |
|
| 2201 |
{192.8.0.0/15, 19, 2001:0db8:0000::/37} |
| 2202 |
{192.4.0.0/16, 18, 2001:0db8:0800::/38} |
| 2203 |
{192.2.0.0/16, 18, 2001:0db8:0c00::/38} |
| 2204 |
{0.0.0.0/0, 32, 2001:0db8:0000:0001:300::/80} |
| 2205 |
|
| 2206 |
The CE whose IPv6 prefix is, for example, 2001:db8:0bbb:bb00::/56 |
| 2207 |
derives its IPv4 address and its port set as follows (<a href="#section-4.4">Section 4.4</a>): |
| 2208 |
|
| 2209 |
CE IPv6 prefix : 2001:0db8:0bbb:bb00::/56 |
| 2210 |
Rule IPv6 prefix(i): 2001:0db8:0800::/38 (longest match) |
| 2211 |
EA-bits length(i) : 18 |
| 2212 |
EA bits : 0b11 1011 1011 1011 1011 |
| 2213 |
Rule IPv4 prefix(i): 0b1100 0000 0000 0100 (192.4.0.0/16) |
| 2214 |
IPv4 address : 0b1100 0000 0000 0100 1110 1110 1110 1110 |
| 2215 |
: 192.4.238.238 |
| 2216 |
PSID : 0b11 |
| 2217 |
Ports : 0bYYYY 11XX XXXX XXXX |
| 2218 |
with YYYY > 0, and X...X any value |
| 2219 |
|
| 2220 |
|
| 2221 |
|
| 2222 |
|
| 2223 |
|
| 2224 |
|
| 2225 |
|
| 2226 |
|
| 2227 |
|
| 2228 |
|
| 2229 |
|
| 2230 |
|
| 2231 |
|
| 2232 |
|
| 2233 |
|
| 2234 |
|
| 2235 |
|
| 2236 |
<span class="grey">Despres, et al. Experimental [Page 40]</span></pre> |
| 2237 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span> |
| 2238 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2239 |
|
| 2240 |
|
| 2241 |
An IPv4 packet sent to address 192.4.238.238 and port 7777 is |
| 2242 |
tunneled to the IPv6 address obtained as follows (<a href="#section-4.5">Section 4.5</a>): |
| 2243 |
|
| 2244 |
IPv4 address : 192.4.238.238 (0xc004 eeee) |
| 2245 |
: 0b1100 0000 0000 0100 1110 1110 1110 1110 |
| 2246 |
Rule IPv4 prefix(i): 192.4.0.0/16 (longest match) |
| 2247 |
: 0b1100 0000 0000 0100 |
| 2248 |
IPv4 suffix(i) : 0b1110 1110 1110 1110 |
| 2249 |
EA-bits length(i) : 18 |
| 2250 |
PSID length(i) : 2 (= 16 + 18 - 32) |
| 2251 |
Port field : 0b 0001 1110 0110 0001 (7777) |
| 2252 |
PSID : 0b11 |
| 2253 |
Rule IPv6 prefix(i): 2001:0db8:0800::/38 |
| 2254 |
CE IPv6 prefix : 2001:0db8:0bbb:bb00::/56 |
| 2255 |
IPv6 address : 2001:0db8:0bbb:bb00:300:c004:eeee:YYYY |
| 2256 |
with YYYY = the computed CNP |
| 2257 |
|
| 2258 |
<span class="h3"><a class="selflink" id="appendix-C.2" href="#appendix-C.2">C.2</a>. With Some CEs behind Third-Party Router CPEs</span> |
| 2259 |
|
| 2260 |
We now consider an ISP that has the same need as the ISP described in |
| 2261 |
the previous section, except that (1) instead of using only its own |
| 2262 |
IPv6 infrastructure, it uses that of a third-party provider and (2) |
| 2263 |
some of its customers use this provider's Customer Premises Equipment |
| 2264 |
(CPEs) so that they can use specific services offered by the |
| 2265 |
provider. In these CPEs, a non-zero index is used to route IPv6 |
| 2266 |
packets to the physical port to which CEs are attached, say 0x2. |
| 2267 |
Each such CPE delegates to the CE nodes the customer-site IPv6 prefix |
| 2268 |
followed by this index. |
| 2269 |
|
| 2270 |
The ISP is supposed to have the same IPv4 prefixes as those in the |
| 2271 |
previous use case -- 192.8.0.0/15, 192.4.0.0/16, and 192.2.0.0/16 -- |
| 2272 |
and to use the same Common_IPv6_prefix, 2001:db8:0::/36. |
| 2273 |
|
| 2274 |
We also assume that only a minority of customers use third-party |
| 2275 |
CPEs, so that it is sufficient to use only one of the two /16s for |
| 2276 |
them. |
| 2277 |
|
| 2278 |
Mapping rules are then (see <a href="#appendix-C.1">Appendix C.1</a>): |
| 2279 |
|
| 2280 |
{192.8.0.0/15, 19, 2001:0db8:0000::/37} |
| 2281 |
{192.4.0.0/16, 18, 2001:0db8:0800::/38} |
| 2282 |
{192.2.0.0/16, 18, 2001:0db8:0c00::/38} |
| 2283 |
{0.0.0.0/0, 32, 2001:0db8:0000:0001:300::/80} |
| 2284 |
|
| 2285 |
CEs that are behind third-party CPEs derive their own IPv4 addresses |
| 2286 |
and port sets as described in <a href="#appendix-C.1">Appendix C.1</a>. |
| 2287 |
|
| 2288 |
|
| 2289 |
|
| 2290 |
|
| 2291 |
|
| 2292 |
<span class="grey">Despres, et al. Experimental [Page 41]</span></pre> |
| 2293 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span> |
| 2294 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2295 |
|
| 2296 |
|
| 2297 |
In a BR, and also in a CE if the topology is mesh, the IPv6 address |
| 2298 |
that is derived from IPv4 address 192.4.238.238 and port 7777 is |
| 2299 |
obtained as described in the previous section, except for the last |
| 2300 |
two steps, which are modified as follows: |
| 2301 |
|
| 2302 |
IPv4 address : 192.4.238.238 (0xc004 eeee) |
| 2303 |
: 0b1100 0000 0000 0100 1110 1110 1110 1110 |
| 2304 |
Rule IPv4 prefix(i): 192.4.0.0/16 (longest match) |
| 2305 |
: 0b1100 0000 0000 0100 |
| 2306 |
IPv4 suffix(i) : 0b1110 1110 1110 1110 |
| 2307 |
EA-bits length(i) : 18 |
| 2308 |
PSID length(i) : 2 (= 16 + 18 - 32) |
| 2309 |
Port field : 0b 0001 1110 0110 0001 (7777) |
| 2310 |
PSID : 0b11 |
| 2311 |
Rule IPv6 prefix(i): 2001:0db8:0800::/38 |
| 2312 |
CE IPv6 prefix : 2001:0db8:0bbb:bb00::/60 |
| 2313 |
IPv6 address : 2001:0db8:0bbb:bb00:300:192.4.238.238:YYYY |
| 2314 |
with YYYY = the computed CNP |
| 2315 |
|
| 2316 |
<span class="h2"><a class="selflink" id="appendix-D" href="#appendix-D">Appendix D</a>. Replacing Dual-Stack Routing with IPv6-Only Routing</span> |
| 2317 |
|
| 2318 |
In this use case, we consider an ISP that offers IPv4 service with |
| 2319 |
public addresses individually assigned to its customers. It also |
| 2320 |
offers IPv6 service, as it has deployed dual-stack routing. Because |
| 2321 |
it provides its own CPEs to customers, it can upgrade all of its CPEs |
| 2322 |
to support 4rd. It wishes to take advantage of this capability to |
| 2323 |
replace dual-stack routing with IPv6-only routing, without changing |
| 2324 |
any IPv4 address or IPv6 prefix. |
| 2325 |
|
| 2326 |
For this, the ISP can use the single-rule model described at the |
| 2327 |
beginning of <a href="#appendix-B">Appendix B</a>. If the prefix routed to BRs is chosen to |
| 2328 |
start with 2001:db8:0:1::/64, this rule is: |
| 2329 |
|
| 2330 |
{0.0.0.0/0, 32, 2001:db8:0:1:300::/80} |
| 2331 |
|
| 2332 |
All that is needed in the network before disabling IPv4 routing is |
| 2333 |
the following: |
| 2334 |
|
| 2335 |
o In all routers, where there is an IPv4 route toward x.x.x.x/n, add |
| 2336 |
a parallel route toward 2001:db8:0:1:300:x.x.x.x::/(80+n). |
| 2337 |
|
| 2338 |
o Where IPv4 address x.x.x.x was assigned to a CPE, now delegate |
| 2339 |
IPv6 prefix 2001:db8:0:1:300:x.x.x.x::/112. |
| 2340 |
|
| 2341 |
|
| 2342 |
|
| 2343 |
|
| 2344 |
|
| 2345 |
|
| 2346 |
|
| 2347 |
|
| 2348 |
<span class="grey">Despres, et al. Experimental [Page 42]</span></pre> |
| 2349 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span> |
| 2350 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2351 |
|
| 2352 |
|
| 2353 |
NOTE: In parallel with this deployment, or after it, shared IPv4 |
| 2354 |
addresses can be assigned to IPv6 customers. It is sufficient that |
| 2355 |
IPv4 prefixes used for this be different from those used for |
| 2356 |
exclusive-address assignments. Under this constraint, Mapping rules |
| 2357 |
can be set up according to the same principles as those described in |
| 2358 |
<a href="#appendix-C">Appendix C</a>. |
| 2359 |
|
| 2360 |
<span class="h2"><a class="selflink" id="appendix-E" href="#appendix-E">Appendix E</a>. Adding IPv6 and 4rd Service to a Net-10 Network</span> |
| 2361 |
|
| 2362 |
In this use case, we consider an ISP that has only deployed IPv4, |
| 2363 |
possibly because some of its network devices are not yet IPv6 |
| 2364 |
capable. Because it did not have enough IPv4 addresses, it has |
| 2365 |
assigned private IPv4 addresses [<a href="./rfc1918" title=""Address Allocation for Private Internets"">RFC1918</a>] to customers, say 10.x.x.x. |
| 2366 |
It thus supports up to 2^24 customers (a "Net-10" network, using the |
| 2367 |
NAT444 model [<a href="#ref-NAT444" title=""NAT444"">NAT444</a>]). |
| 2368 |
|
| 2369 |
Now, it wishes to offer IPv6 service without further delay, using 6rd |
| 2370 |
[<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>]. It also wishes to offer incoming IPv4 connectivity to its |
| 2371 |
customers with a simpler solution than that provided by the Port |
| 2372 |
Control Protocol (PCP) [<a href="./rfc6887" title=""Port Control Protocol (PCP)"">RFC6887</a>]. |
| 2373 |
|
| 2374 |
This appendix describes an example that adds IPv6 (using 6rd) and 4rd |
| 2375 |
services to the "Net-10" private IPv4 network. |
| 2376 |
|
| 2377 |
The IPv6 prefix to be used for 6rd is supposed to be 2001:db8::/32, |
| 2378 |
and the public IPv4 prefix to be used for shared addresses is |
| 2379 |
supposed to be 198.16.0.0/16 (0xc610). The resulting sharing ratio |
| 2380 |
is 2^24 / 2^(32 - 16) = 256, giving a PSID length of 8. |
| 2381 |
|
| 2382 |
The ISP installs one or several BRs at its border to the public IPv4 |
| 2383 |
Internet. They support 6rd, and 4rd above it. The BR prefix /64 is |
| 2384 |
supposed to be that which is derived from IPv4 address 10.0.0.1 |
| 2385 |
(i.e., 2001:db8:0:100:/64). |
| 2386 |
|
| 2387 |
In accordance with [<a href="./rfc5969" title=""IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification"">RFC5969</a>], 6rd BRs are configured with the |
| 2388 |
following parameters: IPv4MaskLen = 8; 6rdPrefix = 2001:db8::/32; |
| 2389 |
6rdBRIPv4Address = 192.168.0.1 (0xc0a80001). |
| 2390 |
|
| 2391 |
4rd Mapping rules are then the following: |
| 2392 |
|
| 2393 |
{198.16.0.0/16, 24, 2001:db8:0:0:300::/80} |
| 2394 |
{0.0.0.0/0, 32, 2001:db8:0:100:300:/80,} |
| 2395 |
|
| 2396 |
Any customer device that supports 4rd in addition to 6rd can then use |
| 2397 |
its assigned shared IPv4 address with 240 assigned ports. |
| 2398 |
|
| 2399 |
|
| 2400 |
|
| 2401 |
|
| 2402 |
|
| 2403 |
|
| 2404 |
<span class="grey">Despres, et al. Experimental [Page 43]</span></pre> |
| 2405 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span> |
| 2406 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2407 |
|
| 2408 |
|
| 2409 |
If its NAT44 supports port forwarding to provide incoming IPv4 |
| 2410 |
connectivity (statically, or dynamically with Universal Plug and Play |
| 2411 |
(UPnP) and/or the NAT Port Mapping Protocol (NAT-PMP)), it can use it |
| 2412 |
with ports of the assigned port set (a possibility that does not |
| 2413 |
exist in Net-10 networks without 4rd/6rd). |
| 2414 |
|
| 2415 |
Acknowledgements |
| 2416 |
|
| 2417 |
This specification has benefited over several years from independent |
| 2418 |
proposals, questions, comments, constructive suggestions, and useful |
| 2419 |
criticisms from numerous IETF contributors. The authors would like |
| 2420 |
to express recognition of all of these contributors, and especially |
| 2421 |
the following, in alphabetical order by their first names: Behcet |
| 2422 |
Sarikaya, Bing Liu, Brian Carpenter, Cameron Byrne, Congxiao Bao, Dan |
| 2423 |
Wing, Derek Atkins, Erik Kline, Francis Dupont, Gabor Bajko, Hui |
| 2424 |
Deng, Jacni Quin (who was an active coauthor of some earlier versions |
| 2425 |
of this specification), James Huang, Jan Zorz, Jari Arkko, Kathleen |
| 2426 |
Moriarty, Laurent Toutain, Leaf Yeh, Lorenzo Colitti, Marcello |
| 2427 |
Bagnulo, Mark Townsley, Mohamed Boucadair, Nejc Skoberne, Olaf |
| 2428 |
Maennel, Ole Troan, Olivier Vautrin, Peng Wu, Qiong Sun, Rajiv Asati, |
| 2429 |
Ralph Droms, Randy Bush, Satoru Matsushima, Simon Perreault, Stuart |
| 2430 |
Cheshire, Suresh Krishnan, Ted Lemon, Teemu Savolainen, Tetsuya |
| 2431 |
Murakami, Tina Tsou, Tomek Mrugalski, Washam Fan, Wojciech Dec, |
| 2432 |
Xiaohong Deng, Xing Li, and Yu Fu. |
| 2433 |
|
| 2434 |
Authors' Addresses |
| 2435 |
|
| 2436 |
Remi Despres |
| 2437 |
RD-IPtech |
| 2438 |
3 rue du President Wilson |
| 2439 |
Levallois |
| 2440 |
France |
| 2441 |
|
| 2442 |
Email: [email protected] |
| 2443 |
|
| 2444 |
|
| 2445 |
Sheng Jiang (editor) |
| 2446 |
Huawei Technologies Co., Ltd |
| 2447 |
Q14, Huawei Campus, No. 156 BeiQing Road |
| 2448 |
Hai-Dian District, Beijing 100095 |
| 2449 |
China |
| 2450 |
|
| 2451 |
Email: [email protected] |
| 2452 |
|
| 2453 |
|
| 2454 |
|
| 2455 |
|
| 2456 |
|
| 2457 |
|
| 2458 |
|
| 2459 |
|
| 2460 |
<span class="grey">Despres, et al. Experimental [Page 44]</span></pre> |
| 2461 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span> |
| 2462 |
<span class="grey"><a href="./rfc7600">RFC 7600</a> Stateless IPv4 Residual Deployment (4rd) July 2015</span> |
| 2463 |
|
| 2464 |
|
| 2465 |
Reinaldo Penno |
| 2466 |
Cisco Systems, Inc. |
| 2467 |
170 West Tasman Drive |
| 2468 |
San Jose, CA 95134 |
| 2469 |
United States |
| 2470 |
|
| 2471 |
Email: [email protected] |
| 2472 |
|
| 2473 |
|
| 2474 |
Yiu Lee |
| 2475 |
Comcast |
| 2476 |
One Comcast Center |
| 2477 |
Philadelphia, PA 19103 |
| 2478 |
United States |
| 2479 |
|
| 2480 |
Email: [email protected] |
| 2481 |
|
| 2482 |
|
| 2483 |
Gang Chen |
| 2484 |
China Mobile |
| 2485 |
29, Jinrong Avenue |
| 2486 |
Xicheng District, Beijing 100033 |
| 2487 |
China |
| 2488 |
|
| 2489 |
Email: [email protected], [email protected] |
| 2490 |
|
| 2491 |
|
| 2492 |
Maoke Chen (a.k.a. Noriyuki Arai) |
| 2493 |
BBIX, Inc. |
| 2494 |
Tokyo Shiodome Building, Higashi-Shimbashi 1-9-1 |
| 2495 |
Minato-ku, Tokyo 105-7310 |
| 2496 |
Japan |
| 2497 |
|
| 2498 |
Email: [email protected] |
| 2499 |
|
| 2500 |
|
| 2501 |
|
| 2502 |
|
| 2503 |
|
| 2504 |
|
| 2505 |
|
| 2506 |
|
| 2507 |
|
| 2508 |
|
| 2509 |
|
| 2510 |
|
| 2511 |
|
| 2512 |
|
| 2513 |
|
| 2514 |
|
| 2515 |
|
| 2516 |
Despres, et al. Experimental [Page 45] |
| 2517 |
</pre> |