idnits 2.17.1 draft-matsuhira-m46e-pt-07.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 2, 2019) is 1599 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 2, 2019 5 Expires: June 4, 2020 7 Multiple IPv4 - IPv6 address mapping encapsulation - prefix translator 8 (M46E-PT) 9 draft-matsuhira-m46e-pt-07 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. 16 M46E-PT translate prefix part of M46E-FP address and M46E-PR address 17 both are IPv6 address. M46E-PT does not translate IPv4 packet which 18 is 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 http://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 4, 2020. 43 Copyright Notice 45 Copyright (c) 2019 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3 62 3. Basic function of M46E-PT . . . . . . . . . . . . . . . . . . 4 63 3.1. Translation processing . . . . . . . . . . . . . . . . . . 5 64 3.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 5 65 3.3. Resolving translate prefix . . . . . . . . . . . . . . . . 5 66 3.4. Destination address resolution . . . . . . . . . . . . . . 6 67 3.5. Source address resolution . . . . . . . . . . . . . . . . 6 68 4. Sample Configuration . . . . . . . . . . . . . . . . . . . . . 7 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 10 74 8.2. Informative References . . . . . . . . . . . . . . . . . . 10 75 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 77 1. Introduction 79 This document provide M46E Prefix Translator (M46E-PT) specification. 81 The basic strategy for IPv6 deployment is dual stack. However, 82 because of exhaustion of IPv4 address, there will be no IPv4 83 addresses for configuring dual stack in near future. That means 84 there will be IPv6 only networks automatically. 86 However, there are many IPv4 only networks still exist and those 87 seems continuous use in near future. That means methods continuous 88 use of IPv4 network over IPv6 only network will be required. 90 M46E-FP [I-D.draft-matsuhira-m46e-fp] provide such methods. In 91 addition, M46E-PR [I-D.draft-matsuhira-m46e-pr] also provide such 92 methots. M46E-FP is backbone network based approach, on the other 93 hand, M46E-PR is stub network based approach. 95 M46E-PT expand IPv4 network plane by connecting M46E-FP domain and 96 M46E-PR domain. M46E-PT translate prefix part of M46E-FP address and 97 M46E-PR address both are IPv6 address. M46E-PT does not translate 98 IPv4 packet which is encapsulated, so transparency of IPv4 packet is 99 not broken. 101 2. Basic Network Configuration 103 Figure 1 shows network configuration with M46E-PT. At large view, 104 the network consists three parts, M46E-FP domain, M46E-PR domain, and 105 M46E-PT. M46E-PT connect M46E-FP domain and M46E-PR domain. 107 <------ M46E-FP Domain ------------> <--------- M46E-PR Domain ----> 109 /-------------------------------/ /-----------------------------\ 110 | | | | 111 | Backbone Network +----------+ Backbone Network | 112 | | M46E-PT | | 113 | +----------+ | 114 | +----------+ +----------+ | | | 115 \---| M46E-FP |--| M46E-FP |--/ /-----------------------------/ 116 +----------+ +----------+ | | 117 | | | | 118 | | | | 119 | | +----------+ +----------+ 120 /--------------\/--------------/ /-| M46E-PR |-\/-| M46E-PR |-\ 121 | || | | +----------+ || +----------+ | 122 | || | | || | 123 | Stub Network || Stub Network | | Stub Network || Stub Network | 124 | || | | (IPv4 only) || (Dual Stack) | 125 | || | | || | 126 \--------------//--------------/ \--------------/\--------------/ 128 Figure 1 130 M46E-FP domain consists three parts, backbone network, stub network 131 and M46E-FP. Backbone network can be operated with IPv6 only. Stub 132 network has three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), 133 and IPv6 only.M46E-FP connects backbone network and stub network in 134 case IPv4 still works in that stub network. If stub network is IPv6 135 only, M46E-FP is not needed. M46E-FP is a backbone network based 136 approach, that mean M46E-FP advertise special route for M46E-FP. 138 And also, M46E-PR domain consists three parts, backbone network, stub 139 network and M46E-FP. Backbone network can be operated with IPv6 140 only. Stub network has three cases, IPv4 only, Dual Stack (both IPv4 141 and IPv6), and IPv6 only.M46E-FP connects backbone network and stub 142 network in case IPv4 still works in that stub network. If stub 143 network is IPv6 only, M46E-PR is not needed. M46E-PR is a stub 144 network based approach. 146 3. Basic function of M46E-PT 148 This section describe basic function of M46E-PT. 150 3.1. Translation processing 152 M46E-PT translate between M46E-FP packet and M46E-PT packet. M46E-FP 153 packet and M46E-PT packet are almost the same, however IPv6 address 154 are different. 156 Fig shows packet format of M46E-FP domain and M46E-PT domain. 158 +--------+--------+------------+ +--------+--------+------------+ 159 |IPv6 Hdr|IPv4 Hdr| Data | --> |IPv6 Hdr|IPv4 Hdr| Data | 160 +--------+--------+------------+ +--------+--------+------------+ 162 +--------+--------+------------+ +--------+--------+------------+ 163 |IPv6 Hdr|IPv4 Hdr| Data | <-- |IPv6 Hdr|IPv4 Hdr| Data | 164 +--------+--------+------------+ +--------+--------+------------+ 166 /-------------------\ +----------+ /---------------------------\ 167 | M46E-FP Domain |--| M46E-PT |--| M46E-PR Domain | 168 | | +----------+ | | 169 \-------------------/ \---------------------------/ 171 Figure 2 173 3.2. M46A architecture 175 M46E-FP and M46E-PR use M46A [I-D.draft-matsuhira-m46a]. 177 figure Figure 3 shows M46A architecture. 179 | 96 - m bits | m bits | 32 bits | 180 +--------------------------+------------------------+--------------+ 181 | M46A prefix | IPv4 network plane ID | IPv4 address | 182 +--------------------------+------------------------+--------------+ 184 Figure 3 186 3.3. Resolving translate prefix 188 M46E-PT translate from M46E-FP prefix to M46E-PR prefix, or from 189 M46E-PR prefix to M46E-FP prefix using M46E-FP Prefix Translation 190 (M46E-PT) table. fig Figure 4shows address resolution manner and fig 191 Figure 5shows M46E-PT table. 193 | 96 - m bits | m bits | 32 bits | 194 +--------------------------+------------------------+--------------+ 195 | M46A prefix | IPv4 network plane ID | IPv4 address | 196 +--------------------------+------------------------+--------------+ 198 \--------------------------/\--------------------------------------/ 199 ^ | 200 | | 201 | v 202 +------------------------------------------------------------------+ 203 | | 204 | M46E-FP Prefix Translation Table (M46E-PT Table) | 205 | | 206 +------------------------------------------------------------------+ 208 Figure 4 210 M46E-FP-AT table is similar with M46E-PR table, however M46E-AT table 211 may contain M46E-FP 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 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 221 +---------------------+------------+-------++-----------------------+ 222 : : : 223 +---------------------+------------+-------++-----------------------+ 224 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 225 +---------------------+------------+-------++-----------------------+ 227 Figure 5 229 3.4. Destination address resolution 231 For address resolution for destination address, M46E-PT use M46E-PT 232 table. 234 3.5. Source address resolution 236 For address resolution for source address, M46E-PT use interface 237 information, not M46E-PT table. From M46E-FP domain to M46E-PR 238 domain, M46E-PT use IPv6 address prefix of the interface which belong 239 M46E-PR domain. From 241 4. Sample Configuration 243 Figure Figure 6shows sample confiuration of M46E-PT. In this 244 example, there are four IPv4 stub network with the same IPv4 network 245 plane, and two of four are in M46E-FP domain and other two of four 246 are in M46E-PR domain. 248 In this example, M46E-FP prefix is 2001:0db8:0:46::/64. 250 /------------\ 251 | +--------+ /----------------------\ 252 | Backbone | | |Stub Network#1 | 253 | Network |M46E-FP |--|10.1.1.0/24(plane 1) | 254 |(IPv6 only)| | |2001:0db8:1:1::/64 | 255 | +--------+ \----------------------/ 256 | <--[2001:0db8:1:1::/64] 257 | <--[2001:0db8:0:46:0:1:10.1.1.0/120] 258 | | 259 | +--------+ /----------------------\ 260 | | | |Stub Network#2 | 261 | |M46E-FP |--|10.1.2.0/24(plane 1) | 262 | | | |2001:0db8:1:2::/64 | 263 | +--------+ \----------------------/ 264 | <--[2001:0db8:1:2::/64] 265 | <--[2001:0db8:0:46:0:1:10.1.2.0/120] 266 | | 267 | <--[2001:0db8:0:46:0:1:10.1.4.0/120] 268 | <--[2001:0db8:0:46:0:1:10.1.5.0/120] 269 | +------------+ 270 | | M46E-PT | 271 | +------------+ 272 \------------/ | 273 | |Stub Network #0 274 /------------\ | 2001:0db8:2:0::/64 275 | |----+ 276 | | /--------------------------------------/ 277 | | | Stub Network #3 | 278 | | | 2001:0db8:2:1::/64 | 279 | | | +--------+ /----------------------\ | 280 | |--| |M46E-PR |--|10.1.3.0/24(plane 1) | | 281 | | | +--------+ /----------------------/ | 282 | <--[2001:0db8:2:1::/64] | 283 | | /--------------------------------------/ 284 | | 285 | | /--------------------------------------/ 286 | | | Stub Network #4 | 287 | | | 2001:0db8:2:2::/64 | 288 | Backbone | | +--------+ /----------------------\ | 289 | Network |--| |M46E-PR |--|10.1.4.0/24(plane 1) | | 290 | | | +--------+ \----------------------/ | 291 | <--[2001:0db8:2:2::/64] | 292 | | /--------------------------------------/ 293 \------------/ 295 Figure 6 297 Figure Figure 7 shows M46E-PT table for this example. This example 298 is default free case. 300 +---------------------+------------+-------++-----------------------+ 301 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 302 +---------------------+------------+-------++-----------------------+ 303 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:46 | 304 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:46 | 305 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 306 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 307 +---------------------+------------+-------++-----------------------+ 309 Figure 7 311 Fig Figure 8shows another M46E-PT table for this example. This 312 example use default for M46E-FP. If there are many stub network in 313 M46E-FP domain, by using default as M46E-FP prefix, reduction of 314 M46E-PT table size can be possible. 316 +---------------------+------------+-------++-----------------------+ 317 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 318 +---------------------+------------+-------++-----------------------+ 319 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 320 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 321 | 1 | 0.0.0.0 | /0 || 2001:0db8:0:46 | 322 +---------------------+------------+-------++-----------------------+ 324 Figure 8 326 5. IANA Considerations 328 This document makes no request of IANA. 330 Note to RFC Editor: this section may be removed on publication as an 331 RFC. 333 6. Security Considerations 335 Security Considerations does not discussed in this memo. 337 7. Acknowledgements 339 8. References 340 8.1. Normative References 342 [I-D.draft-matsuhira-m46a] 343 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 344 June 2019. 346 [I-D.draft-matsuhira-m46e-fp] 347 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 348 encapsulation - fixed prefix (M46E-FP)", June 2019. 350 [I-D.draft-matsuhira-m46e-pr] 351 Matsuhira, N., "Multiple IPv4 - IPv6 address mapping 352 encapsulation - prefix resolution", June 2019. 354 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 355 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 356 RFC2119, March 1997, 357 . 359 8.2. Informative References 361 Author's Address 363 Naoki Matsuhira 364 Fujitsu Limited 365 17-25, Shinkamata 1-chome, Ota-ku 366 Tokyo, 144-8588 367 Japan 369 Phone: +81-3-3735-1111 370 Fax: 371 Email: matsuhira@jp.fujitsu.com