| Internet-Draft | M4P6E | April 2024 |
| Matsuhira | Expires 6 October 2024 | [Page] |
This document specifies Multiple IPv4 address and port number - IPv6 address mapping encapulation (M4P6E) specification.¶
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 IPv4 address and port number - IPv6 address mapping encapulation (M4P6E) base specification.¶
M4P6E provide IPv4 address sharing function without Network Address Translation (NAT [RFC1631]). M4P6E require IPv6 network.¶
Figure 1 shows M4P6E address architecture. M4P6E address consists four parts, M4P6E prefix, IPv4 network plane ID, IPv4 address, and Port number.¶
| | | | | | 80 - m bits | m bits | 32 bits | 16 bits | +----------------------+----------------+----------------+----:----+ | M4P6E prefix | IPv4 network | IPv4 address | port | | | plane ID | | number | +----------------------+----------------+----------------+----:----+ |<--------------- Locator (128 -n bits )-------------------->:<-->| | : ID | | (n bits)
In M4P6E, boundary of locator and identifier is in port number part, that mean, M4P6E use upper part of port number as locator, and lower part of port number as identifier.¶
Figure 2 show a example of M4P6E address format. In this example, 16bits IPv4 network plane ID is used, that provide 65535 IPv4 network plane.¶
| 3 | 45bits | 16bits | 16 bits| 32bits | 16 bits | +---+------------------+---------+---------+------------+---------+ |001| routing prefix |subnet id| plane ID|IPv4 address| Port # | +---+------------------+---------+----------------------+---------+
Figure 3 shows a example of M4P6E usage in client environments. In this document, NAPT is IPv4 - IPv4 Netowrk address and port number translator. Coopetation with NAPT, M4P6E provide IPv4 address sharing with different users.¶
+--------------+ | | +---------+ +--------+ +---------+ | +----| M4P6E |--| NAPT |--+--| Clients | | | +---------+ +--------+ | +---------+ | | | +---------+ | | +--| Clients | | Backbone | | +---------+ | | : | | | +---------+ | Network | +--| Clients | | | +---------+ | | | | +---------+ +--------+ +---------+ | +----| M4P6E |--| NAPT |--+--| Clients | | | +---------+ +--------+ | +---------+ | | | +---------+ | | +--| Clients | | | | +---------+ | | : | | | +---------+ | | +--| Clients | | | +---------+ : : : : : | | +---------+ +--------+ +---------+ | +----| M4P6E |--| NAPT |--+--| Clients | | | +---------+ +--------+ | +---------+ | | | +---------+ | | +--| Clients | | | | +---------+ | | : | | | +---------+ | | +--| Clients | | | +---------+ +--------------+
Figure 4 shows an example of M4P6E usage in server environments. In this example, server terminate M4P6E tunnel. This case, Server require at least one port number per server, that mean, 128bits host route advertise for server access via IPv4. This case, full access is provided via IPv6.¶
+--------------+ | | +------------+ | +----|Server with | | | |M4P6E | | Backbone | |function | | | +------------+ | | +------------+ | Network +----|Server with | | | |M4P6E | | | |function | | | +------------+ : : : | | +------------+ | +----|Server with | | | |M4P6E | | | |function | | | +------------+ +--------------+
Figure 5 shows an example of M4P6E usage in Data Center environments. In this example, M4P6E is used only in Data Center Backend Network closely. Client which is connected via backbone network does not know the exists of M4P6E. M4P6E can provide at least one port number per server, this case, 128bits host route is advertised, however this route in advertised only in data center backbone network. Ofcource, IPv6 address may allocated to the server, so full access is provided via IPv6.¶
.
+--------+ . +-------+
| | +-------+ . | | +-----------------+
| +--+ | . | |-| Server w/M4P6E |
| | | Data | . | Data | +-----------------+
|Backbone+--+Center | +----------+ |Center | +-----------------+
| | | +--| M4P6E |--+ |-| Server w/M4P6E |
| | |Front | +----------+ |Backend| +-----------------+
|Network | |Network| . |Network| +-----------------+
| | | | +----------+ | |-| Server w/M4P6E |
| | | +--| M4P6E |--+ | +-----------------+
| | | | +----------+ | | +-----------------+
: : : : . | |-| Server w/M4P6E |
| | | | . | | +-----------------+
| | | | . | | :
| | | | . | | +-----------------+
| | | | . | |-| Server w/M4P6E |
| | +-------+ . | | +-----------------+
+--------+ . +-------+
.
-Normal IPv4 communication->.<----- M4P6E ----->
. communication
.
------- Normal IPv6 communication ----------------->
.
M4P6E require port number of transport layer. M4P6E can not support ICMPv4 [RFC0792]. The function provided by ICMPv4 does not work in M4P6E environments, such as Path MTU Discovery [RFC1191], ping command, etc.¶
M4P6E can not also support IPv4 IPsec ESP [RFC4303] because transport header is encrypted.¶
This document makes no request of IANA.¶
Note to RFC Editor: this section may be removed on publication as an RFC.¶
M4P6E use automatic tunneling technologies. Security consideration related tunneling technologies are discussed in RFC2893 [RFC2893], RFC2267 [RFC2267], etc.¶