idnits 2.17.1 draft-matsuhira-me6e-pr-05.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 : ---------------------------------------------------------------------------- No issues found here. 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 (April 19, 2018) is 2170 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3378' is defined on line 321, but no explicit reference was found in the text -- No information found for draft-matsuhira-me6a - is the name correct? Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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 April 19, 2018 5 Expires: October 21, 2018 7 Multiple Ethernet - IPv6 address mapping encapsulation - prefix 8 resolution 9 draft-matsuhira-me6e-pr-05 11 Abstract 13 This document specifies Multiple Ethernet - IPv6 address mapping 14 encapsulation - Prefix Resolution (ME6E-PR) specification. ME6E-PR 15 makes expantion ethernet network over IPv6 backbone network with 16 encapsuation technoogy. And also, E6ME-PR can stack multiple 17 Ethernet networks. ME6E-PR work on non own routing domain. 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 October 21, 2018. 42 Copyright Notice 44 Copyright (c) 2018 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 ME6E-PR . . . . . . . . . . . . . . . . . . . 4 62 3.1. Ethernet over IPv6 Encapsulation . . . . . . . . . . . . . 4 63 3.2. Multiple Ethernet - IPv6 mapped address (ME6A) 64 architecture . . . . . . . . . . . . . . . . . . . . . . . 4 65 3.3. Resolving ME6E address . . . . . . . . . . . . . . . . . . 5 66 4. Sample configuration . . . . . . . . . . . . . . . . . . . . . 6 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 68 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 70 7.1. Normative References . . . . . . . . . . . . . . . . . . . 8 71 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 74 1. Introduction 76 This document provide Multiple Ethernet - IPv6 address mapping 77 encapsulation - Prefix Resolution (ME6E-PR) specification. 79 ME6E-PR make many virtual ethernet network over IPv6 network with 80 unicast base technology. 82 ME6E-PR can use on both own routing domain and non own routing 83 domain, i.e. can or cannot advertise routes to the network. 85 2. Basic Network Configuration 87 Figure 1 shows network configuration with ME6E-PR. The network 88 consists of three parts, backbone network, nodes (host or router), 89 and ME6E-PR. 91 Backbone network can be operated with dual stack or IPv6 only. Node 92 may physical node or virtual node, and have Ethernet Interface. 94 ME6E-PR connects IPv6 network and nodes. ME6E-PR connect to node 95 with Ethernet (Layer2), and ME6E-PR connect to IPv6 network with IPv6 96 (Layer3). 98 /---------------------------------------------------\ 99 | | 100 | IPv6 Network | 101 | (Dual stack or IPv6 only) | 102 | | 103 \---------------------------------------------------/ 104 | | 105 +-------+ +------------------------+ 106 |E6ME-PR| | E6ME-PR | 107 +-------+ +------------------------+ 108 | | | 109 /--------------\ /--------------\ /--------------\ 110 | | | | | | 111 | Node | | Node | | Node | 112 |(Host/Router) | |(Host/Router) | |(Host/Router) | 113 | | | | | | 114 \--------------/ \--------------/ \--------------/ 116 Figure 1 118 3. Basic Function of ME6E-PR 120 ME6E-PR has mainly two function. 122 One is encapsulate from Ethernet frame to IPv6 packet, and 123 decapsulate from IPv6 packet to Ethernet frame. Another is generate 124 a table where Ethernet MAC address belong to IPv6 network. 126 3.1. Ethernet over IPv6 Encapsulation 128 ME6E-PR encapsulates Ethernet frame to IPv6 packet from node to IPv6 129 network, and decapsulates IPv6 packet to Ethernet frame from IPv6 130 network to node. Figure 2 shows frame and packet format on both IPv6 131 network and IPv6 network. 133 +--------+------------+ +----------+--------+------------+ 134 |Ethr Hdr| Data | --> | IPv6 Hdr |Ethr Hdr| Data | 135 +--------+------------+ +----------+--------+------------+ 137 +--------+------------+ +----------+--------+------------+ 138 |Ethr Hdr| Data | <-- | IPv6 Hdr |Ethr Hdr| Data | 139 +--------+------------+ +----------+--------+------------+ 141 /-------------------\ +----------+ /-----------------------------\ 142 | Node |--| ME6E-PR |--| IPv6 Network | 143 |(Host or Router) | +----------+ |(Dual stack or IPv6 only) | 144 \-------------------/ \-----------------------------/ 146 Figure 2 148 The value of next header field of IPv6 header is TBD. The value of 149 EtherIP(RFC3378) EtherIP [RFC3378]may used, however new value for 150 this protocol may assigned. 152 When encapsulated IPv6 Packet size exceed path MTU , ME6E-PR fragment 153 Ethernet frame, and then send them. 155 3.2. Multiple Ethernet - IPv6 mapped address (ME6A) architecture 157 ME6A[I-D.matsuhira-me6a] is a IPv6 address used in outer IPv6 header 158 which encapsulate ethernet frame by ME6E-PR. Figure 3 shows ME6A 159 architecture. 161 | 96 - m -n bits | m bits | n bits | 162 +--------------------------+------------------------+----------------+ 163 | ME6 address prefix | Multiple net plane ID |Ethernet address| 164 +--------------------------+------------------------+----------------+ 166 Figure 3 168 ME6E address consists of three parts as follows. 170 ME6 address prefix 172 ME6 address prefix. This value is resolved by ME6E-PR. 174 Multiple network plane ID 176 Multiple network plane ID is an identifier of Ethernet network 177 over IPv6 backbone network. This value is preconfigured depend on 178 the ME6E-RP belong which ethernet network plane. This value is 179 just like VLAN-ID of IEEE802.1Q, tag VLAN. 181 EThernet address 183 Ethernet MAC address in inner Ethernet frame. EUI-48 address or 184 EUI-64 address. 186 3.3. Resolving ME6E address 188 ME6E-PR resolve ME6 address using ME6E Prefix Resolution Table 189 (ME6E-PR Table). ME6E-PR generate ME6E-PR address resolving ME6E-PR 190 prefix from Multiple network plane ID and Ethernet MAC address. 191 Figure 4 show this processing. 193 | 96 - m -n bits | m bits | n bits | 194 +--------------------------+------------------------+----------------+ 195 | ME6 address prefix | Multiple net plane ID |Ethernet address| 196 +--------------------------+------------------------+----------------+ 198 \--------------------------/\--------------------------------------/ 199 ^ | 200 | | 201 | v 202 +------------------------------------------------------------------+ 203 | | 204 | ME6E Prefix Resolution Table (ME6E-PR Table) | 205 | | 206 +------------------------------------------------------------------+ 208 Figure 4 210 Figure 5 show ME6E-PR Table. This table consists four parts, 211 Multiple network plane ID, Ehernet address, netmask, and ME6 address 212 prefix. 214 +---------------------+----------------+-------++-------------------+ 215 |Multiple net plane ID|Ethernet address|netmask|| ME6 address prefix| 216 +---------------------+----------------+-------++-------------------+ 217 |Multiple net plane ID|Ethernet address|netmask|| ME6 address prefix| 218 +---------------------+----------------+-------++-------------------+ 219 |Multiple net plane ID|Ethernet address|netmask|| ME6 address prefix| 220 +---------------------+----------------+-------++-------------------+ 221 |Multiple net plane ID|Ethernet address|netmask|| ME6 address prefix| 222 +---------------------+----------------+-------++-------------------+ 223 : : : 224 +---------------------+----------------+-------++-------------------+ 225 |Multiple net plane ID|Ethernet address|netmask|| ME6 address prefix| 226 +---------------------+----------------+-------++-------------------+ 228 Figure 5 230 ME6E-PR configured multiple network plane ID, so ME6E-PR know 231 multiple network plane ID value the interface belongs. 233 Resolving destination address, ME6E-PR use pre-configured multiple 234 network plane ID valude, and destination MAC address of Ehernet 235 frame, and search the ME6E-PR table. ME6E-PR table return the ME6 236 address prefix value correspoiding multiple network plane ID and 237 ethernet destination MAC address. Then ME6E-PR generate whole ME6 238 address. 240 Resolving source address, ME6E-PR already know multiple network plane 241 ID value and IPv6 address prefix as ME6 prefix. So, searching the 242 ME6E-PR table does not require for resolving source address. 244 4. Sample configuration 246 Figure 6 shows sample confiuration of ME6E-PR. In this example, 247 there are three IPv4 stub network with the same IPv4 network plane. 249 /------------\ /--------------------------------------------/ 250 | | | Stub Network #1 | 251 | | | 2001:0db8:0:1::/64 | 252 | | | +--------+ /----------------------------\ | 253 | |--| |ME6E-PR|-- |00:00:00:00:00:01(plane 1) | | 254 | | | +--------+ | | | 255 | | | \----------------------------/ | 256 | <--[2001:0db8:0:1::/64] | 257 | | /--------------------------------------------/ 258 | | 259 | | /--------------------------------------------/ 260 | | | Stub Network #2 | 261 | | | 2001:0db8:0:2::/64 | 262 | Backbone | | +--------+ /----------------------------\ | 263 | Network |--| |ME6E-PR|-- |00:00:00:00:00:02(plane 1) | | 264 | | | +--------+ | | | 265 | | | \----------------------------/ | 266 | <--[2001:0db8:0:2::/64] | 267 | | /--------------------------------------------/ 268 | | 269 | | /--------------------------------------------/ 270 | | | Stub Network #3 | 271 | | | 2001:0db8:0:3::/64 | 272 | | | +--------+ /----------------------------\ | 273 | |--| |ME6E-PR|-- |00:00:00:00:00:03(plane 1) | | 274 | | | +--------+ | | | 275 | | | \----------------------------/ | 276 | <--[2001:0db8:0:3::/64] | 277 | | /--------------------------------------------/ 278 | | 279 \------------/ 281 Figure 6 283 Figure 7 shows ME6E-PR table for sample network. 285 +---------+-------------------+-------++----------------------+ 286 | plane ID| MAC address |netmask||ME6E-PR address prefix| 287 +---------+-------------------+-------++----------------------+ 288 | 1 | 00:00:00:00:00:01 | /128 || 2001:0db8:0:1 | 289 | 1 | 00:00:00:00:00:02 | /128 || 2001:0db8:0:2 | 290 | 1 | 00:00:00:00:00:03 | /128 || 2001:0db8:0:3 | 291 +---------+-------------------+-------++----------------------+ 293 Figure 7 295 5. IANA Considerations 297 This document makes no request of IANA if using EtherIP Header. 299 Note to RFC Editor: this section may be removed on publication as an 300 RFC. 302 6. Security Considerations 304 Security Considerations does not discussed in this memo. 306 7. References 308 7.1. Normative References 310 [I-D.matsuhira-me6a] 311 Matsuhira, N., "Multiple Ethernet - IPv6 mapped IPv6 312 address (ME6A)", April 2017. 314 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 315 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 316 RFC2119, March 1997, 317 . 319 7.2. Informative References 321 [RFC3378] Housley, R. and S. Hollenbeck, "EtherIP: Tunneling 322 Ethernet Frames in IP Datagrams", RFC 3378, DOI 10.17487/ 323 RFC3378, September 2002, 324 . 326 Author's Address 328 Naoki Matsuhira 329 Fujitsu Limited 330 17-25, Shinkamata 1-chome, Ota-ku 331 Tokyo, 144-8588 332 Japan 334 Phone: +81-3-3735-1111 335 Fax: 336 Email: matsuhira@jp.fujitsu.com