idnits 2.17.1 draft-matsuhira-sa46t-pr-spec-05.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 3 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 (July 23, 2015) is 3194 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) 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: Standards Track July 23, 2015 5 Expires: January 24, 2016 7 SA46T Prefix Resolution (SA46T-PR) 8 draft-matsuhira-sa46t-pr-spec-05 10 Abstract 12 This document specifies SA46T Prefix Resolution (SA46T-PR) 13 specification. SA46T-PR is almost same as SA46T, however method of 14 generation of outer IPv6 address is different. SA46T is backbone 15 network based approach, however SA46T-PR is stub network based 16 approch. 18 Requirements Language 20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 21 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 22 document are to be interpreted as described in RFC 2119 [RFC2119]. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 24, 2016. 41 Copyright Notice 43 Copyright (c) 2015 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Basic Network Configuration . . . . . . . . . . . . . . . . . 3 60 3. Basic Function of SA46T-PR . . . . . . . . . . . . . . . . . . 4 61 3.1. IPv4 over IPv6 Encapsulation / Decapsulation . . . . . . . 4 62 3.2. SA46T-PR Address Format . . . . . . . . . . . . . . . . . 5 63 3.3. Resolving SA46T-PR address . . . . . . . . . . . . . . . . 6 64 4. Mode of SA46T-PR . . . . . . . . . . . . . . . . . . . . . . . 7 65 4.1. Router mode . . . . . . . . . . . . . . . . . . . . . . . 7 66 4.2. Host mode . . . . . . . . . . . . . . . . . . . . . . . . 7 67 5. Sample configuration . . . . . . . . . . . . . . . . . . . . . 7 68 6. Comparison with SA46T . . . . . . . . . . . . . . . . . . . . 9 69 6.1. difference with SA46T . . . . . . . . . . . . . . . . . . 9 70 6.2. Compatibility with SA46T . . . . . . . . . . . . . . . . . 9 71 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 72 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 73 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 74 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 75 10.1. Normative References . . . . . . . . . . . . . . . . . . . 9 76 10.2. Informative References . . . . . . . . . . . . . . . . . . 10 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 79 1. Introduction 81 This document provide SA46T Prefix Resolution (SA46T-PR) 82 specification. 84 The basic strategy for IPv6 deployment is dual stack. However, 85 because of exhaustion of IPv4 address, there will be no IPv4 86 addresses for configuring dual stack in near future. That means 87 there will be IPv6 only networks automatically. 89 However, there are many IPv4 only networks still exist and those 90 seems continuous use in near future. That means methods continuous 91 use of IPv4 network over IPv6 only network will be required. 93 SA46T [I-D.draft-matsuhira-sa46t-spec] provide such methods. In 94 addition, SA46T-PR also provide such methots. SA46T is backbone 95 network based approach, on the other hand, SA46T-PR is stub network 96 based approach. 98 2. Basic Network Configuration 100 Figure 1 shows network configuration with SA46T-PR. The network 101 consists of three parts, backbone network, stub network, and 102 SA46T-PR. 104 Backbone network can be operated with IPv6 only. Stub network has 105 three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6 106 only. 108 SA46T connects backbone network and stub network in case IPv4 still 109 works in that stub network. If stub network is IPv6 only, SA46T-PR 110 is not needed. 112 /---------------------------------------------------\ 113 | | 114 | Backbone Network | 115 | (IPv6 only) | 116 | | 117 \---------------------------------------------------/ 118 | | | 119 | | | 120 | | | 121 +----------+ +----------+ | 122 /-| SA46T-PR |-\ /-| SA46T-PR |-\ /--------------\ 123 | +----------+ | | +----------+ | | | 124 | | | | | | 125 | Stub Network | | Stub Network | | Stub Network | 126 | (IPv4 only) | | (Dual Stack) | | (IPv6 only) | 127 | | | | | | 128 \--------------/ \--------------/ \--------------/ 130 Figure 1 132 3. Basic Function of SA46T-PR 134 SA46T-PR has mainly two function. One is IPv4 over IPv6 135 Encapsulation / Decapsulation, and another is generate a table where 136 IPv4 stub network belong to IPv6 network. 138 3.1. IPv4 over IPv6 Encapsulation / Decapsulation 140 SA46T-PR excapsulates IPv4 packet to IPv6 from stub network to 141 backbone network, and decapsulates IPv6 packet to IPv4 from backbone 142 network to stub network. Figure 2 shows packet format on both 143 backbone network and stub network. 145 +--------+------------+ +----------+--------+------------+ 146 |IPv4 Hdr| Data | --> | IPv6 Hdr |IPv4 Hdr| Data | 147 +--------+------------+ +----------+--------+------------+ 149 +--------+------------+ +----------+--------+------------+ 150 |IPv4 Hdr| Data | <-- | IPv6 Hdr |IPv4 Hdr| Data | 151 +--------+------------+ +----------+--------+------------+ 153 /-------------------\ +----------+ /-----------------------------\ 154 | Stub Network |--| SA46T-PR |--| Backbone Network | 155 | (IPv4) | +----------+ | (IPv6 only) | 156 \-------------------/ \-----------------------------/ 158 Figure 2 160 3.2. SA46T-PR Address Format 162 SA46T-PR address is a IPv6 address used in outer IPv6 header which 163 encapsulate IPv4 packet by SA46T-PR. Figure 3 shows SA46T-PR address 164 format. 166 | 96 - m bits | m bits | 32 bits | 167 +--------------------------+------------------------+--------------+ 168 | SA46T-PR address prefix | IPv4 network plane ID | IPv4 address | 169 +--------------------------+------------------------+--------------+ 171 Figure 3 173 SA46T address consists of three parts as follows. 175 SA46T-PR address prefix 177 SA46T-PR address prefix is the IPv6 network prefix of stub network 178 which contain IPv4 network of the IPv4 network plane. 180 IPv4 network plane ID 182 IPv4 network plane ID is an identifier of IPv4 network stack over 183 IPv6 backbone network. 185 IPv4 address 187 IPv4 address in inner IPv4 packet. 189 3.3. Resolving SA46T-PR address 191 SA46T-PR resolve SA46T-PR address using SA46T Prefix Resolution Table 192 (SA46T-PR Table). SA46T-PR generate SA46T-PR address resolving 193 SA46T-PR prefix from IPv4 network plane ID and IPv4 address. 194 FigureFigure 4 show this processing. 196 | 96 - m bits | m bits | 32 bits | 197 +--------------------------+------------------------+--------------+ 198 | SA46T-PR address prefix | IPv4 network plane ID | IPv4 address | 199 +--------------------------+------------------------+--------------+ 201 \--------------------------/\--------------------------------------/ 202 ^ | 203 | | 204 | v 205 +------------------------------------------------------------------+ 206 | | 207 | SA46T Prefix Resolution Table (SA46T-PR Table) | 208 | | 209 +------------------------------------------------------------------+ 211 Figure 4 213 Figure Figure 5show SA46T-PR Table. This table consists four parts, 214 IPv4 network plane ID, IPv4 address, netmask, and SA46T-PR address 215 prefix. 217 +---------------------+------------+-------++-----------------------+ 218 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 219 +---------------------+------------+-------++-----------------------+ 220 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 221 +---------------------+------------+-------++-----------------------+ 222 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 223 +---------------------+------------+-------++-----------------------+ 224 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 225 +---------------------+------------+-------++-----------------------+ 226 : : : 227 +---------------------+------------+-------++-----------------------+ 228 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 229 +---------------------+------------+-------++-----------------------+ 231 Figure 5 233 SA46T-PR configured IPv4 network plane ID, so SA46T-PR know IPv4 234 network plane ID value the interface belongs. 236 Resolving destination address, SA46T-PR use pre-configured IPv4 237 network plane ID valude, and destination address of IPv4 packets, and 238 serch the SA46T-PR table. SA46T-PR table return the SA46T-PR address 239 prefix value correspoiding IPv4 network plane ID and IPv4 destination 240 address. Then SA46T-PR generate whole SA46T-PR address. 242 Resolving source address, SA46T-PR already know IPv4 network plane ID 243 value and IPv6 address prefix as SA46T-PR prefix. So, searching the 244 SA46T-PR table does not require for resolving source address. 246 4. Mode of SA46T-PR 248 SA46T-PR has two working mode, one is router mode, another is host 249 mode. 251 4.1. Router mode 253 In router mode, SA46T-PR act as a IPv6 router. SA46T-PR occupy IPv6 254 subnet, and SA46T-PR advertise route for SA46T-PR. 256 4.2. Host mode 258 In host mode, SA46T-PR act as a IPv6 host. SA46T-PR share IPv4 259 subnet, that mean, SA46T-PR and IPv6 hosts exists on same IPv6 260 subnet. SA46T-PR do proxy NDP function for IPv4 host. 262 5. Sample configuration 264 Figure Figure 6shows sample confiuration of SA46T-PR. In this 265 example, there are three IPv4 stub network with the same IPv4 network 266 plane. 268 /------------\ /--------------------------------------/ 269 | | | Stub Network #1 | 270 | | | 2001:0db8:0:1::/64 | 271 | | | +--------+ /----------------------\ | 272 | |--| |SA46T-PR|--|10.1.1.0/24(plane 1) | | 273 | | | +--------+ | | | 274 | | | \----------------------/ | 275 | <--[2001:0db8:0:1::/64] | 276 | | /--------------------------------------/ 277 | | 278 | | /--------------------------------------/ 279 | | | Stub Network #2 | 280 | | | 2001:0db8:0:2::/64 | 281 | Backbone | | +--------+ /----------------------\ | 282 | Network |--| |SA46T-PR|--|10.1.2.0/24(plane 1) | | 283 | | | +--------+ | | | 284 | | | \----------------------/ | 285 | <--[2001:0db8:0:2::/64] | 286 | | /--------------------------------------/ 287 | | 288 | | /--------------------------------------/ 289 | | | Stub Network #3 | 290 | | | 2001:0db8:0:3::/64 | 291 | | | +--------+ /----------------------\ | 292 | |--| |SA46T-PR|--|10.1.3.0/24(plane 1) | | 293 | | | +--------+ | | | 294 | | | \----------------------/ | 295 | <--[2001:0db8:0:3::/64] | 296 | | /--------------------------------------/ 297 | | 298 \------------/ 300 Figure 6 302 Figure Figure 7 shows SA46T-PR table for sample network. 304 +---------------------+------------+-------++-----------------------+ 305 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 306 +---------------------+------------+-------++-----------------------+ 307 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:1 | 308 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:2 | 309 | 1 | 10.1.3.0 | /120 || 2001:0db8:0:3 | 310 +---------------------+------------+-------++-----------------------+ 312 Figure 7 314 6. Comparison with SA46T 316 SA46T is backbone network based approach, and SA46T-PR is stub 317 network based approach. 319 6.1. difference with SA46T 321 SA46T require route advertisement of SA46T prefix, so additional 322 route are require, however configuration is few. On the other hand, 323 SA46T-PR does not require additional route, however SA46T-PR table is 324 require. 326 There are such trade-off between SA46T and SA46T-PR. 328 6.2. Compatibility with SA46T 330 If configure SA46t-PR table with default prefix as SA46T prefix, 331 SA46T-PR acts as SA46T. In this case, netmask value of SA46T-PR table 332 is /0, that mean any IPv4 network plane ID and IPv4 address pair 333 match this entry. 335 7. IANA Considerations 337 This document makes no request of IANA. 339 Note to RFC Editor: this section may be removed on publication as an 340 RFC. 342 8. Security Considerations 344 Security Considerations does not discussed in this memo. 346 9. Acknowledgements 348 10. References 350 10.1. Normative References 352 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 353 Requirement Levels", BCP 14, RFC 2119, March 1997. 355 10.2. Informative References 357 [I-D.draft-matsuhira-sa46t-spec] 358 Matsuhira, N., "Stateless Automatic IPv4 over IPv6 359 Encapsulation / Decapsulation Technology: Specification", 360 January 2014. 362 Author's Address 364 Naoki Matsuhira 365 Fujitsu Limited 366 1-1, Kamikodanaka 4-chome, Nakahara-ku 367 Kawasaki, 211-8588 368 Japan 370 Phone: +81-44-754-3466 371 Fax: 372 Email: matsuhira@jp.fujitsu.com