idnits 2.17.1 draft-matsuhira-m46e-pr-00.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 (February 4, 2016) is 2975 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 February 4, 2016 5 Expires: August 7, 2016 7 Multiple IPv4 - IPv6 address mapping encapsulation - prefix resolution 8 (M46E-PR) 9 draft-matsuhira-m46e-pr-00 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 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 August 7, 2016. 42 Copyright Notice 44 Copyright (c) 2016 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. Basic Network Configuration . . . . . . . . . . . . . . . . . . 3 61 3. Basic Function of M46E-PR . . . . . . . . . . . . . . . . . . . 4 62 3.1. IPv4 over IPv6 Encapsulation / Decapsulation . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . 7 69 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 72 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 76 1. Introduction 78 This document provide M46E Prefix Resolution (M46E-PR) specification. 80 The basic strategy for IPv6 deployment is dual stack. However, 81 because of exhaustion of IPv4 address, there will be no IPv4 82 addresses for configuring dual stack in near future. That means 83 there will be IPv6 only networks automatically. 85 However, there are many IPv4 only networks still exist and those 86 seems continuous use in near future. That means methods continuous 87 use of IPv4 network over IPv6 only network will be required. 89 M46E-PR also provide such methots. 91 2. Basic Network Configuration 93 Figure 1 shows network configuration with M46E-PR. The network 94 consists of three parts, backbone network, stub network, and M46E-PR. 96 Backbone network can be operated with IPv6 only. Stub network has 97 three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6 98 only. 100 M46E-FP connects backbone network and stub network in case IPv4 still 101 works in that stub network. If stub network is IPv6 only, M46E-PR is 102 not needed. 104 /---------------------------------------------------\ 105 | | 106 | Backbone Network | 107 | (IPv6 only) | 108 | | 109 \---------------------------------------------------/ 110 | | | 111 | | | 112 | | | 113 +----------+ +----------+ | 114 /-| M46E-PR |-\ /-| M46E-PR |-\ /--------------\ 115 | +----------+ | | +----------+ | | | 116 | | | | | | 117 | Stub Network | | Stub Network | | Stub Network | 118 | (IPv4 only) | | (Dual Stack) | | (IPv6 only) | 119 | | | | | | 120 \--------------/ \--------------/ \--------------/ 121 Figure 1 123 3. Basic Function of M46E-PR 125 M46E-PR has mainly two function. One is IPv4 over IPv6 Encapsulation 126 / Decapsulation, and another is generate a table where IPv4 stub 127 network belong to IPv6 network. 129 3.1. IPv4 over IPv6 Encapsulation / Decapsulation 131 M46E-PR excapsulates IPv4 packet to IPv6 from stub network to 132 backbone network, and decapsulates IPv6 packet to IPv4 from backbone 133 network to stub network. Figure 2 shows packet format on both 134 backbone network and stub network. 136 +--------+------------+ +----------+--------+------------+ 137 |IPv4 Hdr| Data | --> | IPv6 Hdr |IPv4 Hdr| Data | 138 +--------+------------+ +----------+--------+------------+ 140 +--------+------------+ +----------+--------+------------+ 141 |IPv4 Hdr| Data | <-- | IPv6 Hdr |IPv4 Hdr| Data | 142 +--------+------------+ +----------+--------+------------+ 144 /-------------------\ +----------+ /-----------------------------\ 145 | Stub Network |--| M46E-PR |--| Backbone Network | 146 | (IPv4) | +----------+ | (IPv6 only) | 147 \-------------------/ \-----------------------------/ 149 Figure 2 151 3.2. M46A architecture 153 M46A is a IPv6 address used in outer IPv6 header which encapsulate 154 IPv4 packet by M46E-PR. M46A is described in 155 [I-D.draft-matsuhira-m46a].Figure 3 shows M46A address architecture. 157 | 96 - m bits | m bits | 32 bits | 158 +--------------------------+------------------------+--------------+ 159 | M46A prefix | IPv4 network plane ID | IPv4 address | 160 +--------------------------+------------------------+--------------+ 162 Figure 3 164 M46E address consists of three parts as follows. 166 M46A prefix 168 M46A prefix. This value is not a fixed value, and resolved packet 169 by packet 171 IPv4 network plane ID IPv4 network plane ID is an identifier of IPv4 172 network stack over IPv6 backbone network. 174 IPv4 address 176 IPv4 address in inner IPv4 packet. 178 3.3. Resolving M46A 180 M46E-PR resolve M46A using M46E Prefix Resolution Table (M46E-PR 181 Table). M46E-PR generate M46E-PR address resolving M46A prefix from 182 IPv4 network plane ID and IPv4 address. FigureFigure 4 show this 183 processing. 185 | 96 - m bits | m bits | 32 bits | 186 +--------------------------+------------------------+--------------+ 187 | M46A prefix | IPv4 network plane ID | IPv4 address | 188 +--------------------------+------------------------+--------------+ 190 \--------------------------/\--------------------------------------/ 191 ^ | 192 | | 193 | v 194 +------------------------------------------------------------------+ 195 | | 196 | M46E Prefix Resolution Table (M46E-PR Table) | 197 | | 198 +------------------------------------------------------------------+ 200 Figure 4 202 Figure Figure 5show M46E-PR Table. This table consists four parts, 203 IPv4 network plane ID, IPv4 address, netmask, and M46A prefix. 205 +---------------------+------------+-------++-----------------------+ 206 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 207 +---------------------+------------+-------++-----------------------+ 208 |IPv4 network plane ID|IPv4 address|netmask||M46A 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 : : : 215 +---------------------+------------+-------++-----------------------+ 216 |IPv4 network plane ID|IPv4 address|netmask||M46A prefix | 217 +---------------------+------------+-------++-----------------------+ 219 Figure 5 221 M46E-PR configured IPv4 network plane ID, so M46E-PR know IPv4 222 network plane ID value the interface belongs. 224 Resolving destination address, M46E-PR use pre-configured IPv4 225 network plane ID valude, and destination address of IPv4 packets, and 226 serch the M46E-PR table. M46E-PR table return the M46E-PR address 227 prefix value correspoiding IPv4 network plane ID and IPv4 destination 228 address. Then M46E-PR generate whole M46E-PR address. 230 Resolving source address, M46E-PR already know IPv4 network plane ID 231 value and IPv6 address prefix as M46E-PR prefix. So, searching the 232 M46E-PR table does not require for resolving source address. 234 4. Mode of M46E-PR 236 M46E-PR has two working mode, one is router mode, another is host 237 mode. 239 4.1. Router mode 241 In router mode, M46E-PR act as a IPv6 router. M46E-PR occupy IPv6 242 subnet, and M46E-PR advertise route for M46E-PR. 244 4.2. Host mode 246 In host mode, M46E-PR act as a IPv6 host. M46E-PR share IPv4 subnet, 247 that mean, M46E-PR and IPv6 hosts exists on same IPv6 subnet. 248 M46E-PR do proxy NDP function for IPv4 host. 250 5. Sample configuration 252 Figure Figure 6shows sample confiuration of M46E-PR. In this 253 example, there are three IPv4 stub network with the same IPv4 network 254 plane. 256 /------------\ /--------------------------------------/ 257 | | | Stub Network #1 | 258 | | | 2001:0db8:0:1::/64 | 259 | | | +--------+ /----------------------\ | 260 | |--| |M46E-PR |--|10.1.1.0/24(plane 1) | | 261 | | | +--------+ | | | 262 | | | \----------------------/ | 263 | <--[2001:0db8:0:1::/64] | 264 | | /--------------------------------------/ 265 | | 266 | | /--------------------------------------/ 267 | | | Stub Network #2 | 268 | | | 2001:0db8:0:2::/64 | 269 | Backbone | | +--------+ /----------------------\ | 270 | Network |--| |M46E-PR |--|10.1.2.0/24(plane 1) | | 271 | | | +--------+ | | | 272 | | | \----------------------/ | 273 | <--[2001:0db8:0:2::/64] | 274 | | /--------------------------------------/ 275 | | 276 | | /--------------------------------------/ 277 | | | Stub Network #3 | 278 | | | 2001:0db8:0:3::/64 | 279 | | | +--------+ /----------------------\ | 280 | |--| |M46E-PR |--|10.1.3.0/24(plane 1) | | 281 | | | +--------+ | | | 282 | | | \----------------------/ | 283 | <--[2001:0db8:0:3::/64] | 284 | | /--------------------------------------/ 285 | | 286 \------------/ 288 Figure 6 290 Figure Figure 7 shows M46E-PR table for sample network. 292 +---------------------+------------+-------++-----------------------+ 293 |IPv4 network plane ID|IPv4 address|netmask||M46E-PR address prefix | 294 +---------------------+------------+-------++-----------------------+ 295 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:1 | 296 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:2 | 297 | 1 | 10.1.3.0 | /120 || 2001:0db8:0:3 | 298 +---------------------+------------+-------++-----------------------+ 300 Figure 7 302 6. IANA Considerations 304 This document makes no request of IANA. 306 Note to RFC Editor: this section may be removed on publication as an 307 RFC. 309 7. Security Considerations 311 Security Considerations does not discussed in this memo. 313 8. References 315 8.1. Normative References 317 [I-D.draft-matsuhira-m46a] 318 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 319 February 2016. 321 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 322 Requirement Levels", BCP 14, RFC 2119, March 1997. 324 8.2. Informative References 325 Author's Address 327 Naoki Matsuhira 328 Fujitsu Limited 329 17-25, Shinkamata 1-chome, Ota-ku 330 Tokyo, 144-8588 331 Japan 333 Phone: +81-3-3730-8386 334 Fax: 335 Email: matsuhira@jp.fujitsu.com