idnits 2.17.1 draft-matsuhira-m4p6e-11.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 (18 December 2021) is 857 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC1631' is mentioned on line 269, but not defined ** Obsolete undefined reference: RFC 1631 (Obsoleted by RFC 3022) == Missing Reference: 'RFC0792' is mentioned on line 261, but not defined == Missing Reference: 'RFC1191' is mentioned on line 265, but not defined == Missing Reference: 'RFC4303' is mentioned on line 282, but not defined == Missing Reference: 'RFC2893' is mentioned on line 278, but not defined ** Obsolete undefined reference: RFC 2893 (Obsoleted by RFC 4213) == Missing Reference: 'RFC2267' is mentioned on line 273, but not defined ** Obsolete undefined reference: RFC 2267 (Obsoleted by RFC 2827) Summary: 3 errors (**), 0 flaws (~~), 8 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 18 December 2021 5 Expires: 21 June 2022 7 Multiple IPv4 address and port number - IPv6 address mapping 8 encapsulation (M4P6E) 9 draft-matsuhira-m4p6e-11 11 Abstract 13 This document specifies Multiple IPv4 address and port number - IPv6 14 address mapping encapulation (M4P6E) specification. 16 Requirements Language 18 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 19 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 20 document are to be interpreted as described in RFC 2119 [RFC2119]. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on 21 June 2022. 39 Copyright Notice 41 Copyright (c) 2021 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 46 license-info) in effect on the date of publication of this document. 47 Please review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. Code Components 49 extracted from this document must include Revised BSD License text as 50 described in Section 4.e of the Trust Legal Provisions and are 51 provided without warranty as described in the Revised BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Architecture of M4P6E . . . . . . . . . . . . . . . . . . . . 2 57 3. M4P6E address format . . . . . . . . . . . . . . . . . . . . 3 58 4. Using M4P6E in client server environments . . . . . . . . . . 3 59 4.1. Client environments . . . . . . . . . . . . . . . . . . . 3 60 4.2. Server environments . . . . . . . . . . . . . . . . . . . 4 61 4.3. Data Center Environments . . . . . . . . . . . . . . . . 5 62 5. Port Number Issue . . . . . . . . . . . . . . . . . . . . . . 6 63 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 64 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 65 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 66 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 67 8.2. References . . . . . . . . . . . . . . . . . . . . . . . 7 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 70 1. Introduction 72 This document provides Multiple IPv4 address and port number - IPv6 73 address mapping encapulation (M4P6E) base specification. 75 M4P6E provide IPv4 address sharing function without Network Address 76 Translation (NAT [RFC1631]). M4P6E require IPv6 network. 78 2. Architecture of M4P6E 80 Figure 1 shows M4P6E address architecture. M4P6E address consists 81 four parts, M4P6E prefix, IPv4 network plane ID, IPv4 address, and 82 Port number. 84 | | | | | 85 | 80 - m bits | m bits | 32 bits | 16 bits | 86 +----------------------+----------------+----------------+----:----+ 87 | M4P6E prefix | IPv4 network | IPv4 address | port | 88 | | plane ID | | number | 89 +----------------------+----------------+----------------+----:----+ 90 |<--------------- Locator (128 -n bits )-------------------->:<-->| 91 | : ID | 92 | (n bits) 94 Figure 1 96 In M4P6E, boundary of locator and identifier is in port number part, 97 that mean, M4P6E use upper part of port number as locator, and lower 98 part of port number as identifier. 100 3. M4P6E address format 102 Figure 2 show a example of M4P6E address format. In this example, 103 16bits IPv4 network plane ID is used, that provide 65535 IPv4 network 104 plane. 106 | 3 | 45bits | 16bits | 16 bits| 32bits | 16 bits | 107 +---+------------------+---------+---------+------------+---------+ 108 |001| routing prefix |subnet id| plane ID|IPv4 address| Port # | 109 +---+------------------+---------+----------------------+---------+ 111 Figure 2 113 4. Using M4P6E in client server environments 115 4.1. Client environments 117 Figure 3 shows a example of M4P6E usage in client environments. In 118 this document, NAPT is IPv4 - IPv4 Netowrk address and port number 119 translator. Coopetation with NAPT, M4P6E provide IPv4 address 120 sharing with different users. 122 +--------------+ 123 | | +---------+ +--------+ +---------+ 124 | +----| M4P6E |--| NAPT |--+--| Clients | 125 | | +---------+ +--------+ | +---------+ 126 | | | +---------+ 127 | | +--| Clients | 128 | Backbone | | +---------+ 129 | | : 130 | | | +---------+ 131 | Network | +--| Clients | 132 | | +---------+ 133 | | 134 | | +---------+ +--------+ +---------+ 135 | +----| M4P6E |--| NAPT |--+--| Clients | 136 | | +---------+ +--------+ | +---------+ 137 | | | +---------+ 138 | | +--| Clients | 139 | | | +---------+ 140 | | : 141 | | | +---------+ 142 | | +--| Clients | 143 | | +---------+ 144 : : : : : 145 | | +---------+ +--------+ +---------+ 146 | +----| M4P6E |--| NAPT |--+--| Clients | 147 | | +---------+ +--------+ | +---------+ 148 | | | +---------+ 149 | | +--| Clients | 150 | | | +---------+ 151 | | : 152 | | | +---------+ 153 | | +--| Clients | 154 | | +---------+ 155 +--------------+ 157 Figure 3 159 4.2. Server environments 161 Figure 4 shows an example of M4P6E usage in server environments. In 162 this example, server terminate M4P6E tunnel. This case, Server 163 require at least one port number per server, that mean, 128bits host 164 route advertise for server access via IPv4. This case, full access 165 is provided via IPv6. 167 +--------------+ 168 | | +------------+ 169 | +----|Server with | 170 | | |M4P6E | 171 | Backbone | |function | 172 | | +------------+ 173 | | +------------+ 174 | Network +----|Server with | 175 | | |M4P6E | 176 | | |function | 177 | | +------------+ 178 : : : 179 | | +------------+ 180 | +----|Server with | 181 | | |M4P6E | 182 | | |function | 183 | | +------------+ 184 +--------------+ 186 Figure 4 188 4.3. Data Center Environments 190 Figure 5 shows an example of M4P6E usage in Data Center environments. 191 In this example, M4P6E is used only in Data Center Backend Network 192 closely. Client which is connected via backbone network does not 193 know the exists of M4P6E. M4P6E can provide at least one port number 194 per server, this case, 128bits host route is advertised, however this 195 route in advertised only in data center backbone network. Ofcource, 196 IPv6 address may allocated to the server, so full access is provided 197 via IPv6. 199 . 200 +--------+ . +-------+ 201 | | +-------+ . | | +-----------------+ 202 | +--+ | . | |-| Server w/M4P6E | 203 | | | Data | . | Data | +-----------------+ 204 |Backbone+--+Center | +----------+ |Center | +-----------------+ 205 | | | +--| M4P6E |--+ |-| Server w/M4P6E | 206 | | |Front | +----------+ |Backend| +-----------------+ 207 |Network | |Network| . |Network| +-----------------+ 208 | | | | +----------+ | |-| Server w/M4P6E | 209 | | | +--| M4P6E |--+ | +-----------------+ 210 | | | | +----------+ | | +-----------------+ 211 : : : : . | |-| Server w/M4P6E | 212 | | | | . | | +-----------------+ 213 | | | | . | | : 214 | | | | . | | +-----------------+ 215 | | | | . | |-| Server w/M4P6E | 216 | | +-------+ . | | +-----------------+ 217 +--------+ . +-------+ 218 . 219 -Normal IPv4 communication->.<----- M4P6E -----> 220 . communication 221 . 222 ------- Normal IPv6 communication -----------------> 223 . 225 Figure 5 227 5. Port Number Issue 229 M4P6E require port number of transport layer. M4P6E can not support 230 ICMPv4 [RFC0792]. The function provided by ICMPv4 does not work in 231 M4P6E environments, such as Path MTU Discovery [RFC1191], ping 232 command, etc. 234 M4P6E can not also support IPv4 IPsec ESP [RFC4303] because transport 235 header is encrypted. 237 6. IANA Considerations 239 This document makes no request of IANA. 241 Note to RFC Editor: this section may be removed on publication as an 242 RFC. 244 7. Security Considerations 246 M4P6E use automatic tunneling technologies. Security consideration 247 related tunneling technologies are discussed in RFC2893 [RFC2893], 248 RFC2267 [RFC2267], etc. 250 8. References 252 8.1. Normative References 254 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 255 Requirement Levels", BCP 14, RFC 2119, 256 DOI 10.17487/RFC2119, March 1997, 257 . 259 8.2. References 261 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 262 RFC 792, DOI 10.17487/RFC0792, September 1981, 263 . 265 [RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, 266 DOI 10.17487/RFC1191, November 1990, 267 . 269 [RFC1631] Egevang, K. and P. Francis, "The IP Network Address 270 Translator (NAT)", RFC 1631, DOI 10.17487/RFC1631, May 271 1994, . 273 [RFC2267] Ferguson, P. and D. Senie, "Network Ingress Filtering: 274 Defeating Denial of Service Attacks which employ IP Source 275 Address Spoofing", RFC 2267, DOI 10.17487/RFC2267, January 276 1998, . 278 [RFC2893] Gilligan, R. and E. Nordmark, "Transition Mechanisms for 279 IPv6 Hosts and Routers", RFC 2893, DOI 10.17487/RFC2893, 280 August 2000, . 282 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 283 RFC 4303, DOI 10.17487/RFC4303, December 2005, 284 . 286 Author's Address 287 Naoki Matsuhira 288 Fujitsu Limited 289 17-25, Shinkamata 1-chome, Ota-ku, 290 144-8588 291 Japan 293 Phone: +81-3-3735-1111 294 Email: naoki.matsuhira@gmail.com