idnits 2.17.1 draft-matsuhira-m46e-fp-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 26 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 14, 2017) is 2419 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC2453' is mentioned on line 682, but not defined == Missing Reference: 'RFC2080' is mentioned on line 669, but not defined == Missing Reference: 'RFC2328' is mentioned on line 678, but not defined == Missing Reference: 'RFC2740' is mentioned on line 686, but not defined ** Obsolete undefined reference: RFC 2740 (Obsoleted by RFC 5340) == Missing Reference: 'RFC1195' is mentioned on line 665, but not defined == Missing Reference: 'RFC5308' is mentioned on line 694, but not defined == Missing Reference: 'RFC2893' is mentioned on line 690, but not defined ** Obsolete undefined reference: RFC 2893 (Obsoleted by RFC 4213) == Missing Reference: 'RFC2267' is mentioned on line 673, but not defined ** Obsolete undefined reference: RFC 2267 (Obsoleted by RFC 2827) Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group N. Matsuhira 3 Internet-Draft Fujitsu Limited 4 Intended status: Informational August 14, 2017 5 Expires: February 15, 2018 7 Multiple IPv4 - IPv6 address mapping encapsulation - fixed prefix 8 (M46E-FP) 9 draft-matsuhira-m46e-fp-03 11 Abstract 13 This document specifies Multiple IPv4 - IPv6 address mapping 14 encapsulation - fixed prefix (M46E-FP) specification. M46E-FP makes 15 backbone network to IPv6 only. And also, M46E-FP can stack many IPv4 16 networks, i.e. the networks using same IPv4 (private) addresses, 17 without interdependence. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on February 15, 2018. 42 Copyright Notice 44 Copyright (c) 2017 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. Architecture of M46E-FP . . . . . . . . . . . . . . . . . . . 3 61 3. Basic Network Configuration . . . . . . . . . . . . . . . . . 5 62 4. Basic Function of M46E-FP . . . . . . . . . . . . . . . . . . 6 63 4.1. IPv4 over IPv6 Encapsulation / Decapsulation . . . . . . . 6 64 4.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 7 65 4.3. Route Advertisement . . . . . . . . . . . . . . . . . . . 8 66 5. Stacking IPv4 Networks . . . . . . . . . . . . . . . . . . . . 9 67 6. Redundancy of M46E-FP . . . . . . . . . . . . . . . . . . . . 9 68 7. Example of M46E-FP Operation . . . . . . . . . . . . . . . . . 10 69 7.1. Basic M46E-FP Operation . . . . . . . . . . . . . . . . . 10 70 7.2. M46E-FP Operation with plane ID . . . . . . . . . . . . . 12 71 8. Characteristic . . . . . . . . . . . . . . . . . . . . . . . . 15 72 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 73 10. Security Considerations . . . . . . . . . . . . . . . . . . . 16 74 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 75 11.1. Normative References . . . . . . . . . . . . . . . . . . . 16 76 11.2. References . . . . . . . . . . . . . . . . . . . . . . . . 17 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 17 79 1. Introduction 81 This document provides Multiple IPv4 - IPv6 address maping 82 encapsulation - fixed prefix (M46E-FP) specification. 84 The basic strategy for IPv6 deployment is dual stack. Viewing this 85 strategy from operational side, operation cost of dual stack is 86 higher than single stack operation. Viewing from future, IPv6 only 87 operation is more reasonable rather than IPv4 only operation. 88 Therefore IPv6 only operation is desired. 90 M46E-FP makes backbone network to IPv6 only and privide IPv4 91 connectivities. And also, M46E-FP can stack many IPv4 networks, i.e. 92 the networks using same IPv4 (private) address, without 93 interdependence. 95 2. Architecture of M46E-FP 97 IP address contain two information, one is locator information, and 98 another is identifier information. This is basic architecture of 99 internet protocol, and also the Internet, and no difference between 100 IPv4 and IPv6. 102 Locater is a information related "Where", and indentifier is a 103 information related "Who". That mean, IP address's semantics is 104 "Where's Who" meaning. Host is identified whole IP address 105 information, that is "Where's Who", however route to the host is 106 identified just locator information in IP address, that is "Where". 107 See Figure 1. 109 |<------ IP address ------------------>| 110 |<----- Locator ----->|<--Identifier-->| 111 (Where ) (Who) 112 +---------------------+----------------+ 113 | | | 114 +---------------------+----------------+ 116 Figure 1 118 In IPv4 address space, some host has IPv4 address, which consist n 119 bits length identifier and 32 - n bits locator. In Where's Who 120 representation, 32 - n bits "Where" and n bits "Who". 122 Keeping such "Where's Who" relation, IPv4 address can be represent as 123 IPv6 address by expanding "Where" information from 32 - n bits to 128 124 - n bits. Expanding " Where" information, IPv4 address can be mapped 125 to IPv6 address. Figure 2 shows such expanding. 127 |<------------------------ 128 bits ----------------------------->| 128 |<-------------------- 96 bits ------------------->|<-- 32 bits ->| 129 | : | 130 | : | 131 | +-------:------+ 132 | | IPv4 address | 133 | +-------:------+ 134 | |<-Loc->:<-ID->| 135 | | 32-n : n | 136 | | bits : bits | 137 | | : | 138 +--------------------------------------------------+-------:------+ 139 | M46A prefix (no IPv4 network plane ID) | IPv4 address | 140 +--------------------------------------------------+-------:------+ 141 | : | 142 |<------------- Locator (128 - n bits ) ------------------>:<-ID->| 143 | : n | 144 | : bits | 146 Figure 2 148 IPv4 address space contain private address, that is non globally 149 unique IP address. If some identifier which distinguish private 150 address can introduce in IPv6 address space, we can treate IPv4 151 private address as different address in IPv6 address space. This 152 document define such identifier as "IPv4 network plane ID". "IPv6 153 network plane ID" can provide VPN (Virtual Private Network) like 154 service. 156 That is M46A. In M46E-FP address, "Where" information's bit length is 157 128 -n bits, and "Who" information's bit length is n bits. Figure 3 158 shows summary of IPv4 address and M46E-FP address relation. 160 |<------------------------ 128 bits ----------------------------->| 161 |<-------------------- 96 bits ------------------->|<-- 32 bits ->| 162 | : | 163 | : | 164 | +-------:------+ 165 | | IPv4 address | 166 | +-------:------+ 167 | |<-Loc->:<-ID->| 168 | | 32-n : n | 169 | | bits : bits | 170 | | : | 171 +--------------------------------------------------+-------:------+ 172 | M46A prefix (no IPv4 network plane ID) | IPv4 address | 173 +--------------------------------------------------+-------:------+ 174 | : | 175 | : | 176 | 96 - m bits | m bits | 32 bits | 177 +-----------------------+--------------------------+-------:------+ 178 | M46A prefix | IPv4 network plane ID | IPv4 address | 179 +-----------------------+--------------------------+-------:------+ 180 |<------------- Locator (128 - n bits ) ------------------>:<-ID->| 181 | : n | 182 | : bits | 184 Figure 3 186 3. Basic Network Configuration 188 Figure 4 shows network configuration with M46E-FP. The network 189 consists of three parts. Backbone network, stub network, and 190 M46E-FP. 192 Backbone network is operated with IPv6 only. Stub network has three 193 cases. IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6 only. 195 M46E-FP connects backbone network and stub network in case IPv4 still 196 works in that stub network. If stub network is IPv6 only, M46E-FP is 197 not needed. 199 Campus network, corporate network, ISP and datacenter network are the 200 example for such network. 202 /---------------------------------------------------\ 203 | | 204 | Backbone Network | 205 | (IPv6 only) | 206 | | 207 \---------------------------------------------------/ 208 | | | 209 +-------+ +-------+ | 210 |M46E-FP| |M46E-FP| | 211 +-------+ +-------+ | 212 | | | 213 /--------------\ /--------------\ /--------------\ 214 | | | | | | 215 | Stub Network | | Stub Network | | Stub Network | 216 | (IPv4 only) | | (Dual Stack) | | (IPv6 only) | 217 | | | | | | 218 \--------------/ \--------------/ \--------------/ 220 Figure 4 222 4. Basic Function of M46E-FP 224 M46E-FP has mainly two function. One is IPv4 over IPv6 Encapsulation 225 / Decapsulation, and another is advertise route for stub network. 227 4.1. IPv4 over IPv6 Encapsulation / Decapsulation 229 M46E-FP encapsulates IPv4 packet to IPv6 from stub network to 230 backbone network, and decapsulates IPv6 packet to IPv4 from backbone 231 network to stub network. Figure 5 shows such movement. 233 +--------+------------+ +----------+--------+------------+ 234 |IPv4 Hdr| Data | --> | IPv6 Hdr |IPv4 Hdr| Data | 235 +--------+------------+ +----------+--------+------------+ 237 +--------+------------+ +----------+--------+------------+ 238 |IPv4 Hdr| Data | <-- | IPv6 Hdr |IPv4 Hdr| Data | 239 +--------+------------+ +----------+--------+------------+ 241 /-------------------\ +-------+ /-----------------------------\ 242 | Stub Network |--|M46E-FP|--| Backbone Network | 243 | (IPv4) | +-------+ | (IPv6 only) | 244 \-------------------/ \-----------------------------/ 246 Figure 5 248 M46E-FP MUST support tunnel MTU discovery [RFC1853]. When 249 encapsulated IPv6 Packet size exceed path MTU and inner IPv4 packet 250 have the Don't Fragment bit is set, M46E-FP MUST return ICMP 251 Destination unreachable message with Type3 Code4, fragmentation 252 needed and DS set [RFC0792]. 254 In case IPv6, M46E-FP just relays IPv6 packet. 256 +----------+------------+ +----------+------------+ 257 | IPv6 Hdr | data | --> | IPv6 Hdr | data | 258 +----------+------------+ +----------+------------+ 260 +----------+------------+ +----------+------------+ 261 | IPv6 Hdr | data | <-- | IPv6 Hdr | data | 262 +----------+------------+ +----------+------------+ 264 /---------------------\ +-------+ /--------------------\ 265 | Stub Network |--|M46E-FP|--| Backbone Network | 266 | (IPv6) | +-------+ | (IPv6 only) | 267 \--------------------/ \---------------------/ 269 Figure 6 271 By IPv4 over IPv6 function, M46E-FP make backbone network to IPv6 272 only. 274 4.2. M46A architecture 276 M46A is a IPv6 address used in outer IPv6 header which encapsulate 277 IPv4 packet by M46E-FP. M46A is described in M46A 278 [I-D.draft-matsuhira-m46a]. 280 Figure 7 shows M46A address architecture 282 | 96 - m bits | m bits | 32 bits | 283 +-----------------------+--------------------------+--------------+ 284 | M46A prefix | IPv4 network plane ID | IPv4 address | 285 +-----------------------+--------------------------+--------------+ 287 Figure 7 289 M46A consists of three parts as follows. 291 M46A prefix 293 M46A prefix. This value is fixed value and preconfigured to all 294 M46E-FP in the networks. 296 IPv4 network plane ID 298 IPv4 network plane ID is an identifier of IPv4 network stack over 299 IPv6 backbone network. This value is preconfigured depend on the 300 M46E-FP belong which IPv4 network plane. For more detail see 301 Section 5. 303 IPv4 address 305 IPv4 address in inner IPv4 packet. 307 M46A is resolved copying IPv4 address in inner IPv4 packet, and 308 preconfigured values, M46A prefix and IPv4 network plane ID. 310 4.3. Route Advertisement 312 M46E-FP converts stub network's IPv4 route to M46E-FP IPv6 route and 313 advertises to backbone network. And reverse direction, M46E-FP 314 converts M46E-FP IPv6 route to IPv4 route, that advertises other IPv4 315 stub networks. 317 The IPv4 route for stub network is map to M46E-FP IPv6 route one to 318 one, so number of route of IPv4 is same as number of route of M46E-FP 319 IPv6 route. Total number of route is same as when backbone network 320 operate dual stack, without M46E-FP. 322 In stub network, usual dynamic routing protocol for IPv4 and IPv6 can 323 be used such as RIPv2 [RFC2453], RIPng [RFC2080], OSPFv2 [RFC2328], 324 OSPFv3 [RFC2740] and IS-IS [RFC1195][RFC5308]. Similarly, in 325 backbone network, usual dynamic routing protocol for IPv6 can be used 326 such as RIPng [RFC2080], OSPFv3 [RFC2740] and IS-IS [RFC5308] . 328 If want using default route, default M46E-FP advertise the route 329 [M46E-FP address prefix/( 96 - m )] as default route. If want using 330 different default route by IPv4 network plane ID, default M46E-FP in 331 IPv4 network plane #1 advertise the route [ M46E-FP address prefix + 332 IPv4 network plane ID #1 / 96] as default route. Figure 10 in 333 Section 7 show the example using default route. 335 5. Stacking IPv4 Networks 337 M46E-FP can provide VPN like service to stub networks by using 338 different IPv4 network plane ID value. 340 If backbone network operator provide IPv4 privates network service to 341 Organization A, backbone network operator sets IPv4 network plane ID 342 value =1 to the M46E-FP which connects stub network of organization 343 A. If there are five stub network of organization A, backbone network 344 operator sets same IPv4 network plane ID = 1, to five M46E-FPs which 345 connect stub network of organization A. If there are one hundred stub 346 network of organization B, backbone network operator sets same IPv4 347 network plane ID = 2, to one hundred M46E-FPs which connect stub 348 network of organization B. If a new stub network in organization B 349 join, backbone network operator configures same IPv4 network plane ID 350 = 2, to the new stub network only, which connect stub network of 351 organization B, and no configuration is needed to one hundred M46E- 352 FPs which are already connected. 354 Such configuration, that means same stub network group to same IPv4 355 network plane ID value, is simple and easy to understand, so, it is 356 expected that possibility of misconfiguration is very low. And also, 357 number of configuration is minimum, that mean, number of 358 configuration is same as number of stub networks, and add new stub 359 network, configure to new one only. 361 Describe above, M46E-FP can provide VPN like service, for example, 362 Intranet or extranet. And, after IPv4 global address running out, 363 some service provider may want to reuse IPv4 private address. 364 M46E-FP can provide such IPv4 private address networks over single 365 IPv6 backbone network. By M46E-FP, some service providers may reuse 366 IPv4 private address. 368 6. Redundancy of M46E-FP 370 M46E-FP brings no limit for redundancy. Figure 8 shows such example 371 in case two connection between backbone network and stub network. 372 Number of link between backbone network and stub network is not 373 limited, and different type of link can be used, for example, for 374 wire and wireless. 376 Configuration of M46E-FPs, which connect same stub network, is same. 377 That mean same M46E-FP prefix and same IPv4 network plane ID value. 379 /---------------------------------------------------\ 380 | | 381 | Backbone Network | 382 | (IPv6 only) | 383 | | 384 \---------------------------------------------------/ 385 | | | | 386 +-------+ +-------+ +-------+ +-------+ 387 |M46E-FP| |M46E-FP| |M46E-FP| |M46E-FP| 388 +-------+ +-------+ +-------+ +-------+ 389 | | | | 390 /---------------------\ /---------------------\ 391 | | | | 392 | Stub Network | | Stub Network | 393 | (IPv4 only) | | (Dual Stack) | 394 | | | | 395 \---------------------/ \---------------------/ 397 Figure 8 399 7. Example of M46E-FP Operation 401 7.1. Basic M46E-FP Operation 403 Figure 9 shows M46E-FP operation which does not use IPv4 network 404 plane ID. In this example, two stub network is connected to backbone 405 network via M46E-FP. One stub network is 10.1.1.0/24 sub network, 406 and the other is 10.1.2.0/24 sub network. 408 When M46E-FP receives IPv4 route advertisement, then M46E-FP convert 409 this IPv4 route to IPv6 route by address resolution to M46E-FP 410 address, and advertise this IPv6 route to backbone network. When 411 M46E-FP receives IPv6 route advertisements, then M46E-FP converts 412 this IPv6 route to IPv4 route if this IPv6 route is match M46E-FP 413 address ( same prefix with M46E-FP), and advertise this IPv4 route to 414 stub network. 416 In this example. IPv4 route, 10.1.1.0/24 is converted to IPv6 route, 417 :10.1.1.0/120,and IPv4 route, 10.1.2.0/24 is converted 418 to IPv6 route, :10.1.2.0/120 at M46E-FP from stub 419 network to backbone network. And, from backbone network to stub 420 network, IPv6 route, :10.1.1.0/120 is converted to 421 IPv4 route, 10.1.1.0/24, and IPv6 route, :10.1.2.0/120 422 is converted to IPv4 route, 10.1.2.0/24. 424 /-------------\ +-----+ /------------\ +-----+ /-------------\ 425 |Stub Network | | | | Backbone | | | |Stub Network | 426 |(10.1.1.0/24)|--|M46E |--| Network |--|M46E |--|(10.1.2.0/24)| 427 | | | -FP | |(IPv6 only) | | -FP | | | 428 \-------------/ +-----+ \------------/ +-----+ \-------------/ 430 [10.1.1.0/24] ---> [:10.1.1.0/120] ---> [10.1.1.0/24] 431 [10.1.2.0/24] <--- [:10.1.2.0/120] <--- [10.1.2.0/24] 433 +---------+----+ +---------+----+----+ +---------+----+ 434 | data |IPv4| --> | data |IPv4|IPv6| --> | data |IPv4| 435 +---------+----+ +---------+----+----+ +---------+----+ 436 src: 10.1.1.1 src: :10.1.1.1 src: 10.1.1.1 437 dst: 10.1.2.1 dst: :10.1.2.1 dst: 10.1.2.1 439 Figure 9 441 Figure 10 shows the example using default route. Default route is 442 useful in case most packets are routed same path. Typically, access 443 network is one of the example. Although using default route, 444 communication between stub networks can be done. Communication 445 between host 10.1.1.1 and host 10.1.2.1 can be done inside in access 446 network, and does not pass over default M46E-FP. 448 /------------\ 449 | | 450 /-------------\ +-----+ | | +-----+ /-------------\ 451 | Backbone | | | | Access | | | |Stub Network | 452 | Network |--|M46E |--| Network |--|M46E |--|(10.1.1.0/24)| 453 | | | -FP | |(IPv6 only) | | -FP | | | 454 \-------------/ +-----+ | | +-----+ \-------------/ 455 (default) | <--[:10.1.1.0/120] 456 [/96] --> | 457 | | 458 | | +-----+ /-------------\ 459 | | | | |Stub Network | 460 | |--|M46E |--|(10.1.2.0/24)| 461 | | | -FP | | | 462 | | +-----+ \-------------/ 463 | <--[:10.1.2.0/120] 464 | | 465 | | 466 | | +-----+ /-------------\ 467 | | | | |Stub Network | 468 | |--|M46E |--|(10.1.3.0/24)| 469 | | | -FP | | | 470 | | +-----+ \-------------/ 471 | <--[:10.1.3.0/120] 472 | | 473 \------------/ 475 Figure 10 477 7.2. M46E-FP Operation with plane ID 479 Figure 11 shows M46E-FP operation which uses IPv4 network plane ID. 480 In this example, there are two planes, and two stub network in each 481 plane is connected to backbone network via M46E-FP. In each plane, 482 one stub network is 10.1.1.0/24 sub network, and the other is 483 10.1.2.0/24 sub network, that means same IPv4 address is used in 484 different plane. 486 When M46E-FP receives IPv4 route advertisements, then M46E-FP 487 converts this IPv4 route to IPv6 route by address resolution to 488 M46E-FP address, and advertise this IPv6 route to backbone network. 489 When M46E-FP receives IPv6 route advertisements, then M46E-FP 490 converts this IPv6 route to IPv4 route if this IPv6 route is match 491 M46E-FP address ( same prefix with M46E-FP), and advertises this IPv4 492 route to stub network. 494 In this example in plane #1. IPv4 route, 10.1.1.0/24 is converted to 495 IPv6 route, <#1>:10.1.1.0/120,and IPv4 route, 496 10.1.2.0/24 is converted to IPv6 route, <#1>:10.1.2.0/ 497 120 at M46E-FP from stub network to backbone network. And, from 498 backbone network to stub network, IPv6 route, <#1>:10.1.1.0/120 is converted to IPv4 route, 10.1.1.0/24, 500 and IPv6 route, <#1>:10.1.2.0/120 is converted to IPv4 501 route, 10.1.2.0/24. 503 And also, In this example in plane #2. IPv4 route, 10.1.1.0/24 is 504 converted to IPv6 route, <#2>:10.1.1.0/120,and IPv4 505 route, 10.1.2.0/24 is converted to IPv6 route, <#2>:10.1.2.0/120 at M46E-FP from stub network to backbone 507 network. And, from backbone network to stub network, IPv6 route, 508 <#2>:10.1.1.0/120 is converted to IPv4 route, 509 10.1.1.0/24, and IPv6 route, <#2>:10.1.2.0/120 is 510 converted to IPv4 route, 10.1.2.0/24. 512 In IPv6 space, address <#1>:10.1.1.1 and address 513 <#2>:10.1.1.1 are different address, route <#1>:10.1.1.0/120 and route <#2>:10.1.1.0/120 515 are different route, although in IPv4 space, address 10.1.1.1 in 516 plane #1 and 10.1.1.1 in plane#2 are same address, route 10.1.1.0/24 517 in plane#1 and route 10.1.1.0/24 in plane#2 are same route. 519 /------------\ 520 ...................|............|............................ 521 : /-------------\ +-----+ | | +-----+ /-------------\ : 522 : | Stub Network| | | | | | | | Stub Network| : 523 : |(10.1.1.0/24)|--|M46E |--| Backbone |--|M46E |--|(10.1.2.0/24)| : 524 : | | | -FP | | Network | | -FP | | | : 525 : \-------------/ +-----+ |(IPv6 only) | +-----+ \-------------/ : 526 :...........................|............|...........................: 527 | | 528 ...................|............|............................ 529 : /-------------\ +-----+ | | +-----+ /-------------\ : 530 : | Stub Network| | | | | | | | Stub Network| : 531 : |(10.1.1.0/24)|--|M46E |--| |--|M46E |--|(10.1.2.0/24)| : 532 : | | | -FP | | | | -FP | | | : 533 : \-------------/ +-----+ | | +-----+ \-------------/ : 534 :...........................|............|...........................: 535 \------------/ 537 <> 539 [10.1.1.0/24] --> [<#1>:10.1.1.0/120] --> [10.1.1.0/24] 540 [10.1.2.0/24] <-- [<#1>:10.1.2.0/120] <-- [10.1.2.0/24] 542 +---------+----+ +---------+----+----+ +---------+----+ 543 | data |IPv4| --> | data |IPv4|IPv6| --> | data |IPv4| 544 +---------+----+ +---------+----+----+ +---------+----+ 545 src: 10.1.1.1 src: <#1>:10.1.1.1 src: 10.1.1.1 546 dst: 10.1.2.1 dst: <#1>:10.1.2.1 dst: 10.1.2.1 548 <> 550 [10.1.1.0/24] --> [<#2>:10.1.1.0/120] --> [10.1.1.0/24] 551 [10.1.2.0/24] <-- [<#2>:10.1.2.0/120] <-- [10.1.2.0/24] 553 +---------+----+ +---------+----+----+ +---------+----+ 554 | data |IPv4| --> | data |IPv4|IPv6| --> | data |IPv4| 555 +---------+----+ +---------+----+----+ +---------+----+ 556 src: 10.1.1.1 src: <#2>:10.1.1.1 src: 10.1.1.1 557 dst: 10.1.2.1 dst: <#2>:10.1.2.1 dst: 10.1.2.1 559 Figure 11 561 Figure 12shows the example using default route with IPv4 network 562 plane. In this case, default M46E-FP may configure different by each 563 IPv4 network plane. 565 /------------\ 566 ...................|............|............................ 567 : /-------------\ +-----+ | | +-----+ /-------------\ : 568 : | Backbone | | | | | | | | Stub Network| : 569 : | Network |--|M46E |--| Access |--|M46E |--|(10.1.1.0/24)| : 570 : | | | -FP | | Network | | -FP | | | : 571 : \-------------/ +-----+ |(IPv6 only) | +-----+ \-------------/ : 572 : (default) | <--[<#1>:10.1.1.0/120] : 573 : [<#1>/96] --> | : 574 : | | : 575 : | | : 576 : | | +-----+ /-------------\ : 577 : | | | | | Stub Network| : 578 : | |--|M46E |--|(10.1.2.0/24)| : 579 : | | | -FP | | | : 580 : | | +-----+ \-------------/ : 581 : | <--[<#1>:10.1.2.0/120] : 582 :...........................|............|...........................: 583 | | 584 ...................|............|............................ 585 : /-------------\ +-----+ | | +-----+ /-------------\ : 586 : | Backbone | | | | | | | | Stub Network| : 587 : | Network |--|M46E |--| |--|M46E |--|(10.1.1.0/24)| : 588 : | | | -FP | | | | -FP | | | : 589 : \-------------/ +-----+ | | +-----+ \-------------/ : 590 : (default) | <--[<#2>:10.1.1.0/120] : 591 : [<#2>/96] --> | : 592 : | | : 593 : | | : 594 : | | +-----+ /-------------\ : 595 : | | | | | Stub Network| : 596 : | |--|M46E |--|(10.1.2.0/24)| : 597 : | | | -FP | | | : 598 : | | +-----+ \-------------/ : 599 : | <--[<#2>:10.1.2.0/120] : 600 :...........................|............|...........................: 601 | | 602 \------------/ 604 Figure 12 606 8. Characteristic 608 M46E-FP has following useful characteristics. 610 o Reduce backbone network operation cost with IPv6 single stack ( at 611 least less than Dual Stack) 613 o Can allocate IPv4 address to stub networks, which used in backbone 614 network before installing M46E-FP 616 o Less configuration 618 o No need for special protocol 620 o No dependent Layer 2 network 622 o Can Stack IPv4 Private networks 624 o Easy stop IPv4 operation in stub network for future ( just remove 625 M46E-FP) 627 o Provide redundancy 629 9. IANA Considerations 631 This document makes no request of IANA. 633 Note to RFC Editor: this section may be removed on publication as an 634 RFC. 636 10. Security Considerations 638 M46E-FP use automatic Encapsulation / Decapsulation technologies. 639 Security consideration related tunneling technologies are discussed 640 in RFC2893[RFC2893], RFC2267[RFC2267], etc. 642 11. References 644 11.1. Normative References 646 [I-D.draft-matsuhira-m46a] 647 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 648 August 2017. 650 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 651 RFC 792, DOI 10.17487/RFC0792, September 1981, 652 . 654 [RFC1853] Simpson, W., "IP in IP Tunneling", RFC 1853, DOI 10.17487/ 655 RFC1853, October 1995, 656 . 658 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 659 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 660 RFC2119, March 1997, 661 . 663 11.2. References 665 [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and 666 dual environments", RFC 1195, DOI 10.17487/RFC1195, 667 December 1990, . 669 [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, 670 DOI 10.17487/RFC2080, January 1997, 671 . 673 [RFC2267] Ferguson, P. and D. Senie, "Network Ingress Filtering: 674 Defeating Denial of Service Attacks which employ IP Source 675 Address Spoofing", RFC 2267, DOI 10.17487/RFC2267, 676 January 1998, . 678 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/ 679 RFC2328, April 1998, 680 . 682 [RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453, 683 DOI 10.17487/RFC2453, November 1998, 684 . 686 [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", 687 RFC 2740, DOI 10.17487/RFC2740, December 1999, 688 . 690 [RFC2893] Gilligan, R. and E. Nordmark, "Transition Mechanisms for 691 IPv6 Hosts and Routers", RFC 2893, DOI 10.17487/RFC2893, 692 August 2000, . 694 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 695 DOI 10.17487/RFC5308, October 2008, 696 . 698 Author's Address 700 Naoki Matsuhira 701 Fujitsu Limited 702 17-25, Shinkamata 1-chome, Ota-ku 703 Tokyo, 144-8588 704 Japan 706 Phone: +81-3-3730-8386 707 Fax: 708 Email: matsuhira@jp.fujitsu.com