idnits 2.17.1 draft-matsuhira-sa46t-gaddr-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 date (July 23, 2015) is 3198 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 2267 (Obsoleted by RFC 2827) -- Obsolete informational reference (is this intentional?): RFC 2893 (Obsoleted by RFC 4213) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). 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: Experimental July 23, 2015 5 Expires: January 24, 2016 7 Stateless Automatic IPv4 over IPv6 Encapsulation / Decapsulation 8 Technology: Global SA46T Address Format 9 draft-matsuhira-sa46t-gaddr-11 11 Abstract 13 This document proposes Stateless Automatic IPv4 over IPv6 14 Encapsulation / Decapsulation Technology (SA46T) Global Address 15 Format. 17 SA46T can apply to organization's network individually, but if 18 coordination between the organizations made, the total number of 19 times of encapsulations and decapusulations can be reduced. That 20 coordination is achieved by using same SA46T address format, that is 21 Global address. This document proposes SA46T Global address format. 23 SA46T is a gateway technology, not protocol. But SA46T Global 24 Address needs IANA assignment, so this document should be categorized 25 standard track or experimental. 27 Requirements Language 29 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 30 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 31 document are to be interpreted as described in RFC 2119 [RFC2119]. 33 Status of this Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at http://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on January 24, 2016. 50 Copyright Notice 52 Copyright (c) 2015 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. SA46T Global Address . . . . . . . . . . . . . . . . . . . . . 5 69 2.1. Option 1: Allocate new SA46T address prefix . . . . . . . 5 70 2.2. Option 2: Adjustment with IPv6 address with Embedded 71 IPv4 addresses . . . . . . . . . . . . . . . . . . . . . . 6 72 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 74 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 75 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 76 6.1. Normative References . . . . . . . . . . . . . . . . . . . 9 77 6.2. Informative References . . . . . . . . . . . . . . . . . . 10 78 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 80 1. Introduction 82 This document proposes Stateless Automatic IPv4 over IPv6 83 Encapsulation / Decapsulation Technology (SA46T) Global Address 84 Format. 86 SA46T [I-D.draft-matsuhira-sa46t-spec]can apply to organization's 87 network individually. Figure 1 shows such example. Organization A 88 applies SA46T and makes backbone network to IPv6 only, and this 89 operation has no effect to Organization B and others. 91 <------- Organization A -------> : <------- Organization B -------> 92 : 93 +-------+ : +-------+ 94 |Router +----:----+Router | 95 |(Dual) | : |(Dual) | 96 +---+---+ : +---+---+ 97 | : | 98 +-------+ : | 99 | SA46T | : | 100 +---+---+ : | 101 | : | 102 /-----------------------+-----\ : /-----+-----------------------\ 103 | | : | | 104 | Backbone Network | : | Backbone Network | 105 | (IPv6 only) | : | (Dual Stack) | 106 | | : | | 107 \-----+----------------+------/ : \-----+----------------+------/ 108 | | : | | 109 +-------+ +-------+ : | | 110 | SA46T | | SA46T | : | | 111 +-------+ +-------+ : | | 112 | | : | | 113 /-----+------\ /-----+------\ : /-----+------\ /-----+------\ 114 | | | | : | | | | 115 |Stub Network| |Stub Network| : |Stub Network| |Stub Network| 116 |(IPv4 only) | |(Dual Stack)| : |(IPv4 only) | |(Dual Stack)| 117 | | | | : | | | | 118 \------------/ \------------/ : \------------/ \------------/ 119 : 121 Figure 1 123 If organization B applies SA46T, network is just like Figure 2. In 124 this network configuration, communication between IPv4 host in 125 organization A and IPv4 host in organization B, IPv4 packet is 126 encapsulated to IPv6 Packet, and decapsulated to IPv4, and 127 encapsulated to IPv6, and decapsulated to IPv4. There are two times 128 encapsulations, and two times decapusulations. If number of 129 organization which applies SA46T increase, number of encapsulations 130 and decapusulation will increase. 132 <------- Organization A -------> : <------- Organization B -------> 133 : 134 +-------+ : +-------+ 135 |Router +----:----+Router | 136 |(Dual) | : |(Dual) | 137 +-------+ : +-------+ 138 | : | 139 +-------+ : +-------+ 140 | SA46T | : | SA46T | 141 +-------+ : +-------+ 142 | : | 143 /-----------------------+-----\ : /-----+-----------------------\ 144 | | : | | 145 | Backbone Network | : | Backbone Network | 146 | (IPv6 only) | : | (IPv6 only) | 147 | | : | | 148 \-----+----------------+------/ : \-----+----------------+------/ 149 | | : | | 150 +---+---+ +---+---+ : +---+---+ +---+---+ 151 | SA46T | | SA46T | : | SA46T | | SA46T | 152 +---+---+ +---+---+ : +---+---+ +---+---+ 153 | | : | | 154 /-----+------\ /-----+------\ : /-----+------\ /-----+------\ 155 | | | | : | | | | 156 |Stub Network| |Stub Network| : |Stub Network| |Stub Network| 157 | (IPv4 only)| |(Dual Stack)| : |(IPv4 only) | |(Dual Stack)| 158 | | | | : | | | | 159 \------------/ \------------/ : \------------/ \------------/ 160 : 162 Figure 2 164 But if coordination between the organizations are made, the total 165 number of times of encapsulations and decapusulations can be reduced. 166 Figure 3 shows such example. That coordination is achieved by using 167 same SA46T address format. This is the reason for the proposal of 168 SA46T Global address. When most of IPv4 node moves to IPv6 and few 169 IPv6 node exists, such coodination in the Internet scale is useful 170 and efficient to co-existing IPv6 and IPv4. 172 <------- Organization A -------> : <------- Organization B -------> 173 : 174 +-------+ : +-------+ 175 |Router +----:----+Router | 176 |(IPv6) | : |(IPv6) | 177 +---+---+ : +---+---+ 178 | : | 179 /-----------------------+-----\ : /-----+-----------------------\ 180 | | : | | 181 | Backbone Network | : | Backbone Network | 182 | (IPv6 only) | : | (IPv6 only) | 183 | | : | | 184 \-----+----------------+------/ : \-----+----------------+------/ 185 | | : | | 186 +---+---+ +---+---+ : +---+---+ +---+---+ 187 | SA46T | | SA46T | : | SA46T | | SA46T | 188 +---+---+ +---+---+ : +---+---+ +---+---+ 189 | | : | | 190 /-----+------\ /-----+------\ : /-----+------\ /-----+------\ 191 | | | | : | | | | 192 |Stub Network| |Stub Network| : |Stub Network| |Stub Network| 193 |(IPv4 only) | |(Dual Stack)| : |(IPv4 only) | |(Dual Stack)| 194 | | | | : | | | | 195 \------------/ \------------/ : \------------/ \------------/ 196 : 198 Figure 3 200 2. SA46T Global Address 202 Figure 4 shows SA46T address 203 architecture[I-D.draft-matsuhira-sa46t-spec]. 205 | 96 - m bits | m bits | 32 bits | 206 +-----------------------+--------------------------+--------------+ 207 | SA46T address prefix | IPv4 network plane ID | IPv4 address | 208 +-----------------------+--------------------------+--------------+ 210 Figure 4 212 2.1. Option 1: Allocate new SA46T address prefix 214 This option requests special IPv6 address prefix for SA46T. Figure 5 215 shows SA46T Global Address Format. 217 | 96 - m bits | m | 32 bits | 218 +--------------------------------------+------+------------------+ 219 | SA46T address prefix |PID* | IPv4 address | 220 +--------------------------------------+------+------------------+ 221 PID: IPv4 network plane ID 223 Figure 5 225 Table 1 shows SA46T IPv4 network plane ID length (m) and SA46T prefix 226 length and number of plane. 228 +----+---------------+-----------------+ 229 | m | prefix length | number of plane | 230 +----+---------------+-----------------+ 231 | 16 | 80 | 65536 | 232 | 32 | 64 | 4294967296 | 233 +----+---------------+-----------------+ 235 Table 1 237 Table 2 is an example of SA46T IPv4 network plane ID management 238 table. Value 0 should be assigned to IPv4 Global Internet, and the 239 other are reserved for IPv4 private networks. 241 +----------------+--------------------------------------------+ 242 | plane ID value | assign to | 243 +----------------+--------------------------------------------+ 244 | 0 | Global IPv4 Internet (IPv4 Global address) | 245 | 1 | Reserved | 246 | 2 | Reserved | 247 | .... | .... | 248 +----------------+--------------------------------------------+ 250 Table 2 252 These value except zero are reserved for stacking IPv4 private 253 network over IPv6 Internet with SA46T. In future, if there are much 254 demand for stacking IPv4 private network, These usage of reserved ID 255 value may be defined. At that time, central coordination or 256 assignment should be discussed too. 258 2.2. Option 2: Adjustment with IPv6 address with Embedded IPv4 259 addresses 261 RFC4291 [RFC4291] define IPv6 addresses with Embedded IPv4 addresses. 262 SA46T address is such addresses. Therefore merging SA46T global 263 address into IPv6 addresses with Embedded IPv4 addresses may be 264 possible. 266 Figure 6 shows IPv4 Compatible IPv6 address, and Figure 7 shows IPv4- 267 Mapped IPv6 address. 269 | 80 bits | 16 | 32 bits | 270 +--------------------------------------+--------------------------+ 271 |0000..............................0000|0000| IPv4 address | 272 +--------------------------------------+----+---------------------+ 274 Figure 6 276 | 80 bits | 16 | 32 bits | 277 +--------------------------------------+--------------------------+ 278 |0000..............................0000|FFFF| IPv4 address | 279 +--------------------------------------+----+---------------------+ 281 Figure 7 283 It seem that 80bits prefix (all zero) shows IPv6 addresses with 284 Embedded IPv6 addresses, and continued 16bits shows more detail, 285 0x0000 means IPv4-Compatible addresses and 0xFFFF means IPv4-Mapped 286 addresses. 288 Adjustment with such format, IPv6 addresses with Embedded IPv4 289 addresses may redefine such format. Figure 8 shows such format. 291 | 80 bits | 16 | 32 bits | 292 +--------------------------------------+--------------------------+ 293 |0000..............................0000| EID| IPv4 address | 294 +--------------------------------------+----+---------------------+ 296 Figure 8 298 Where 300 IPv4 Embedded address prefix 302 IPv4 Embedded prefix. 80 bits long, value is zero. 304 EID 306 Embedded ID. Indicates Type of IPv6 addresses with Embedded IPv4 307 address. This value MUST be globally unique. See below for more 308 detail. 310 IPv4 address 312 IPv4 address 314 Table 3 shows EID value of proposed IPv6 addresses with Embedded IPv4 315 addresses and the detail usage. EID = 0x0000 shows this IPv6 316 addresses with Embedded IPv4 address is the IPv4-Compatible IPv6 317 address, and EID=0xFFFF shows this IPv6 addresses with Embedded IPv4 318 address is the IPv4-Mapped address. 320 In this proposal, EID value except 0x0000 and 0xFFFF is for SA46T 321 usage, and EID=0x0001 shows this IPv6 addresses is used for SA46T for 322 IPv4 Internet, that mean, IPv4 address is limited for global and 323 inhibit for private address. 325 In this proposal, EID value except 0x0000, 0x0001 and 0xFFFF are 326 reserved for SA46T. These value are reserved for stacking IPv4 327 private network over IPv6 Internet with SA46T. In future, if there is 328 much demand for stacking IPv4 private network, these usage of 329 reserved EID value may be defined. At that time, central 330 coordination or assignment should be discussed too. 332 +--------+---------------------------------------------------------+ 333 | EID | detail | 334 +--------+---------------------------------------------------------+ 335 | 0x0000 | IPv4 Compatible IPv6 address | 336 | 0x0001 | SA46T address for IPv4 Internet (IPv4 Global Addresses) | 337 | 0x0002 | Reserved for SA46T | 338 | .... | .... | 339 | 0xFFFE | Reserved for SA46T | 340 | 0xFFFF | IPv4-Mapped IPv6 address | 341 +--------+---------------------------------------------------------+ 343 Table 3 345 3. IANA Considerations 347 This document may requests IANA to assign IPv6 prefix for SA46T 348 Global address. 350 This document proposes two option. One is New IPv6 address prefix 351 for SA46T. Another is adjustment with IPv6 address with Embedded IPv4 352 addresses. 354 The Well-known preifx 0000::/8 is reserved by IETF [RFC4291]. If new 355 IPv6 address prefix for SA46T is allocated from 0000::/8 space by 356 IETF, this document request no actions for IANA. And also, if 357 adjustment with IPv6 adddress with Embedded IPv4 addresses is 358 approved by IETF, this document request no actions for IANA. 360 Note to RFC Editor: this section may be removed on publication as an 361 RFC. 363 4. Security Considerations 365 SA46T uses automatic Encapsulation / Decapsulation technologies. 366 Security consideration related tunneling technologies are discussed 367 in RFC2893 [RFC2893], RFC2267 [RFC2267], etc. 369 5. Acknowledgements 371 This document is based on Naoki Matsuhira's original ideas and an 372 individual effort of the author. 374 Review and encouragement have been provided by many others. 375 Particulary Akira Kato at WIDE Project / Keio University and Masanobu 376 Katoh at Fujitsu. 378 Originally, SA46T is an abbreviation for "Stateless Automatic IPv4 379 over IPv6 Tunneling". Now, SA46T is an abbreviation for "Stateless 380 Automatic IPv4 over IPv6 Encapsulation / Decapsulation Technology". 381 This change was made in response to the indication from the softwire 382 WG chair at 4th softwire interim meeting in September 2011. 384 6. References 386 6.1. Normative References 388 [I-D.draft-matsuhira-sa46t-spec] 389 Matsuhira, N., "Stateless Automatic IPv4 over IPv6 390 Encapsulation / Decapsulation Technology: Specification", 391 January 2014. 393 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 394 Requirement Levels", BCP 14, RFC 2119, March 1997. 396 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 397 Architecture", RFC 4291, February 2006. 399 6.2. Informative References 401 [RFC2267] Ferguson, P. and D. Senie, "Network Ingress Filtering: 402 Defeating Denial of Service Attacks which employ IP Source 403 Address Spoofing", RFC 2267, January 1998. 405 [RFC2893] Gilligan, R. and E. Nordmark, "Transition Mechanisms for 406 IPv6 Hosts and Routers", RFC 2893, August 2000. 408 Author's Address 410 Naoki Matsuhira 411 Fujitsu Limited 412 1-1, Kamikodanaka 4-chome, Nakahara-ku 413 Kawasaki, 211-8588 414 Japan 416 Phone: +81-44-754-3466 417 Email: matsuhira@jp.fujitsu.com