idnits 2.17.1 draft-matsuhira-m4p6e-09.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 (December 15, 2020) is 1225 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC1631' is mentioned on line 270, but not defined ** Obsolete undefined reference: RFC 1631 (Obsoleted by RFC 3022) == Missing Reference: 'RFC0792' is mentioned on line 262, but not defined == Missing Reference: 'RFC1191' is mentioned on line 266, but not defined == Missing Reference: 'RFC4303' is mentioned on line 283, but not defined == Missing Reference: 'RFC2893' is mentioned on line 279, but not defined ** Obsolete undefined reference: RFC 2893 (Obsoleted by RFC 4213) == Missing Reference: 'RFC2267' is mentioned on line 274, 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 December 15, 2020 5 Expires: June 18, 2021 7 Multiple IPv4 address and port number - IPv6 address mapping 8 encapsulation (M4P6E) 9 draft-matsuhira-m4p6e-09 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 June 18, 2021. 39 Copyright Notice 41 Copyright (c) 2020 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 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Architecture of M4P6E . . . . . . . . . . . . . . . . . . . . 2 58 3. M4P6E address format . . . . . . . . . . . . . . . . . . . . 3 59 4. Using M4P6E in client server environments . . . . . . . . . . 3 60 4.1. Client environments . . . . . . . . . . . . . . . . . . . 3 61 4.2. Server environments . . . . . . . . . . . . . . . . . . . 4 62 4.3. Data Center Environments . . . . . . . . . . . . . . . . 5 63 5. Port Number Issue . . . . . . . . . . . . . . . . . . . . . . 6 64 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 66 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 67 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 68 8.2. References . . . . . . . . . . . . . . . . . . . . . . . 7 69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7 71 1. Introduction 73 This document provides Multiple IPv4 address and port number - IPv6 74 address mapping encapulation (M4P6E) base specification. 76 M4P6E provide IPv4 address sharing function without Network Address 77 Translation (NAT [RFC1631]). M4P6E require IPv6 network. 79 2. Architecture of M4P6E 81 Figure 1 shows M4P6E address architecture. M4P6E address consists 82 four parts, M4P6E prefix, IPv4 network plane ID, IPv4 address, and 83 Port number. 85 | | | | | 86 | 80 - m bits | m bits | 32 bits | 16 bits | 87 +----------------------+----------------+----------------+----:----+ 88 | M4P6E prefix | IPv4 network | IPv4 address | port | 89 | | plane ID | | number | 90 +----------------------+----------------+----------------+----:----+ 91 |<--------------- Locator (128 -n bits )-------------------->:<-->| 92 | : ID | 93 | (n bits) 95 Figure 1 97 In M4P6E, boundary of locator and identifier is in port number part, 98 that mean, M4P6E use upper part of port number as locator, and lower 99 part of port number as identifier. 101 3. M4P6E address format 103 Figure 2 show a example of M4P6E address format. In this example, 104 16bits IPv4 network plane ID is used, that provide 65535 IPv4 network 105 plane. 107 | 3 | 45bits | 16bits | 16 bits| 32bits | 16 bits | 108 +---+------------------+---------+---------+------------+---------+ 109 |001| routing prefix |subnet id| plane ID|IPv4 address| Port # | 110 +---+------------------+---------+----------------------+---------+ 112 Figure 2 114 4. Using M4P6E in client server environments 116 4.1. Client environments 118 Figure 3 shows a example of M4P6E usage in client environments. In 119 this document, NAPT is IPv4 - IPv4 Netowrk address and port number 120 translator. Coopetation with NAPT, M4P6E provide IPv4 address 121 sharing with different users. 123 +--------------+ 124 | | +---------+ +--------+ +---------+ 125 | +----| M4P6E |--| NAPT |--+--| Clients | 126 | | +---------+ +--------+ | +---------+ 127 | | | +---------+ 128 | | +--| Clients | 129 | Backbone | | +---------+ 130 | | : 131 | | | +---------+ 132 | Network | +--| Clients | 133 | | +---------+ 134 | | 135 | | +---------+ +--------+ +---------+ 136 | +----| M4P6E |--| NAPT |--+--| Clients | 137 | | +---------+ +--------+ | +---------+ 138 | | | +---------+ 139 | | +--| Clients | 140 | | | +---------+ 141 | | : 142 | | | +---------+ 143 | | +--| Clients | 144 | | +---------+ 145 : : : : : 146 | | +---------+ +--------+ +---------+ 147 | +----| M4P6E |--| NAPT |--+--| Clients | 148 | | +---------+ +--------+ | +---------+ 149 | | | +---------+ 150 | | +--| Clients | 151 | | | +---------+ 152 | | : 153 | | | +---------+ 154 | | +--| Clients | 155 | | +---------+ 156 +--------------+ 158 Figure 3 160 4.2. Server environments 162 Figure 4 shows an example of M4P6E usage in server environments. In 163 this example, server terminate M4P6E tunnel. This case, Server 164 require at least one port number per server, that mean, 128bits host 165 route advertise for server access via IPv4. This case, full access 166 is provided via IPv6. 168 +--------------+ 169 | | +------------+ 170 | +----|Server with | 171 | | |M4P6E | 172 | Backbone | |function | 173 | | +------------+ 174 | | +------------+ 175 | Network +----|Server with | 176 | | |M4P6E | 177 | | |function | 178 | | +------------+ 179 : : : 180 | | +------------+ 181 | +----|Server with | 182 | | |M4P6E | 183 | | |function | 184 | | +------------+ 185 +--------------+ 187 Figure 4 189 4.3. Data Center Environments 191 Figure 5 shows an example of M4P6E usage in Data Center environments. 192 In this example, M4P6E is used only in Data Center Backend Network 193 closely. Client which is connected via backbone network does not 194 know the exists of M4P6E. M4P6E can provide at least one port number 195 per server, this case, 128bits host route is advertised, however this 196 route in advertised only in data center backbone network. Ofcource, 197 IPv6 address may allocated to the server, so full access is provided 198 via IPv6. 200 . 201 +--------+ . +-------+ 202 | | +-------+ . | | +-----------------+ 203 | +--+ | . | |-| Server w/M4P6E | 204 | | | Data | . | Data | +-----------------+ 205 |Backbone+--+Center | +----------+ |Center | +-----------------+ 206 | | | +--| M4P6E |--+ |-| Server w/M4P6E | 207 | | |Front | +----------+ |Backend| +-----------------+ 208 |Network | |Network| . |Network| +-----------------+ 209 | | | | +----------+ | |-| Server w/M4P6E | 210 | | | +--| M4P6E |--+ | +-----------------+ 211 | | | | +----------+ | | +-----------------+ 212 : : : : . | |-| Server w/M4P6E | 213 | | | | . | | +-----------------+ 214 | | | | . | | : 215 | | | | . | | +-----------------+ 216 | | | | . | |-| Server w/M4P6E | 217 | | +-------+ . | | +-----------------+ 218 +--------+ . +-------+ 219 . 220 -Normal IPv4 communication->.<----- M4P6E -----> 221 . communication 222 . 223 ------- Normal IPv6 communication -----------------> 224 . 226 Figure 5 228 5. Port Number Issue 230 M4P6E require port number of transport layer. M4P6E can not support 231 ICMPv4 [RFC0792]. The function provided by ICMPv4 does not work in 232 M4P6E environments, such as Path MTU Discovery [RFC1191], ping 233 command, etc. 235 M4P6E can not also support IPv4 IPsec ESP [RFC4303] because transport 236 header is encrypted. 238 6. IANA Considerations 240 This document makes no request of IANA. 242 Note to RFC Editor: this section may be removed on publication as an 243 RFC. 245 7. Security Considerations 247 M4P6E use automatic tunneling technologies. Security consideration 248 related tunneling technologies are discussed in RFC2893 [RFC2893], 249 RFC2267 [RFC2267], etc. 251 8. References 253 8.1. Normative References 255 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 256 Requirement Levels", BCP 14, RFC 2119, 257 DOI 10.17487/RFC2119, March 1997, 258 . 260 8.2. References 262 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 263 RFC 792, DOI 10.17487/RFC0792, September 1981, 264 . 266 [RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, 267 DOI 10.17487/RFC1191, November 1990, 268 . 270 [RFC1631] Egevang, K. and P. Francis, "The IP Network Address 271 Translator (NAT)", RFC 1631, DOI 10.17487/RFC1631, May 272 1994, . 274 [RFC2267] Ferguson, P. and D. Senie, "Network Ingress Filtering: 275 Defeating Denial of Service Attacks which employ IP Source 276 Address Spoofing", RFC 2267, DOI 10.17487/RFC2267, January 277 1998, . 279 [RFC2893] Gilligan, R. and E. Nordmark, "Transition Mechanisms for 280 IPv6 Hosts and Routers", RFC 2893, DOI 10.17487/RFC2893, 281 August 2000, . 283 [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", 284 RFC 4303, DOI 10.17487/RFC4303, December 2005, 285 . 287 Author's Address 288 Naoki Matsuhira 289 Fujitsu Limited 290 17-25, Shinkamata 1-chome, Ota-ku 291 Tokyo 144-8588 292 Japan 294 Phone: +81-3-3735-1111 295 Email: matsuhira@fujitsu.com