idnits 2.17.1 draft-matsuhira-m46e-pr-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 3 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 1227 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 resolution 8 (M46E-PR) 9 draft-matsuhira-m46e-pr-09 11 Abstract 13 This document specifies M46E Prefix Resolution (M46E-PR) 14 specification. M46E-PR connect IPv4 stub networks between IPv6 15 backbone network. And also, M46E-PR can stack many IPv4 networks, 16 i.e. the nwtworks using same IPv4 private addresses without 17 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 https://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 June 18, 2021. 42 Copyright Notice 44 Copyright (c) 2020 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2 60 2. Basic Network Configuration . . . . . . . . . . . . . . . . . 2 61 3. Basic Function of M46E-PR . . . . . . . . . . . . . . . . . . 3 62 3.1. IPv4 over IPv6 Encapsulation / Decapsulation . . . . . . 3 63 3.2. M46A architecture . . . . . . . . . . . . . . . . . . . . 4 64 3.3. Resolving M46A . . . . . . . . . . . . . . . . . . . . . 5 65 4. Mode of M46E-PR . . . . . . . . . . . . . . . . . . . . . . . 6 66 4.1. Router mode . . . . . . . . . . . . . . . . . . . . . . . 6 67 4.2. Host mode . . . . . . . . . . . . . . . . . . . . . . . . 6 68 5. Sample configuration . . . . . . . . . . . . . . . . . . . . 6 69 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 71 8. Normative References . . . . . . . . . . . . . . . . . . . . 8 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 This document provide M46E Prefix Resolution (M46E-PR) 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-PR also provide such methots. 89 2. Basic Network Configuration 91 Figure 1 shows network configuration with M46E-PR. The network 92 consists of three parts, backbone network, stub network, and M46E-PR. 94 Backbone network can be operated with IPv6 only. Stub network has 95 three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6 96 only. 98 M46E-FP connects backbone network and stub network in case IPv4 still 99 works in that stub network. If stub network is IPv6 only, M46E-PR is 100 not needed. 102 /---------------------------------------------------\ 103 | | 104 | Backbone Network | 105 | (IPv6 only) | 106 | | 107 \---------------------------------------------------/ 108 | | | 109 | | | 110 | | | 111 +----------+ +----------+ | 112 /-| M46E-PR |-\ /-| M46E-PR |-\ /--------------\ 113 | +----------+ | | +----------+ | | | 114 | | | | | | 115 | Stub Network | | Stub Network | | Stub Network | 116 | (IPv4 only) | | (Dual Stack) | | (IPv6 only) | 117 | | | | | | 118 \--------------/ \--------------/ \--------------/ 120 Figure 1 122 3. Basic Function of M46E-PR 124 M46E-PR has mainly two function. One is IPv4 over IPv6 Encapsulation 125 / Decapsulation, and another is generate a table where IPv4 stub 126 network belong to IPv6 network. 128 3.1. IPv4 over IPv6 Encapsulation / Decapsulation 130 M46E-PR excapsulates IPv4 packet to IPv6 from stub network to 131 backbone network, and decapsulates IPv6 packet to IPv4 from backbone 132 network to stub network. Figure 2 shows packet format on both 133 backbone network and stub network. 135 +--------+------------+ +----------+--------+------------+ 136 |IPv4 Hdr| Data | --> | IPv6 Hdr |IPv4 Hdr| Data | 137 +--------+------------+ +----------+--------+------------+ 139 +--------+------------+ +----------+--------+------------+ 140 |IPv4 Hdr| Data | <-- | IPv6 Hdr |IPv4 Hdr| Data | 141 +--------+------------+ +----------+--------+------------+ 143 /-------------------\ +----------+ /-----------------------------\ 144 | Stub Network |--| M46E-PR |--| Backbone Network | 145 | (IPv4) | +----------+ | (IPv6 only) | 146 \-------------------/ \-----------------------------/ 148 Figure 2 150 3.2. M46A architecture 152 M46A is a IPv6 address used in outer IPv6 header which encapsulate 153 IPv4 packet by M46E-PR. M46A is described in 154 [I-D.draft-matsuhira-m46a].Figure 3 shows M46A address architecture. 156 | 96 - m bits | m bits | 32 bits | 157 +--------------------------+------------------------+--------------+ 158 | M46A prefix | IPv4 network plane ID | IPv4 address | 159 +--------------------------+------------------------+--------------+ 161 Figure 3 163 M46E address consists of three parts as follows. 165 M46A prefix 167 M46A prefix. This value is not a fixed value, and resolved packet 168 by packet 170 IPv4 network plane ID IPv4 network plane ID is an identifier of IPv4 171 network stack over IPv6 backbone network. 173 IPv4 address 175 IPv4 address in inner IPv4 packet. 177 3.3. Resolving M46A 179 M46E-PR resolve M46A using M46E Prefix Resolution Table (M46E-PR 180 Table). M46E-PR generate M46E-PR address resolving M46A prefix from 181 IPv4 network plane ID and IPv4 address. FigureFigure 4 show this 182 processing. 184 | 96 - m bits | m bits | 32 bits | 185 +--------------------------+------------------------+--------------+ 186 | M46A prefix | IPv4 network plane ID | IPv4 address | 187 +--------------------------+------------------------+--------------+ 189 \--------------------------/\--------------------------------------/ 190 ^ | 191 | | 192 | v 193 +------------------------------------------------------------------+ 194 | | 195 | M46E Prefix Resolution Table (M46E-PR Table) | 196 | | 197 +------------------------------------------------------------------+ 199 Figure 4 201 Figure Figure 5show M46E-PR Table. This table consists four parts, 202 IPv4 network plane ID, IPv4 address, netmask, and M46A prefix. 204 +---------------------+------------+-------++-----------------------+ 205 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 206 +---------------------+------------+-------++-----------------------+ 207 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 208 +---------------------+------------+-------++-----------------------+ 209 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 210 +---------------------+------------+-------++-----------------------+ 211 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 212 +---------------------+------------+-------++-----------------------+ 213 : : : 214 +---------------------+------------+-------++-----------------------+ 215 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 216 +---------------------+------------+-------++-----------------------+ 218 Figure 5 220 M46E-PR configured IPv4 network plane ID, so M46E-PR know IPv4 221 network plane ID value the interface belongs. 223 Resolving destination address, M46E-PR use pre-configured IPv4 224 network plane ID valude, and destination address of IPv4 packets, and 225 serch the M46E-PR table. M46E-PR table return the M46E-PR address 226 prefix value correspoiding IPv4 network plane ID and IPv4 destination 227 address. Then M46E-PR generate whole M46E-PR address. 229 Resolving source address, M46E-PR already know IPv4 network plane ID 230 value and IPv6 address prefix as M46E-PR prefix. So, searching the 231 M46E-PR table does not require for resolving source address. 233 4. Mode of M46E-PR 235 M46E-PR has two working mode, one is router mode, another is host 236 mode. 238 4.1. Router mode 240 In router mode, M46E-PR act as a IPv6 router. M46E-PR occupy IPv6 241 subnet, and M46E-PR advertise route for M46E-PR. 243 4.2. Host mode 245 In host mode, M46E-PR act as a IPv6 host. M46E-PR share IPv4 subnet, 246 that mean, M46E-PR and IPv6 hosts exists on same IPv6 subnet. M46E- 247 PR do proxy NDP function for IPv4 host. 249 5. Sample configuration 251 Figure Figure 6shows sample confiuration of M46E-PR. In this 252 example, there are three IPv4 stub network with the same IPv4 network 253 plane. 255 /------------\ /--------------------------------------/ 256 | | | Stub Network #1 | 257 | | | 2001:0db8:0:1::/64 | 258 | | | +--------+ /----------------------\ | 259 | |--| |M46E-PR |--|10.1.1.0/24(plane 1) | | 260 | | | +--------+ | | | 261 | | | \----------------------/ | 262 | <--[2001:0db8:0:1::/64] | 263 | | /--------------------------------------/ 264 | | 265 | | /--------------------------------------/ 266 | | | Stub Network #2 | 267 | | | 2001:0db8:0:2::/64 | 268 | Backbone | | +--------+ /----------------------\ | 269 | Network |--| |M46E-PR |--|10.1.2.0/24(plane 1) | | 270 | | | +--------+ | | | 271 | | | \----------------------/ | 272 | <--[2001:0db8:0:2::/64] | 273 | | /--------------------------------------/ 274 | | 275 | | /--------------------------------------/ 276 | | | Stub Network #3 | 277 | | | 2001:0db8:0:3::/64 | 278 | | | +--------+ /----------------------\ | 279 | |--| |M46E-PR |--|10.1.3.0/24(plane 1) | | 280 | | | +--------+ | | | 281 | | | \----------------------/ | 282 | <--[2001:0db8:0:3::/64] | 283 | | /--------------------------------------/ 284 | | 285 \------------/ 287 Figure 6 289 Figure Figure 7 shows M46E-PR table for sample network. 291 +---------------------+------------+-------++-----------------------+ 292 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 293 +---------------------+------------+-------++-----------------------+ 294 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:1 | 295 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:2 | 296 | 1 | 10.1.3.0 | /120 || 2001:0db8:0:3 | 297 +---------------------+------------+-------++-----------------------+ 299 Figure 7 301 6. IANA Considerations 303 This document makes no request of IANA. 305 Note to RFC Editor: this section may be removed on publication as an 306 RFC. 308 7. Security Considerations 310 Security Considerations does not discussed in this memo. 312 8. Normative References 314 [I-D.draft-matsuhira-m46a] 315 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 316 June 2019. 318 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 319 Requirement Levels", BCP 14, RFC 2119, 320 DOI 10.17487/RFC2119, March 1997, 321 . 323 Author's Address 325 Naoki Matsuhira 326 Fujitsu Limited 327 17-25, Shinkamata 1-chome, Ota-ku 328 Tokyo 144-8588 329 Japan 331 Phone: +81-3-3735-1111 332 Email: matsuhira@fujitsu.com