| Internet-Draft | ME6E-FP | April 2024 |
| Matsuhira | Expires 6 October 2024 | [Page] |
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.¶
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].¶
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 https://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 6 October 2024.¶
Copyright (c) 2024 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 (https://trustee.ietf.org/license-info) in effect on the date of 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 Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
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.¶
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) |
| | | | | |
\--------------/ \--------------/ \--------------/
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.¶
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) | \-------------------/ \-----------------------------/
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.¶
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¶
| 80 - m - n bits | m bits | n bits | +-----------------------+--------------------------+----------------+ | ME6 address prefix | Multiple net plane ID |Ethernet address| +-----------------------+--------------------------+----------------+
ME6 address consists of three parts as follows.¶
ME6 address is resolved by copying ethernet MAC address in inner ethernet frame, and preconfigured values, ME6 prefix and multiple network plane ID.¶
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] .¶
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 IPv6 network. Some example are shown as follows. These address is based on EUI-48 MAC address. EUI-64 address is the future study.¶
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 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--------------->
Where:¶
16bits plane ID can represent 65535 ethernet network plane.¶
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----->
Where:¶
32bits plane ID can represent about 4.3 billion ethernet network plane.¶
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.¶
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, "<ME6E-FP address prefix><multiple network plane ID>/ prefix length of ME6E-FP route".¶
ME6E-FP has following useful characteristics.¶
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.¶
ME6E-FP use automatic tunneling technologies. Security consideration related tunneling technologies are discussed in RFC2893 [RFC2893], RFC2267 [RFC2267], etc.¶