idnits 2.17.1 draft-matsuhira-m46e-pt-11.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 (18 December 2021) is 857 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 18 December 2021 5 Expires: 21 June 2022 7 Multiple IPv4 - IPv6 address mapping encapsulation - prefix translator 8 (M46E-PT) 9 draft-matsuhira-m46e-pt-11 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 21 June 2022. 43 Copyright Notice 45 Copyright (c) 2021 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 (https://trustee.ietf.org/ 50 license-info) in effect on the date of publication of this document. 51 Please review these documents carefully, as they describe your rights 52 and restrictions with respect to this document. Code Components 53 extracted from this document must include Revised BSD License text as 54 described in Section 4.e of the Trust Legal Provisions and are 55 provided without warranty as described in the Revised BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3 61 3. Basic function of M46E-PT . . . . . . . . . . . . . . . . . . 4 62 3.1. Translation processing . . . . . . . . . . . . . . . . . 4 63 3.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 4 64 3.3. Resolving translate prefix . . . . . . . . . . . . . . . 5 65 3.4. Destination address resolution . . . . . . . . . . . . . 6 66 3.5. Source address resolution . . . . . . . . . . . . . . . . 6 67 4. Sample Configuration . . . . . . . . . . . . . . . . . . . . 6 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 70 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 71 8. Normative References . . . . . . . . . . . . . . . . . . . . 8 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 74 1. Introduction 76 This document provide M46E Prefix Translator (M46E-PT) specification. 78 The basic strategy for IPv6 deployment is dual stack. However, 79 because of exhaustion of IPv4 address, there will be no IPv4 80 addresses for configuring dual stack in near future. That means 81 there will be IPv6 only networks automatically. 83 However, there are many IPv4 only networks still exist and those 84 seems continuous use in near future. That means methods continuous 85 use of IPv4 network over IPv6 only network will be required. 87 M46E-FP [I-D.draft-matsuhira-m46e-fp] provide such methods. In 88 addition, M46E-PR [I-D.draft-matsuhira-m46e-pr] also provide such 89 methots. M46E-FP is backbone network based approach, on the other 90 hand, M46E-PR is stub network based approach. 92 M46E-PT expand IPv4 network plane by connecting M46E-FP domain and 93 M46E-PR domain. M46E-PT translate prefix part of M46E-FP address and 94 M46E-PR address both are IPv6 address. M46E-PT does not translate 95 IPv4 packet which is encapsulated, so transparency of IPv4 packet is 96 not broken. 98 2. Basic Network Configuration 100 Figure 1 shows network configuration with M46E-PT. At large view, 101 the network consists three parts, M46E-FP domain, M46E-PR domain, and 102 M46E-PT. M46E-PT connect M46E-FP domain and M46E-PR domain. 104 <------ M46E-FP Domain ------------> <--------- M46E-PR Domain ----> 106 /-------------------------------/ /-----------------------------\ 107 | | | | 108 | Backbone Network +----------+ Backbone Network | 109 | | M46E-PT | | 110 | +----------+ | 111 | +----------+ +----------+ | | | 112 \---| M46E-FP |--| M46E-FP |--/ /-----------------------------/ 113 +----------+ +----------+ | | 114 | | | | 115 | | | | 116 | | +----------+ +----------+ 117 /--------------\/--------------/ /-| M46E-PR |-\/-| M46E-PR |-\ 118 | || | | +----------+ || +----------+ | 119 | || | | || | 120 | Stub Network || Stub Network | | Stub Network || Stub Network | 121 | || | | (IPv4 only) || (Dual Stack) | 122 | || | | || | 123 \--------------//--------------/ \--------------/\--------------/ 125 Figure 1 127 M46E-FP domain consists three parts, backbone network, stub network 128 and M46E-FP. Backbone network can be operated with IPv6 only. Stub 129 network has three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), 130 and IPv6 only.M46E-FP connects backbone network and stub network in 131 case IPv4 still works in that stub network. If stub network is IPv6 132 only, M46E-FP is not needed. M46E-FP is a backbone network based 133 approach, that mean M46E-FP advertise special route for M46E-FP. 135 And also, M46E-PR domain consists three parts, backbone network, stub 136 network and M46E-FP. Backbone network can be operated with IPv6 137 only. Stub network has three cases, IPv4 only, Dual Stack (both IPv4 138 and IPv6), and IPv6 only.M46E-FP connects backbone network and stub 139 network in case IPv4 still works in that stub network. If stub 140 network is IPv6 only, M46E-PR is not needed. M46E-PR is a stub 141 network based approach. 143 3. Basic function of M46E-PT 145 This section describe basic function of M46E-PT. 147 3.1. Translation processing 149 M46E-PT translate between M46E-FP packet and M46E-PT packet. M46E-FP 150 packet and M46E-PT packet are almost the same, however IPv6 address 151 are different. 153 Fig shows packet format of M46E-FP domain and M46E-PT domain. 155 +--------+--------+------------+ +--------+--------+------------+ 156 |IPv6 Hdr|IPv4 Hdr| Data | --> |IPv6 Hdr|IPv4 Hdr| Data | 157 +--------+--------+------------+ +--------+--------+------------+ 159 +--------+--------+------------+ +--------+--------+------------+ 160 |IPv6 Hdr|IPv4 Hdr| Data | <-- |IPv6 Hdr|IPv4 Hdr| Data | 161 +--------+--------+------------+ +--------+--------+------------+ 163 /-------------------\ +----------+ /---------------------------\ 164 | M46E-FP Domain |--| M46E-PT |--| M46E-PR Domain | 165 | | +----------+ | | 166 \-------------------/ \---------------------------/ 168 Figure 2 170 3.2. M46A architecture 172 M46E-FP and M46E-PR use M46A [I-D.draft-matsuhira-m46a]. 174 figure Figure 3 shows M46A architecture. 176 | 96 - m bits | m bits | 32 bits | 177 +--------------------------+------------------------+--------------+ 178 | M46A prefix | IPv4 network plane ID | IPv4 address | 179 +--------------------------+------------------------+--------------+ 180 Figure 3 182 3.3. Resolving translate prefix 184 M46E-PT translate from M46E-FP prefix to M46E-PR prefix, or from 185 M46E-PR prefix to M46E-FP prefix using M46E-FP Prefix Translation 186 (M46E-PT) table. fig Figure 4shows address resolution manner and fig 187 Figure 5shows M46E-PT table. 189 | 96 - m bits | m bits | 32 bits | 190 +--------------------------+------------------------+--------------+ 191 | M46A prefix | IPv4 network plane ID | IPv4 address | 192 +--------------------------+------------------------+--------------+ 194 \--------------------------/\--------------------------------------/ 195 ^ | 196 | | 197 | v 198 +------------------------------------------------------------------+ 199 | | 200 | M46E-FP Prefix Translation Table (M46E-PT Table) | 201 | | 202 +------------------------------------------------------------------+ 204 Figure 4 206 M46E-FP-AT table is similar with M46E-PR table, however M46E-AT table 207 may contain M46E-FP prefix. 209 +---------------------+------------+-------++-----------------------+ 210 |IPv4 network plane ID|IPv4 address|netmask||M46A 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 : : : 219 +---------------------+------------+-------++-----------------------+ 220 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 221 +---------------------+------------+-------++-----------------------+ 223 Figure 5 225 3.4. Destination address resolution 227 For address resolution for destination address, M46E-PT use M46E-PT 228 table. 230 3.5. Source address resolution 232 For address resolution for source address, M46E-PT use interface 233 information, not M46E-PT table. From M46E-FP domain to M46E-PR 234 domain, M46E-PT use IPv6 address prefix of the interface which belong 235 M46E-PR domain. From 237 4. Sample Configuration 239 Figure Figure 6shows sample confiuration of M46E-PT. In this 240 example, there are four IPv4 stub network with the same IPv4 network 241 plane, and two of four are in M46E-FP domain and other two of four 242 are in M46E-PR domain. 244 In this example, M46E-FP prefix is 2001:0db8:0:46::/64. 246 /------------\ 247 | +--------+ /----------------------\ 248 | Backbone | | |Stub Network#1 | 249 | Network |M46E-FP |--|10.1.1.0/24(plane 1) | 250 |(IPv6 only)| | |2001:0db8:1:1::/64 | 251 | +--------+ \----------------------/ 252 | <--[2001:0db8:1:1::/64] 253 | <--[2001:0db8:0:46:0:1:10.1.1.0/120] 254 | | 255 | +--------+ /----------------------\ 256 | | | |Stub Network#2 | 257 | |M46E-FP |--|10.1.2.0/24(plane 1) | 258 | | | |2001:0db8:1:2::/64 | 259 | +--------+ \----------------------/ 260 | <--[2001:0db8:1:2::/64] 261 | <--[2001:0db8:0:46:0:1:10.1.2.0/120] 262 | | 263 | <--[2001:0db8:0:46:0:1:10.1.4.0/120] 264 | <--[2001:0db8:0:46:0:1:10.1.5.0/120] 265 | +------------+ 266 | | M46E-PT | 267 | +------------+ 268 \------------/ | 269 | |Stub Network #0 270 /------------\ | 2001:0db8:2:0::/64 271 | |----+ 272 | | /--------------------------------------/ 273 | | | Stub Network #3 | 274 | | | 2001:0db8:2:1::/64 | 275 | | | +--------+ /----------------------\ | 276 | |--| |M46E-PR |--|10.1.3.0/24(plane 1) | | 277 | | | +--------+ /----------------------/ | 278 | <--[2001:0db8:2:1::/64] | 279 | | /--------------------------------------/ 280 | | 281 | | /--------------------------------------/ 282 | | | Stub Network #4 | 283 | | | 2001:0db8:2:2::/64 | 284 | Backbone | | +--------+ /----------------------\ | 285 | Network |--| |M46E-PR |--|10.1.4.0/24(plane 1) | | 286 | | | +--------+ \----------------------/ | 287 | <--[2001:0db8:2:2::/64] | 288 | | /--------------------------------------/ 289 \------------/ 291 Figure 6 293 Figure Figure 7 shows M46E-PT table for this example. This example 294 is default free case. 296 +---------------------+------------+-------++-----------------------+ 297 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 298 +---------------------+------------+-------++-----------------------+ 299 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:46 | 300 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:46 | 301 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 302 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 303 +---------------------+------------+-------++-----------------------+ 305 Figure 7 307 Fig Figure 8shows another M46E-PT table for this example. This 308 example use default for M46E-FP. If there are many stub network in 309 M46E-FP domain, by using default as M46E-FP prefix, reduction of 310 M46E-PT table size can be possible. 312 +---------------------+------------+-------++-----------------------+ 313 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 314 +---------------------+------------+-------++-----------------------+ 315 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 316 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 317 | 1 | 0.0.0.0 | /0 || 2001:0db8:0:46 | 318 +---------------------+------------+-------++-----------------------+ 320 Figure 8 322 5. IANA Considerations 324 This document makes no request of IANA. 326 Note to RFC Editor: this section may be removed on publication as an 327 RFC. 329 6. Security Considerations 331 Security Considerations does not discussed in this memo. 333 7. Acknowledgements 335 8. Normative References 337 [I-D.draft-matsuhira-m46a] 338 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 339 1 June 2019. 341 [I-D.draft-matsuhira-m46e-fp] 342 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 343 encapsulation - fixed prefix (M46E-FP)", 1 June 2019. 345 [I-D.draft-matsuhira-m46e-pr] 346 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 347 encapsulation - prefix resolution", 1 June 2019. 349 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 350 Requirement Levels", BCP 14, RFC 2119, 351 DOI 10.17487/RFC2119, March 1997, 352 . 354 Author's Address 356 Naoki Matsuhira 357 Fujitsu Limited 358 17-25, Shinkamata 1-chome, Ota-ku, 359 144-8588 360 Japan 362 Phone: +81-3-3735-1111 363 Email: naoki.matsuhira@gmail.com