Network Working Group N. Matsuhira Internet-Draft Fujitsu Limited Intended status: Informational April 19, 2016 Expires: October 21, 2016 Multiple Ethernet - IPv6 address mapping encapsulation - fixed prefix draft-matsuhira-me6e-fp-01 Abstract This document specifies Multiple Ethernet - IPv6 address mapping encapsulation - fixed prefix (ME6E-FP) base specification. ME6E-FP makes expantion ethernet network over IPv6 backbone network with encapsuation technoogy. And also, E6ME-FP can stack multiple Ethernet networks. ME6E-FP work on own routing domain. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on October 21, 2016. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Matsuhira Expires October 21, 2016 [Page 1] Internet-Draft ME6E-FP April 2016 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Basic Network Configuration . . . . . . . . . . . . . . . . . . 3 3. Basic Function of ME6E-FP . . . . . . . . . . . . . . . . . . . 4 3.1. Ethernet over IPv6 Encapsulation . . . . . . . . . . . . . 4 3.2. Multiple Ethernet - IPv6 mapped address (ME6A) architecture . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Route Advertisement . . . . . . . . . . . . . . . . . . . . 5 4. ME6E-FP address format . . . . . . . . . . . . . . . . . . . . 5 4.1. IPv6 Global Unicast Address . . . . . . . . . . . . . . . . 6 4.2. 16bits plane ID ME6 address . . . . . . . . . . . . . . . . 6 4.3. 32bits plane ID ME6 address . . . . . . . . . . . . . . . . 7 4.4. mixture and renumbering of ME6 address . . . . . . . . . . 7 5. Configuration of ME6E-FP . . . . . . . . . . . . . . . . . . . 8 6. Characteristic . . . . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8 9.2. References . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 Matsuhira Expires October 21, 2016 [Page 2] Internet-Draft ME6E-FP April 2016 1. Introduction This document provides Multiple Ethernet - IPv6 address mapping encapsulation - fixed prefix (ME6E-FP) base specification. ME6E-FP make many virtual ethernet network over IPv6 network with unicast base technology. ME6E-FP can use on own routing domain, i.e. can advertise routes to the network. 2. Basic Network Configuration Figure 1 shows network configuration with ME6E-FP. The network consists of three parts. IPv6 network, Nodes (Host or Router) , and ME6E-FP. Backbone network is operated with Dual Stack or IPv6 only. Node may physical node or virtual node, and have Ethernet Interface. ME6E-FP connects IPv6 network and nodes. ME6E-FP connect to node with Ethernet (Layer2), and ME6E-FP connect to IPv6 network with IPv6 (Layer3). /---------------------------------------------------\ | | | IPv6 Network | | (Dual stack or IPv6 only) | | | \---------------------------------------------------/ | | +-------+ +------------------------+ |E6ME-FP| | E6ME-FP | +-------+ +------------------------+ | | | /--------------\ /--------------\ /--------------\ | | | | | | | Node | | Node | | Node | |(Host/Router) | |(Host/Router) | |(Host/Router) | | | | | | | \--------------/ \--------------/ \--------------/ Figure 1 Matsuhira Expires October 21, 2016 [Page 3] Internet-Draft ME6E-FP April 2016 3. Basic Function of ME6E-FP ME6E-FP has mainly two function. One is encapsulate from Ethernet frame to IPv6 packet, and decapsulate from IPv6 packet to Ethernet frame. Another is advertise route corresponding to Ethernet MAC address. 3.1. Ethernet over IPv6 Encapsulation ME6E-FP encapsulates ethernet frame to IPv6 packet from node to IPv6 network, and decapsulates IPv6 packet to ethernet frame from IPv6 network to node. Figure 2 shows encapsulation and decapsulation of Ethernet frame and IPv6 packet +--------+------------+ +----------+--------+------------+ |Ethr Hdr| Data | --> | IPv6 Hdr |Ethr Hdr| Data | +--------+------------+ +----------+--------+------------+ +--------+------------+ +----------+--------+------------+ |Ethr Hdr| Data | <-- | IPv6 Hdr |Ethr Hdr| Data | +--------+------------+ +----------+--------+------------+ /-------------------\ +-------+ /-----------------------------\ | Node |--|ME6E-FP|--| IPv6 Network | | (Host or Router) | +-------+ | (Dual Stack or IPv6 only) | \-------------------/ \-----------------------------/ Figure 2 The value of next header field of IPv6 header is TBD. The value of EtherIP [RFC3378] may used, however new value for this protocol may assigned. When encapsulated IPv6 Packet size exceed path MTU , ME6E-FP fragment Ethernet frame, and then send them. 3.2. Multiple Ethernet - IPv6 mapped address (ME6A) architecture ME6A[I-D.matsuhira-me6a] is a IPv6 address used in outer IPv6 header which encapsulate ethernet frame by ME6E-FP. Figure 3 shows ME6A architecture Matsuhira Expires October 21, 2016 [Page 4] Internet-Draft ME6E-FP April 2016 | 80 - m - n bits | m bits | n bits | +-----------------------+--------------------------+----------------+ | ME6 address prefix | Multiple net plane ID |Ethernet address| +-----------------------+--------------------------+----------------+ Figure 3 ME6 address consists of three parts as follows. ME6 address prefix ME6 address prefix . This value is preconfigured to all ME6E-FP in the IPv6 networks. Multiple network plane ID Multiple network plane ID is an identifier of Ethernet network over IPv6 backbone network. This value is preconfigured depend on the ME6E-FP belong which ethernet network plane. This value is just like VLAN-ID of IEEE802.1Q, tag VLAN. Ethernet address Ethernet MAC address in inner Ethernet frame. EUI-48 address or EUI-64 address. ME6 address is resolved by copying ethernet MAC address in inner ethernet frame, and preconfigured values, ME6 prefix and multiple network plane ID. 3.3. Route Advertisement ME6E-FP advertises ME6 address host route to the IPv6 network. The number of the route of ME6 addresses is the same as the number of MAC address table. In the IPv6 network, usual dynamic routing protocol for IPv6 can be used such as RIPng [RFC2080], OSPFv3 [RFC2740] and IS-IS [RFC5308] . 4. ME6E-FP address format ME6E-FP can be used closely in the IPv6 network, so ME6 address does not be advertised outside of the IPv6 network, and IPv6 packet which contains ME6 address does not be forwarded outside of the backbone network. So, ME6 address format and ME6 address prefix can be decided each Matsuhira Expires October 21, 2016 [Page 5] Internet-Draft ME6E-FP April 2016 IPv6 network. Some example are shown as follows. These address is based on EUI-48 MAC address. EUI-64 address is the future study. 4.1. IPv6 Global Unicast Address This example is based on IPv6 Global Unicast Address Format [RFC3587]. Figure 4 shows IPv6 Global Unicast Address Format. | 3 | 45bits | 16bits | 64bits | +---+-----------------------+-----------+--------------------------+ |001| Global routing prefix | subnet id | Interface ID | +---+-----------------------+-----------+--------------------------+ Figure 4 4.2. 16bits plane ID ME6 address Figure 5 shows ME6 address format with 16bits multiple network plane ID using part of IPv6 Global Unicast Address. | 3 | 45bits | 16bits | 16bits | 48bits | +---+-----------------------+-----------+--------------------------+ |001| Global routing prefix | subnet id | plane ID |EUI-48 address| +---+-----------------------+-----------+--------------------------+ <---ME6 address prefix---------------> Figure 5 Where: Global routing prefix global routing prefix subnet id indication for ME6 prefix. multiple network plane id ethernet network plane ID. Matsuhira Expires October 21, 2016 [Page 6] Internet-Draft ME6E-FP April 2016 EUI-48 address EUI-48 MAC address of inner ethernet frame. 16bits plane ID can represent 65535 ethernet network plane. 4.3. 32bits plane ID ME6 address Figure 6shows ME6 address format with 32bits plane ID using part of IPv6 Global Unicast Address. | 3 | 45bits | 32bits | 48bits | +---+-----------------------+--------------------------------------+ |001| Global routing prefix | plane ID |EUI-48 address| +---+-----------------------+--------------------------------------+ <---ME6 address prefix-----> Figure 6 Where: Global routing prefix global routing prefix multiple network plane id ethernet network plane ID. EUI-48 address EUI-48 MAC address of inner ethernet frame 32bits plane ID can represent about 4.3 billion ethernet network plane. 4.4. mixture and renumbering of ME6 address If ME6 address prefix does not overlap, ME6 address can co-existing. And also, ME6 address prefix may renumber, that mean, small start with 16bits plane ID ME6 address, then renumber to 32bits plane ID ME6 address. ME6E-FP provide flexible operation for scalability of multiple network plane id. Matsuhira Expires October 21, 2016 [Page 7] Internet-Draft ME6E-FP April 2016 5. Configuration of ME6E-FP Configuration of ME6E-FP require just three information, ME6 address prefix, multiple Network plane ID, and prefix length of ME6E-FP route. These information could explain just only one line, "/ prefix length of ME6E-FP route". 6. Characteristic ME6E-FP has following useful characteristics. o can operate unicast routing domain o TBD 7. IANA Considerations This document makes no request of IANA if using EtherIP Header. Note to RFC Editor: this section may be removed on publication as an RFC. 8. Security Considerations ME6E-FP use automatic tunneling technologies. Security consideration related tunneling technologies are discussed in RFC2893 [RFC2893], RFC2267 [RFC2267], etc. 9. References 9.1. Normative References [I-D.matsuhira-me6a] Matsuhira, N., "Multiple Ethernet - IPv6 mapped IPv6 address (ME6A)", April 2016. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3587] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global Unicast Address Format", RFC 3587, August 2003. Matsuhira Expires October 21, 2016 [Page 8] Internet-Draft ME6E-FP April 2016 9.2. References [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, January 1997. [RFC2267] Ferguson, P. and D. Senie, "Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing", RFC 2267, January 1998. [RFC2740] Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6", RFC 2740, December 1999. [RFC2893] Gilligan, R. and E. Nordmark, "Transition Mechanisms for IPv6 Hosts and Routers", RFC 2893, August 2000. [RFC3378] Housley, R. and S. Hollenbeck, "EtherIP: Tunneling Ethernet Frames in IP Datagrams", RFC 3378, September 2002. [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, October 2008. Author's Address Naoki Matsuhira Fujitsu Limited 17-25, Shinkamata 1-chome, Ota-ku Tokyo, 144-8588 Japan Phone: +81-3-3735-1111 Fax: Email: matsuhira@jp.fujitsu.com Matsuhira Expires October 21, 2016 [Page 9]