idnits 2.17.1 draft-matsuhira-m46e-pt-09.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 6 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (December 15, 2020) is 1220 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 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 December 15, 2020 5 Expires: June 18, 2021 7 Multiple IPv4 - IPv6 address mapping encapsulation - prefix translator 8 (M46E-PT) 9 draft-matsuhira-m46e-pt-09 11 Abstract 13 This document specifies Multiple IPv4 - IPv6 mapping encapsulation - 14 Prefix Translator (M46E-PT) specification. M46E-PT expand IPv4 15 network plane by connecting M46E-FP domain and M46E-PR domain. M46E- 16 PT translate prefix part of M46E-FP address and M46E-PR address both 17 are IPv6 address. M46E-PT does not translate IPv4 packet which is 18 encapsulated, so transparency of IPv4 packet is not broken. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in RFC 2119 [RFC2119]. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on June 18, 2021. 43 Copyright Notice 45 Copyright (c) 2020 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3 62 3. Basic function of M46E-PT . . . . . . . . . . . . . . . . . . 4 63 3.1. Translation processing . . . . . . . . . . . . . . . . . 4 64 3.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 4 65 3.3. Resolving translate prefix . . . . . . . . . . . . . . . 5 66 3.4. Destination address resolution . . . . . . . . . . . . . 5 67 3.5. Source address resolution . . . . . . . . . . . . . . . . 6 68 4. Sample Configuration . . . . . . . . . . . . . . . . . . . . 6 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 72 8. Normative References . . . . . . . . . . . . . . . . . . . . 8 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 75 1. Introduction 77 This document provide M46E Prefix Translator (M46E-PT) specification. 79 The basic strategy for IPv6 deployment is dual stack. However, 80 because of exhaustion of IPv4 address, there will be no IPv4 81 addresses for configuring dual stack in near future. That means 82 there will be IPv6 only networks automatically. 84 However, there are many IPv4 only networks still exist and those 85 seems continuous use in near future. That means methods continuous 86 use of IPv4 network over IPv6 only network will be required. 88 M46E-FP [I-D.draft-matsuhira-m46e-fp] provide such methods. In 89 addition, M46E-PR [I-D.draft-matsuhira-m46e-pr] also provide such 90 methots. M46E-FP is backbone network based approach, on the other 91 hand, M46E-PR is stub network based approach. 93 M46E-PT expand IPv4 network plane by connecting M46E-FP domain and 94 M46E-PR domain. M46E-PT translate prefix part of M46E-FP address and 95 M46E-PR address both are IPv6 address. M46E-PT does not translate 96 IPv4 packet which is encapsulated, so transparency of IPv4 packet is 97 not broken. 99 2. Basic Network Configuration 101 Figure 1 shows network configuration with M46E-PT. At large view, 102 the network consists three parts, M46E-FP domain, M46E-PR domain, and 103 M46E-PT. M46E-PT connect M46E-FP domain and M46E-PR domain. 105 <------ M46E-FP Domain ------------> <--------- M46E-PR Domain ----> 107 /-------------------------------/ /-----------------------------\ 108 | | | | 109 | Backbone Network +----------+ Backbone Network | 110 | | M46E-PT | | 111 | +----------+ | 112 | +----------+ +----------+ | | | 113 \---| M46E-FP |--| M46E-FP |--/ /-----------------------------/ 114 +----------+ +----------+ | | 115 | | | | 116 | | | | 117 | | +----------+ +----------+ 118 /--------------\/--------------/ /-| M46E-PR |-\/-| M46E-PR |-\ 119 | || | | +----------+ || +----------+ | 120 | || | | || | 121 | Stub Network || Stub Network | | Stub Network || Stub Network | 122 | || | | (IPv4 only) || (Dual Stack) | 123 | || | | || | 124 \--------------//--------------/ \--------------/\--------------/ 126 Figure 1 128 M46E-FP domain consists three parts, backbone network, stub network 129 and M46E-FP. Backbone network can be operated with IPv6 only. Stub 130 network has three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), 131 and IPv6 only.M46E-FP connects backbone network and stub network in 132 case IPv4 still works in that stub network. If stub network is IPv6 133 only, M46E-FP is not needed. M46E-FP is a backbone network based 134 approach, that mean M46E-FP advertise special route for M46E-FP. 136 And also, M46E-PR domain consists three parts, backbone network, stub 137 network and M46E-FP. Backbone network can be operated with IPv6 138 only. Stub network has three cases, IPv4 only, Dual Stack (both IPv4 139 and IPv6), and IPv6 only.M46E-FP connects backbone network and stub 140 network in case IPv4 still works in that stub network. If stub 141 network is IPv6 only, M46E-PR is not needed. M46E-PR is a stub 142 network based approach. 144 3. Basic function of M46E-PT 146 This section describe basic function of M46E-PT. 148 3.1. Translation processing 150 M46E-PT translate between M46E-FP packet and M46E-PT packet. M46E-FP 151 packet and M46E-PT packet are almost the same, however IPv6 address 152 are different. 154 Fig shows packet format of M46E-FP domain and M46E-PT domain. 156 +--------+--------+------------+ +--------+--------+------------+ 157 |IPv6 Hdr|IPv4 Hdr| Data | --> |IPv6 Hdr|IPv4 Hdr| Data | 158 +--------+--------+------------+ +--------+--------+------------+ 160 +--------+--------+------------+ +--------+--------+------------+ 161 |IPv6 Hdr|IPv4 Hdr| Data | <-- |IPv6 Hdr|IPv4 Hdr| Data | 162 +--------+--------+------------+ +--------+--------+------------+ 164 /-------------------\ +----------+ /---------------------------\ 165 | M46E-FP Domain |--| M46E-PT |--| M46E-PR Domain | 166 | | +----------+ | | 167 \-------------------/ \---------------------------/ 169 Figure 2 171 3.2. M46A architecture 173 M46E-FP and M46E-PR use M46A [I-D.draft-matsuhira-m46a]. 175 figure Figure 3 shows M46A architecture. 177 | 96 - m bits | m bits | 32 bits | 178 +--------------------------+------------------------+--------------+ 179 | M46A prefix | IPv4 network plane ID | IPv4 address | 180 +--------------------------+------------------------+--------------+ 182 Figure 3 184 3.3. Resolving translate prefix 186 M46E-PT translate from M46E-FP prefix to M46E-PR prefix, or from 187 M46E-PR prefix to M46E-FP prefix using M46E-FP Prefix Translation 188 (M46E-PT) table. fig Figure 4shows address resolution manner and fig 189 Figure 5shows M46E-PT table. 191 | 96 - m bits | m bits | 32 bits | 192 +--------------------------+------------------------+--------------+ 193 | M46A prefix | IPv4 network plane ID | IPv4 address | 194 +--------------------------+------------------------+--------------+ 196 \--------------------------/\--------------------------------------/ 197 ^ | 198 | | 199 | v 200 +------------------------------------------------------------------+ 201 | | 202 | M46E-FP Prefix Translation Table (M46E-PT Table) | 203 | | 204 +------------------------------------------------------------------+ 206 Figure 4 208 M46E-FP-AT table is similar with M46E-PR table, however M46E-AT table 209 may contain M46E-FP prefix. 211 +---------------------+------------+-------++-----------------------+ 212 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 213 +---------------------+------------+-------++-----------------------+ 214 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 215 +---------------------+------------+-------++-----------------------+ 216 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 217 +---------------------+------------+-------++-----------------------+ 218 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 219 +---------------------+------------+-------++-----------------------+ 220 : : : 221 +---------------------+------------+-------++-----------------------+ 222 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 223 +---------------------+------------+-------++-----------------------+ 225 Figure 5 227 3.4. Destination address resolution 229 For address resolution for destination address, M46E-PT use M46E-PT 230 table. 232 3.5. Source address resolution 234 For address resolution for source address, M46E-PT use interface 235 information, not M46E-PT table. From M46E-FP domain to M46E-PR 236 domain, M46E-PT use IPv6 address prefix of the interface which belong 237 M46E-PR domain. From 239 4. Sample Configuration 241 Figure Figure 6shows sample confiuration of M46E-PT. In this 242 example, there are four IPv4 stub network with the same IPv4 network 243 plane, and two of four are in M46E-FP domain and other two of four 244 are in M46E-PR domain. 246 In this example, M46E-FP prefix is 2001:0db8:0:46::/64. 248 /------------\ 249 | +--------+ /----------------------\ 250 | Backbone | | |Stub Network#1 | 251 | Network |M46E-FP |--|10.1.1.0/24(plane 1) | 252 |(IPv6 only)| | |2001:0db8:1:1::/64 | 253 | +--------+ \----------------------/ 254 | <--[2001:0db8:1:1::/64] 255 | <--[2001:0db8:0:46:0:1:10.1.1.0/120] 256 | | 257 | +--------+ /----------------------\ 258 | | | |Stub Network#2 | 259 | |M46E-FP |--|10.1.2.0/24(plane 1) | 260 | | | |2001:0db8:1:2::/64 | 261 | +--------+ \----------------------/ 262 | <--[2001:0db8:1:2::/64] 263 | <--[2001:0db8:0:46:0:1:10.1.2.0/120] 264 | | 265 | <--[2001:0db8:0:46:0:1:10.1.4.0/120] 266 | <--[2001:0db8:0:46:0:1:10.1.5.0/120] 267 | +------------+ 268 | | M46E-PT | 269 | +------------+ 270 \------------/ | 271 | |Stub Network #0 272 /------------\ | 2001:0db8:2:0::/64 273 | |----+ 274 | | /--------------------------------------/ 275 | | | Stub Network #3 | 276 | | | 2001:0db8:2:1::/64 | 277 | | | +--------+ /----------------------\ | 278 | |--| |M46E-PR |--|10.1.3.0/24(plane 1) | | 279 | | | +--------+ /----------------------/ | 280 | <--[2001:0db8:2:1::/64] | 281 | | /--------------------------------------/ 282 | | 283 | | /--------------------------------------/ 284 | | | Stub Network #4 | 285 | | | 2001:0db8:2:2::/64 | 286 | Backbone | | +--------+ /----------------------\ | 287 | Network |--| |M46E-PR |--|10.1.4.0/24(plane 1) | | 288 | | | +--------+ \----------------------/ | 289 | <--[2001:0db8:2:2::/64] | 290 | | /--------------------------------------/ 291 \------------/ 293 Figure 6 295 Figure Figure 7 shows M46E-PT table for this example. This example 296 is default free case. 298 +---------------------+------------+-------++-----------------------+ 299 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 300 +---------------------+------------+-------++-----------------------+ 301 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:46 | 302 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:46 | 303 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 304 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 305 +---------------------+------------+-------++-----------------------+ 307 Figure 7 309 Fig Figure 8shows another M46E-PT table for this example. This 310 example use default for M46E-FP. If there are many stub network in 311 M46E-FP domain, by using default as M46E-FP prefix, reduction of 312 M46E-PT table size can be possible. 314 +---------------------+------------+-------++-----------------------+ 315 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 316 +---------------------+------------+-------++-----------------------+ 317 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 318 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 319 | 1 | 0.0.0.0 | /0 || 2001:0db8:0:46 | 320 +---------------------+------------+-------++-----------------------+ 322 Figure 8 324 5. IANA Considerations 326 This document makes no request of IANA. 328 Note to RFC Editor: this section may be removed on publication as an 329 RFC. 331 6. Security Considerations 333 Security Considerations does not discussed in this memo. 335 7. Acknowledgements 337 8. Normative References 339 [I-D.draft-matsuhira-m46a] 340 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 341 June 2019. 343 [I-D.draft-matsuhira-m46e-fp] 344 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 345 encapsulation - fixed prefix (M46E-FP)", June 2019. 347 [I-D.draft-matsuhira-m46e-pr] 348 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 349 encapsulation - prefix resolution", June 2019. 351 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 352 Requirement Levels", BCP 14, RFC 2119, 353 DOI 10.17487/RFC2119, March 1997, 354 . 356 Author's Address 358 Naoki Matsuhira 359 Fujitsu Limited 360 17-25, Shinkamata 1-chome, Ota-ku 361 Tokyo 144-8588 362 Japan 364 Phone: +81-3-3735-1111 365 Email: matsuhira@fujitsu.com