idnits 2.17.1 draft-matsuhira-sa46t-pt-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 6 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 3198 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 Translator (SA46T-PT) 8 draft-matsuhira-sa46t-pt-spec-05 10 Abstract 12 This document specifies SA46T Prefix Translator (SA46T-PT) 13 specification. SA46T-PT expand IPv4 network plane by connecting 14 SA46T domain and SA46T-PR domain. SA46T-PT translate prefix part of 15 SA46T address and SA46T-PR address both are IPv6 address. SA46T-PT 16 does not translate IPv4 packet which is encapsulated, so transparency 17 of IPv4 packet is not broken. 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 January 24, 2016. 42 Copyright Notice 44 Copyright (c) 2015 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. Basic Network Configuration . . . . . . . . . . . . . . . . . 3 61 3. Basic function of SA46T-PT . . . . . . . . . . . . . . . . . . 4 62 3.1. Translation processing . . . . . . . . . . . . . . . . . . 5 63 3.2. Address format of SA46T and SA46T-PR . . . . . . . . . . . 5 64 3.3. Resolving translate prefix . . . . . . . . . . . . . . . . 6 65 3.4. Destination address resolution . . . . . . . . . . . . . . 6 66 3.5. Source address resolution . . . . . . . . . . . . . . . . 7 67 4. Sample Configuration . . . . . . . . . . . . . . . . . . . . . 7 68 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 69 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 70 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 8.1. Normative References . . . . . . . . . . . . . . . . . . . 10 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 10 74 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 10 76 1. Introduction 78 This document provide SA46T Prefix Translator (SA46T-PT) 79 specification. 81 The basic strategy for IPv6 deployment is dual stack. However, 82 because of exhaustion of IPv4 address, there will be no IPv4 83 addresses for configuring dual stack in near future. That means 84 there will be IPv6 only networks automatically. 86 However, there are many IPv4 only networks still exist and those 87 seems continuous use in near future. That means methods continuous 88 use of IPv4 network over IPv6 only network will be required. 90 SA46T [I-D.draft-matsuhira-sa46t-spec] provide such methods. In 91 addition, SA46T-PR [I-D.draft-matsuhira-sa46t-pr-spec] also provide 92 such methots. SA46T is backbone network based approach, on the other 93 hand, SA46T-PR is stub network based approach. 95 SA46T-PT expand IPv4 network plane by connecting SA46T domain and 96 SA46T-PR domain. SA46T-PT translate prefix part of SA46T address and 97 SA46T-PR address both are IPv6 address. SA46T-PT does not translate 98 IPv4 packet which is encapsulated, so transparency of IPv4 packet is 99 not broken. 101 2. Basic Network Configuration 103 Figure 1 shows network configuration with SA46T-PT. At large view, 104 the network consists three parts, SA46T domain, SA46T-PR domain, and 105 SA46T-PT. SA46T-PT connect SA46T domain and SA46T-PR domain. 107 <------ SA46T Domain ------------> <--------- SA46T-PR Domain ----> 109 /-------------------------------/ /-----------------------------\ 110 | | | | 111 | Backbone Network +----------+ Backbone Network | 112 | | SA46T-PT | | 113 | +----------+ | 114 | +----------+ +----------+ | | | 115 \---| SA46T |--| SA46T |--/ /-----------------------------/ 116 +----------+ +----------+ | | 117 | | | | 118 | | | | 119 | | +----------+ +----------+ 120 /--------------\/--------------/ /-| SA46T-PR |-\/-| SA46T-PR |-\ 121 | || | | +----------+ || +----------+ | 122 | || | | || | 123 | Stub Network || Stub Network | | Stub Network || Stub Network | 124 | || | | (IPv4 only) || (Dual Stack) | 125 | || | | || | 126 \--------------//--------------/ \--------------/\--------------/ 128 Figure 1 130 SA46T domain consists three parts, backbone network, stub network and 131 SA46T. Backbone network can be operated with IPv6 only. Stub network 132 has three cases, IPv4 only, Dual Stack (both IPv4 and IPv6), and IPv6 133 only.SA46T connects backbone network and stub network in case IPv4 134 still works in that stub network. If stub network is IPv6 only, 135 SA46T is not needed. SA46T is a backbone network based approach, 136 that mean SA46T advertise special route for SA46T. 138 And also, SA46T-PR domain consists three parts, backbone network, 139 stub network and SA46T. Backbone network can be operated with IPv6 140 only. Stub network has three cases, IPv4 only, Dual Stack (both IPv4 141 and IPv6), and IPv6 only.SA46T connects backbone network and stub 142 network in case IPv4 still works in that stub network. If stub 143 network is IPv6 only, SA46T-PR is not needed. SA46T-PR is a stub 144 network based approach. 146 3. Basic function of SA46T-PT 148 This section describe basic function of SA46T-PT. 150 3.1. Translation processing 152 SA46T-PT translate between SA46T packet and SA46T-PT packet. SA46T 153 packet and SA46T-PT packet are almost the same, however IPv6 address 154 are different. 156 Fig shows packet format of SA46T domain and SA46T-PT domain. 158 +--------+--------+------------+ +--------+--------+------------+ 159 |IPv6 Hdr|IPv4 Hdr| Data | --> |IPv6 Hdr|IPv4 Hdr| Data | 160 +--------+--------+------------+ +--------+--------+------------+ 162 +--------+--------+------------+ +--------+--------+------------+ 163 |IPv6 Hdr|IPv4 Hdr| Data | <-- |IPv6 Hdr|IPv4 Hdr| Data | 164 +--------+--------+------------+ +--------+--------+------------+ 166 /-------------------\ +----------+ /---------------------------\ 167 | SA46T Domain |--| SA46T-PT |--| SA46T-PR Domain | 168 | | +----------+ | | 169 \-------------------/ \---------------------------/ 171 Figure 2 173 3.2. Address format of SA46T and SA46T-PR 175 figure Figure 3 shows SA46T address format and Figure 4 shows 176 SA46T-PR address format. These format almost the same except SA46T 177 address prefix in SA46T address and SA46T-PR address prefix in 178 SA46T-PR address. 180 | 96 - m bits | m bits | 32 bits | 181 +--------------------------+------------------------+--------------+ 182 | SA46T address prefix | IPv4 network plane ID | IPv4 address | 183 +--------------------------+------------------------+--------------+ 185 Figure 3 187 | 96 - m bits | m bits | 32 bits | 188 +--------------------------+------------------------+--------------+ 189 | SA46T-PR address prefix | IPv4 network plane ID | IPv4 address | 190 +--------------------------+------------------------+--------------+ 192 Figure 4 194 3.3. Resolving translate prefix 196 SA46T-PT translate from SA46T prefix to SA46T-PR prefix, or from 197 SA46T-PR prefix to SA46T prefix using SA46T Prefix Translation 198 (SA46T-PT) table. fig Figure 5shows address resolution manner and fig 199 Figure 6shows SA46T-PT table. 201 | 96 - m bits | m bits | 32 bits | 202 +--------------------------+------------------------+--------------+ 203 | SA46T / SA46T-PR prefix | IPv4 network plane ID | IPv4 address | 204 +--------------------------+------------------------+--------------+ 206 \--------------------------/\--------------------------------------/ 207 ^ | 208 | | 209 | v 210 +------------------------------------------------------------------+ 211 | | 212 | SA46T Prefix Translation Table (SA46T-PT Table) | 213 | | 214 +------------------------------------------------------------------+ 216 Figure 5 218 SA46T-AT table is similar with SA46T-PR table, however SA46T-AT table 219 may contain SA46T 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 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 227 +---------------------+------------+-------++-----------------------+ 228 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 229 +---------------------+------------+-------++-----------------------+ 230 : : : 231 +---------------------+------------+-------++-----------------------+ 232 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 233 +---------------------+------------+-------++-----------------------+ 235 Figure 6 237 3.4. Destination address resolution 239 For address resolution for destination address, SA46T-PT use SA46T-PT 240 table. 242 3.5. Source address resolution 244 For address resolution for source address, SA46T-PT use interface 245 information, not SA46T-PT table. From SA46T domain to SA46T-PR 246 domain, SA46T-PT use IPv6 address prefix of the interface which 247 belong SA46T-PR domain. From 249 4. Sample Configuration 251 Figure Figure 7shows sample confiuration of SA46T-PT. In this 252 example, there are four IPv4 stub network with the same IPv4 network 253 plane, and two of four are in SA46T domain and other two of four are 254 in SA46T-PR domain. 256 In this example, SA46T prefix is 2001:0db8:0:46::/64. 258 /------------\ 259 | +--------+ /----------------------\ 260 | Backbone | | |Stub Network#1 | 261 | Network |SA46T |--|10.1.1.0/24(plane 1) | 262 |(IPv6 only)| | |2001:0db8:1:1::/64 | 263 | +--------+ \----------------------/ 264 | <--[2001:0db8:1:1::/64] 265 | <--[2001:0db8:0:46:0:1:10.1.1.0/120] 266 | | 267 | +--------+ /----------------------\ 268 | | | |Stub Network#2 | 269 | |SA46T |--|10.1.2.0/24(plane 1) | 270 | | | |2001:0db8:1:2::/64 | 271 | +--------+ \----------------------/ 272 | <--[2001:0db8:1:2::/64] 273 | <--[2001:0db8:0:46:0:1:10.1.2.0/120] 274 | | 275 | <--[2001:0db8:0:46:0:1:10.1.4.0/120] 276 | <--[2001:0db8:0:46:0:1:10.1.5.0/120] 277 | +------------+ 278 | | SA46T-PT | 279 | +------------+ 280 \------------/ | 281 | |Stub Network #0 282 /------------\ | 2001:0db8:2:0::/64 283 | |----+ 284 | | /--------------------------------------/ 285 | | | Stub Network #3 | 286 | | | 2001:0db8:2:1::/64 | 287 | | | +--------+ /----------------------\ | 288 | |--| |SA46T-PR|--|10.1.3.0/24(plane 1) | | 289 | | | +--------+ /----------------------/ | 290 | <--[2001:0db8:2:1::/64] | 291 | | /--------------------------------------/ 292 | | 293 | | /--------------------------------------/ 294 | | | Stub Network #4 | 295 | | | 2001:0db8:2:2::/64 | 296 | Backbone | | +--------+ /----------------------\ | 297 | Network |--| |SA46T-PR|--|10.1.4.0/24(plane 1) | | 298 | | | +--------+ \----------------------/ | 299 | <--[2001:0db8:2:2::/64] | 300 | | /--------------------------------------/ 301 \------------/ 303 Figure 7 305 Figure Figure 8 shows SA46T-PT table for this example. This example 306 is default free case. 308 +---------------------+------------+-------++-----------------------+ 309 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 310 +---------------------+------------+-------++-----------------------+ 311 | 1 | 10.1.1.0 | /120 || 2001:0db8:0:46 | 312 | 1 | 10.1.2.0 | /120 || 2001:0db8:0:46 | 313 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 314 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 315 +---------------------+------------+-------++-----------------------+ 317 Figure 8 319 Fig Figure 9shows another SA46T-PT table for this example. This 320 example use default for SA46T. If there are many stub network in 321 SA46T domain, by using default as SA46T prefix, reduction of SA46T-PT 322 table size can be possible. 324 +---------------------+------------+-------++-----------------------+ 325 |IPv4 network plane ID|IPv4 address|netmask||SA46T-PR address prefix| 326 +---------------------+------------+-------++-----------------------+ 327 | 1 | 10.1.3.0 | /120 || 2001:0db8:2:1 | 328 | 1 | 10.1.4.0 | /120 || 2001:0db8:2:2 | 329 | 1 | 0.0.0.0 | /0 || 2001:0db8:0:46 | 330 +---------------------+------------+-------++-----------------------+ 332 Figure 9 334 5. IANA Considerations 336 This document makes no request of IANA. 338 Note to RFC Editor: this section may be removed on publication as an 339 RFC. 341 6. Security Considerations 343 Security Considerations does not discussed in this memo. 345 7. Acknowledgements 347 8. References 348 8.1. Normative References 350 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 351 Requirement Levels", BCP 14, RFC 2119, March 1997. 353 8.2. Informative References 355 [I-D.draft-matsuhira-sa46t-pr-spec] 356 Matsuhira, N., "SA46T Prefix Resolution (SA46T-PR)", 357 January 2014. 359 [I-D.draft-matsuhira-sa46t-spec] 360 Matsuhira, N., "Stateless Automatic IPv4 over IPv6 361 Encapsulation / Decapsulation Technology: Specification", 362 January 2014. 364 Author's Address 366 Naoki Matsuhira 367 Fujitsu Limited 368 1-1, Kamikodanaka 4-chome, Nakahara-ku 369 Kawasaki, 211-8588 370 Japan 372 Phone: +81-44-754-3466 373 Fax: 374 Email: matsuhira@jp.fujitsu.com