idnits 2.17.1 draft-matsuhira-m46t-07.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 : ---------------------------------------------------------------------------- == There are 14 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. 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 2, 2019) is 1579 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 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 2, 2019 5 Expires: June 4, 2020 7 Multiple IPv4 - IPv6 address mapping translator (M46T) 8 draft-matsuhira-m46t-07 10 Abstract 12 This document specifies Multiple IPv4 - IPv6 address mapping 13 Translator (M46T) specification. M46T enable access to IPv4 only 14 host from IPv6 host. IPv4 host is identified as M46 address in IPv6 15 address space. The address assigned to IPv4 host may be global IPv4 16 address or private IPv4 address. M46T does not support access to 17 IPv6 host from IPv4 only host. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on June 4, 2020. 42 Copyright Notice 44 Copyright (c) 2019 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 2. M46T Architecture . . . . . . . . . . . . . . . . . . . . . . . 3 61 2.1. M46 address . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.2. Mapping IPv4 address and IPv6 address . . . . . . . . . . . 3 63 2.3. Address Translation Table . . . . . . . . . . . . . . . . . 3 64 2.4. DNS mapping of IPv4 only host . . . . . . . . . . . . . . . 4 65 3. Sample Configuration . . . . . . . . . . . . . . . . . . . . . 4 66 3.1. M46 address and IPv4 network plane ID . . . . . . . . . . . 4 67 3.2. Network Configuration . . . . . . . . . . . . . . . . . . . 4 68 3.3. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 4. Processing of M46T . . . . . . . . . . . . . . . . . . . . . . 6 70 4.1. Configuration of M46T . . . . . . . . . . . . . . . . . . . 6 71 4.2. Processing from IPv6 to IPv4 . . . . . . . . . . . . . . . 6 72 4.3. Processing from IPv6 to IPv4 . . . . . . . . . . . . . . . 7 73 4.4. Other processing . . . . . . . . . . . . . . . . . . . . . 7 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 77 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 78 7.2. Informative References . . . . . . . . . . . . . . . . . . 8 79 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 81 1. Introduction 83 This document specifies Multiple IPv4 - IPv6 address mapping 84 Translator (M46T) specification. M46T enable access to IPv4 only 85 host from IPv6 host. IPv4 host is identified as M46 address in IPv6 86 address space. The address assigned to IPv4 host may be global IPv4 87 address or private IPv4 address. M46T does not support access to 88 IPv6 host from IPv4 only host. 90 2. M46T Architecture 92 2.1. M46 address 94 Figure 1 show M46A [I-D.draft-matsuhira-m46a]. 96 | 96 - m bits | m bits | 32 bits | 97 +-----------------------+--------------------------+--------------+ 98 | M46A prefix | IPv4 network plane ID | IPv4 address | 99 +-----------------------+--------------------------+--------------+ 101 Figure 1 103 2.2. Mapping IPv4 address and IPv6 address 105 M46A contain IPv4 address. Mapping IPv4 host address to IPv6 address 106 space is already done with M46A. Address translation for IPv4 address 107 is same as resolving M46A. 109 IPv6 host address and corresponding IPv4 address should manage. 111 2.3. Address Translation Table 113 Figure 2 shows translation table for M46T. Translation table contain 114 three value, IPv6 adddress ot IPv6 host, mapped IPv4 address for the 115 IPv6 host, and extry expire timer for remove the entry. 117 +----------------------+----------------------+--------------------+ 118 | Address of IPv6 host | mapped IPv4 address | entry expire timer | 119 | | for IPv6 host | | 120 +----------------------+----------------------+--------------------+ 121 | : | : | : | 122 ~ : ~ : ~ : ~ 123 | : | : | : | 124 +----------------------+----------------------+--------------------+ 125 | Address of IPv6 host | mapped IPv4 address | entry expire timer | 126 | | for IPv6 host | | 127 +----------------------+----------------------+--------------------+ 129 Figure 2 131 2.4. DNS mapping of IPv4 only host 133 In the Domain Name System, hostnames are mapped to IPv6 addresses by 134 AAAA resource records. M46 address can be mapped to IPv4 only host 135 name. 137 3. Sample Configuration 139 3.1. M46 address and IPv4 network plane ID 141 In this example, M46A prefix length is 64bits, and IPv4 network plane 142 ID length is 32 bits. M46A prefix value is 2001:0DB8:0:46, and IPv4 143 network plane ID value is 0:46. Figure 3 shows these value. 145 | 64 bits | 32 bits | 32 bits | 146 +-----------------------+--------------------------+--------------+ 147 | M46A prefix | IPv4 network plane ID | IPv4 address | 148 | (2001:0DB8:0:46) | (0:46) | | 149 +-----------------------+--------------------------+--------------+ 151 Figure 3 153 3.2. Network Configuration 155 Figure 4 shows sample network configuration. IPv6 network have 2001: 156 0DB8:1:0/64 network prefix and IPv4 network have 10.0.0.0/24 network 157 prefix. 159 +----------------+ 160 | IPv6 host | 161 | 2001:0DB8:1.0::10 162 +----------------+ 163 | 164 | 2001:0DB8:1:0/64 165 | 166 +----------------+ 167 | 2001:0DB8:1:0::1 168 | | 169 | M46T | 170 | address pool for IPv6 host mapping 171 | 192.168.0.0/24 172 | | 173 | 10.0.0.1 174 +----------------+ 175 | 176 | 10.0.0.0/24 177 | 178 +----------------+ 179 | IPv4 only host | 180 | | 181 | ipv4onlyhost10.example.com 182 | 10.0.0.10 | 183 | (2001:0DB8:0:46:0:64:10.0.0.10) 184 | | 185 +----------------+ 187 Figure 4 189 IPv6 host address is 2001:0DB8:1:0::10. IPv4 only host address is 190 10.0.0.10. M46 address for IPv4 only host is 2001:0DB8:0:46:0:64: 191 10.0.0.10. FQDN of IPv4 only host is ipv6onlyhost10.example.com. 192 Figure 5 shows DNS entry in IPv4 address space, and Figure 6 shows 193 DNS entry in IPv6 space. 195 ipv6onlyhost10.example.com IN A 10.0.0.10 197 Figure 5 199 ipv6onlyhost10.example.com IN AAAA 2001:0DB8:0:46:0:64:10.0.0.10 200 Figure 6 202 The address of IPv4 interface of M46T is 10.0.0.1, and the address of 203 IPv6 interface of M46T is 2001:0DB8:1:0::1. M46T have also IPv4 204 address pool for IPv6 host mapping. This example, the IPv4 address 205 pool is 192.168.0.0/24. 207 The default router for IPv4 only host is M46T's IPv4 interface 208 address, 10.0.0.1. 210 3.3. Routing 212 If using M46T in own routing domain, M46T advertise M46 address 213 prefix for IPv4 only host, 2001:0DB8:0:46:0:64:10.0.0.0/120. 215 4. Processing of M46T 217 4.1. Configuration of M46T 219 1. M46A prefix for route advertisement (2001:0DB8:0:46:0:64: 220 10.0.0.0/120) 222 2. IPv4 address pool for IPv6 hosts 224 3. entry expire default time (TBD) 226 M46A contain IPv4 network plane ID, so M46T know IPv4 network plane 227 ID from M46A prefix. 229 4.2. Processing from IPv6 to IPv4 231 1. M46T examine the exists of the entry for IPv6 host, that is 232 source IPv6 address of IPv6 packet. 234 2. If there is no entry, get IPv4 address for mapping of IPv6 host 235 from IPv4 address pool, and make entry to the translation table. 237 3. IF there is the entry, resove mapped IPv4 address for IPv6 host. 239 4. Make IPv4 header, source address is mapped IPv4 address, and 240 destination address is from M46 address. 242 5. Translate IPv6 packet to IPv4 packet, and send it, and reset 243 entry expire timer. 245 The example addess translation table is shown in Figure 7. In this 246 example, IPv6 host address is mapped to 192.168.0.200. 248 +----------------------+----------------------+--------------------+ 249 | Address of IPv6 host | mapped IPv4 address | entry expire timer | 250 | | for IPv6 host | | 251 +----------------------+----------------------+--------------------+ 252 | 2001:0DB8:1.0::10 | 192.168.0.200 | TBD | 253 +----------------------+----------------------+--------------------+ 255 Figure 7 257 4.3. Processing from IPv6 to IPv4 259 1. Search address translation table with key destination IPv4 260 address, and resolve corrensponding IPv6 address. 262 2. Resolve source IPv6 address from sourve IPv4 address with M46 263 address generation rule. 265 3. Translate IPv4 packet to IPv6 packet, and sent it, and reset 266 extry expire timer. 268 4.4. Other processing 270 1. Remove the entry of address translation table if expire. 272 5. IANA Considerations 274 This document may requests IANA to assign IPv6 prefix for M46 Global 275 address. 277 6. Security Considerations 279 Security consideration does not discussed in this memo, at this time. 281 7. References 283 7.1. Normative References 285 [I-D.draft-matsuhira-m46a] 286 Matsuhira, N., "Multiple IPv4 - IPv6 mapped IPv6 address", 287 June 2019. 289 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 290 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 291 RFC2119, March 1997, 292 . 294 7.2. Informative References 296 Author's Address 298 Naoki Matsuhira 299 Fujitsu Limited 300 17-25, Shinkamata 1-chome, Ota-ku 301 Tokyo, 144-8588 302 Japan 304 Phone: +81-3-3735-1111 305 Fax: 306 Email: matsuhira@jp.fujitsu.com