idnits 2.17.1 draft-ietf-softwire-map-radius-08.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 4 instances of too long lines in the document, the longest one being 26 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 27, 2016) is 2736 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) ** Downref: Normative reference to an Informational RFC: RFC 2869 ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Downref: Normative reference to an Informational RFC: RFC 3580 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 7749 (Obsoleted by RFC 7991) Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Softwire S. Jiang, Ed. 3 Internet-Draft Huawei Technologies Co., Ltd 4 Intended status: Standards Track Y. Fu, Ed. 5 Expires: April 30, 2017 CNNIC 6 B. Liu 7 Huawei Technologies Co., Ltd 8 P. Deacon 9 IEA Software, Inc. 10 C. Xie 11 China Telecom 12 T. Li 13 Tsinghua University 14 October 27, 2016 16 RADIUS Attribute for Softwire Address plus Port based Mechanisms 17 draft-ietf-softwire-map-radius-08 19 Abstract 21 IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6 22 connectivity services simultaneously during the IPv4/IPv6 co-existing 23 period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) 24 options have been defined to configure Customer Edge (CE) in MAP-E, 25 MAP-T, and Lightweight 4over6. However, in many networks, the 26 configuration information may be stored in Authentication 27 Authorization and Accounting (AAA) servers while user configuration 28 is mainly from Broadband Network Gateway (BNG) through DHCPv6 29 protocol. This document defines a Remote Authentication Dial In User 30 Service (RADIUS) attribute that carries CE configuration information 31 from AAA server to BNG. 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 April 30, 2017. 50 Copyright Notice 52 Copyright (c) 2016 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3. Configuration process with RADIUS . . . . . . . . . . . . . . 3 70 4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 6 72 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 6 73 4.3. Sub Options for S46 Container Option . . . . . . . . . . 7 74 4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 7 75 4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 8 76 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 8 77 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 9 78 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 9 79 4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 10 80 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 10 81 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 11 82 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 12 83 4.5. Softwire46 Sub Options Encapsulation . . . . . . . . . . 12 84 4.6. Table of attributes . . . . . . . . . . . . . . . . . . . 12 85 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13 86 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 87 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 88 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 89 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 90 9.1. Normative References . . . . . . . . . . . . . . . . . . 14 91 9.2. Informative References . . . . . . . . . . . . . . . . . 15 92 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 16 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 95 1. Introduction 97 Recently providers start to deploy IPv6 and consider how to transit 98 to IPv6. Many transition mechanisms based on the Address plus Port 99 (A+P) [RFC6346] have been proposed for running IPv4 over IPv6-only 100 infrastructure, including MAP-E, MAP-T, and Lightweight 4over6. 101 Mapping of Address and Port with Encapsulation(MAP-E)[RFC7597], 102 Mapping of Address and Port with using Translation(MAP-T)[RFC7599] 103 are stateless mechanisms for running IPv4 over IPv6-only 104 infrastructure. Lightweight 4over6[RFC7596] is a hub-and-spoke IPv4- 105 over-IPv6 tunneling mechanism, with complete independence of IPv4 and 106 IPv6 addressing. They provide both IPv4 and IPv6 connectivity 107 services simultaneously during the IPv4/IPv6 co-existing period. 108 MAP-E, MAP-T and Lightweight 4over6 have adopted Dynamic Host 109 Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as auto- 110 configuring protocol. The Customer Edge (CE) uses DHCPv6 options to 111 discover the Border Relay (BR) and get S46 configurations. 113 In many networks, user configuration information may be stored in AAA 114 (Authentication, Authorization, and Accounting) servers. Current AAA 115 servers communicate using the Remote Authentication Dial In User 116 Service (RADIUS) [RFC2865] protocol. In a fixed line broadband 117 network, the Broadband Network Gateways (BNGs) act as the access 118 gateway of users. The BNGs are assumed to embed a DHCPv6 server 119 function that allows them to locally handle any DHCPv6 requests 120 initiated by hosts. 122 Since the S46 configuration information is stored in AAA servers and 123 user configuration is mainly transmitted through DHCPv6 protocol 124 between BNGs and hosts/CEs, new RADIUS attributes are needed to 125 propagate the information from AAA servers to BNGs. The RADIUS 126 attributes designed in this document are especially for the MAP- 127 E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing 128 enough information to form the correspondent DHCPv6 configuration 129 options[RFC7598]. 131 2. Terminology 133 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 134 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 135 document are to be interpreted as described in [RFC2119]. 137 3. Configuration process with RADIUS 139 The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 140 cooperate to provide CE with MAP configuration information. The BNG 141 acts as a RADIUS client and as a DHCPv6 server. 143 CE BNG AAA Server 144 | | | 145 |-----1.DHCPv6 Solicit----->| | 146 | (ORO w/container option) | | 147 | |-------2.Access-Request------->| 148 | | (S46-Configuration attriubte) | 149 | | | 150 | |<------3.Access-Accept---------| 151 |<--4.DHCPv6 Advertisement--| (S46-Configuration attriubte) | 152 | | | 153 |-----5.DHCPv6 Request---->| | 154 | (container Option) | | 155 |<----6.DHCPv6 Reply--------| | 156 | (cointainer option) | | 157 | | | 158 DHCPv6 RADIUS 160 Figure 1: the cooperation between DHCPv6 and RADIUS combining with 161 RADIUS authentication 163 1. First, CE MAY initiate a DHCPv6 Solicit message that includes an 164 Option Request option(6) [RFC3315] with the S46 Container options as 165 defined in[RFC7598]. OPTION_S46_CONT_MAPE should be included for 166 MAP-E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and 167 OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. But note that 168 the ORO (Option Request option) with the S46 Container options could 169 be optional if the network was planned as S46-enabled as default. 171 2. When BNG receives the SOLICIT, it SHOULD initiate the radius 172 Access-Request message, in which the User-Name attribute (1) SHOULD 173 be filled by the CE MAC address or interface-id or both, to the 174 RADIUS server and the User-password attribute (2) SHOULD be filled by 175 the shared password that has been preconfigured on the DHCPv6 server, 176 requesting authentication as defined in [RFC2865] with the 177 corresponding Softwire46-Configuration Attribute, which will be 178 defined in the next Section. 180 3. If the authentication request is approved by the AAA server, an 181 Access-Accept message MUST be acknowledged with the corresponding 182 Softwire46-Configuration Attribute. 184 4. After receiving the Access-Accept message with the corresponding 185 Attribute, the BNG SHOULD respond the user an Advertisement message. 187 5. After receiving the Advertise message, the user can request for 188 the corresponding S46 Container option, by including the S46 189 Container option in the Request Message. 191 6. After receiving the client's Request messsage, containing the 192 corresponding S46 Container option the BNG SHOULD reply the user with 193 the message containing the S46 Container option. The recommended 194 format of the MAC address is defined as Calling-Station-Id 195 (Section 3.20 in [RFC3580] without the SSID (Service Set Identifier) 196 portion. 198 For Lightweight 4over6 [RFC7596], the subscriber's binding state 199 should be synchronized between AAA server and the lwAFTR. If the 200 bindings are pre-configured statically in both AAA server and lwAFTR, 201 the AAA server does not need to configure lwAFTR anymore. Otherwise, 202 if the bindings are locally creately in AAA server on-demand, it 203 should inform the lwAFTR with the subscriber's binding state, to 204 synchronise the binding information of the lwB4 with the lwAFTR. In 205 the Lightweight 4over6 scenario, the lwB4 could also be configured 206 through DHCPv4-over-DHCPv6 [RFC7341] as well as PCP [RFC6887], in 207 which the lwB4 act a PCP client and the BNG act as both a Radius 208 client and a PCP server. 210 The authorization operation could also be done independently after 211 the authentication process. In such scenario, after the 212 authentication operation, the client MAY initiate a DHCPv6 Request 213 message that includes the corresponding S46 Container options. As 214 similar to above scenario, the ORO with the corresponding S46 215 Container option in the initial DHCPv6 request could be optional if 216 the network was planned as S46-enabled as default. When BNG receives 217 the DHCPv6 Request, it SHOULD initiate the radius Access-Request 218 message, which MUST contain a Service-Type attribute (6) with the 219 value Authorize Only (17), the corresponding Softwire46-Configuration 220 Attribute, and a State attribute obtained from the previous 221 authentication process according to [RFC5080]. If the authorization 222 request is approved by the AAA server, an Access-Accept message MUST 223 be acknowledged with the corresponding Softwire46-Configuration 224 Attribute. The BNG SHOULD then send the DHCPv6 Reply message 225 containing the S46 Container option. 227 In both above-mentioned scenarios, Message-authenticator (type 80) 228 [RFC2869] SHOULD be used to protect both Access-Request and Access- 229 Accept messages. 231 If the BNG does not receive the corresponding MAP-Configuration 232 Attribute in the Access-Accept it MAY fallback to a pre-configured 233 default S46 configuration, if any. If the BNG does not have any pre- 234 configured default S46 configuration or if the BNG receives an 235 Access-Reject, then S46 cannot be established. 237 As specified in [RFC3315], section 18.1.4, "Creation and Transmission 238 of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew 239 message was sent at time T1 has not responded by time T2, the CE 240 (DHCPv6 client) SHOULD enter the Rebind state and attempt to contact 241 any available server. In this situation, the secondary BNG receiving 242 the DHCPv6 message MUST initiate a new Access-Request towards the AAA 243 server. The secondary BNG MAY include the MAP-Configuration 244 Attribute in its Access-Request. 246 4. Attributes 248 This section defines S46 Attributes which are used in the MAP 249 scenario. The attribute design follows [RFC6158] and refers 250 to[RFC6929]. 252 The S46 attributes are designed following the simplify principle. 253 Different sub options are required for each type of S46 Container 254 option. 256 4.1. Softwire46-Configuration Attribute 258 The Softwire46-Configuration Attribute is structured as follows: 260 0 1 2 3 261 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 263 | Type | Length | | 264 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 265 | | 266 + S46 Container Option(s) + 267 | | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 Type 270 TBD 271 Length 272 2 + the length of the S46 Container option(s) 273 S46 Container Option (s) 274 A variable field that may contains one or more S46 Container option(s), 275 defined in Section 4.2 277 4.2. S46 Container Options 279 Depending on the deployment scenario, a client might request for more 280 than one transition mechanism at a time, at least one S46 Container 281 option MUST be included in one MAP-Configuration Attribute. 283 0 1 2 3 284 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | Type | Length | | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 288 | | 289 + Sub Options + 290 | | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 Type 293 1 MAP-E Container Option 294 2 MAP-T Container Option 295 3 Lightweight 4over6 Container Option 296 Length 297 2 + the length of the sub options 298 Sub Option 299 A variable field that contains necessary sub options defined in 300 Section 4.3 and zero or several optional sub options, defined 301 in Section 4.4 303 4.3. Sub Options for S46 Container Option 305 4.3.1. S46-Rule Sub Option 307 Depending on deployment scenario, one Basic Mapping Rule and zero or 308 more Forwarding Mapping Rules MUST be included in one MAP-E or MAP-T 309 Container Option. 311 0 1 2 3 312 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | SubType | SubLen | | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 316 | | 317 + Sub Options + 318 | | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 SubType 321 1 Basic Mapping Rule (Not Forwarding Mapping Rule) 322 2 Forwarding Mapping Rule (Not Basic Mapping Rule) 323 3 Basic & Forwarding Mapping Rule 324 SubLen 325 2 + the length of the sub options 326 Sub Option 327 A variable field that contains sub options defined in 328 Section 4.4 330 4.3.2. S46-BR Sub Option 332 There MUST be atleast one S46-BR Sub Option included in each MAP-E 333 Container Option or Lightweight 4over6 Container Option. 335 0 1 2 3 336 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 338 | SubType | SubLen | BR-ipv6-address | 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 340 | BR-ipv6-address | 341 + + 342 | BR-ipv6-address | 343 + + 344 | BR-ipv6-address | 345 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | BR-ipv6-address | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 SubType 349 4 (SubType number, for the S46-BR sub option) 350 SubLen 351 18 (the length of the S46-BR sub option) 352 BR-ipv6-address 353 a 128-bits field that specifies the IPv6 address for the BR. 355 4.3.3. S46-DMR Sub Option 357 There MUST be exactly one S46-DMR Sub Option included in one MAP-T 358 Container Option. 360 0 1 2 3 361 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | SubType | SubLen |dmr-prefix6-len|dmr-ipv6-prefix| 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 365 | dmr-ipv6-prefix | 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 368 SubType 369 5 (SubType number, for the S46-DMR sub option) 370 SubLen 371 8 (the length of the Rule-IPv4-Prefix6 sub option) 372 dmr-prefix6-len 373 length of the IPv6 prefix, specified in the dmr-ipv6-prefix 374 field, expressed in bits 375 dmr-ipv6-prefix 376 a 32-bits field that specifies an IPv6 prefix that appears in 377 the Default Mapping Rule 379 4.3.4. S46-V4V6Bind Sub Option 381 There MUST be atmost one S46-RULE Sub Option included in each 382 Lightweight 4over6 Container Option. 384 0 1 2 3 385 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 | SubType | SubLen | ipv4-address | 388 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 389 | (Continued) |bindprefix6-len| | 390 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 391 | bind-ipv6-prefix | 392 + + 393 | bind-ipv6-prefix | 394 + + 395 | bind-ipv6-prefix | 396 + +-+-+-+-+-+-+-+-+ 397 | bind-ipv6-prefix | 398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 400 SubType 401 6 (SubType number, for the S46-V4V6Bind sub option) 402 SubLen 403 23 (the length of the S46-V4V6Bind sub option) 404 ipv4-address 405 a 32-bits field that specifies an IPv4 address that appears in 406 the V4V6Bind Option 407 bindprefix6-len 408 length of the IPv6 prefix, specified in the bind-ipv6-prefix 409 field, expressed in bits 410 bind-ipv6-prefix 411 a 128-bits field that specifies an IPv6 prefix that appears in 412 the V4V6Bind Option 414 4.3.5. S46-PORTPARAMS Sub Option 416 The S46-PORTPARAMS sub option specifies optional port set information 417 that MAY be provided to CEs. The S46-PORTPARAMS sub option canbe 418 included optionally by each type of S46 Container Option. 420 0 1 2 3 421 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | SubType | SubLen | PSID-Offset | PSID-len | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | PSID | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 SubType 429 7 (SubType number, for the S46-PORTPARAMS Sub Option sub option) 430 SubLen 431 6 (the length of the S46-PORTPARAMS Sub Option sub option) 432 PSID Offset 433 8 bits long field that specifies the numeric value for the S46 algorithm's excluded 434 port range/ offset bits (a bits), as per Section 5.1 of RFC 7597. 435 Allowed values are between 0 and 15. Default values for this field are specific to the 436 Softwire mechanism being implemented and are defined in the relevant specification document. 437 PSID-len 438 Bit length value of the number of significant bits in the PSID 439 field. (also known as 'k'). When set to 0, the PSID field is to 440 be ignored. After the first 'a' bits, there are k bits in the 441 port number representing valid of PSID. Subsequently, the 442 address sharing ratio would be 2 ^k. 443 PSID (Port-set ID) 444 Explicit 16-bit (unsigned word) PSID value. The PSID value 445 algorithmically identifies a set of ports assigned to a CE. The 446 first k-bits on the left of this 2-octets field is the PSID 447 value. The remaining (16-k) bits on the right are padding zeros. 449 4.4. Sub Options for S46-RULE Sub Option 451 4.4.1. Rule-IPv6-Prefix Sub Option 453 The Rule-IPv6-Prefix Sub Option is necessary for every S46-RULE sub 454 option. It should appear for once and only once. 456 The IPv6 Prefix sub option is followed the framed IPv6 prefix 457 designed in [RFC3162]. 459 0 1 2 3 460 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | SubType | SubLen | Reserved | prefix6-len | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 | | 465 | rule-ipv6-prefix | 466 | | 467 | | 468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 SubType 470 8 (SubType number, for the Rule-IPv6-Prefix6 sub option) 471 SubLen 472 20 (the length of the Rule-IPv6-Prefix6 sub option) 473 Reserved 474 Reserved for future usage. It should be set to all zero 475 prefix6-len 476 length of the IPv6 prefix, specified in the rule-ipv6-prefix 477 field, expressed in bits 478 rule-ipv6-prefix 479 a 128-bits field that specifies an IPv6 prefix that appears in 480 a MAP rule 482 4.4.2. Rule-IPv4-Prefix Sub Option 484 0 1 2 3 485 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 487 | SubType | SubLen | Reserved | prefix4-len | 488 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 | rule-ipv4-prefix | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 492 SubType 493 9 (SubType number, for the Rule-IPv4-Prefix6 sub option) 494 SubLen 495 8 (the length of the Rule-IPv4-Prefix6 sub option) 496 Reserved 497 Reserved for future usage. It should be set to all zero 498 Prefix4-len 499 length of the IPv6 prefix, specified in the rule-ipv6-prefix 500 field, expressed in bits 501 rule-ipv4-prefix 502 a 32-bits field that specifies an IPv4 prefix that appears in 503 a MAP rule 505 4.4.3. EA Length Sub Option 507 0 1 2 3 508 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 | SubType | SubLen | EA-len | 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 SubType 514 10 (SubType number, for the EA Length sub option) 515 SubLen 516 4 (the length of the EA Length sub option) 517 EA-len 518 16 bits long field that specifies the Embedded-Address (EA) 519 bit length. Allowed values range from 0 to 48 521 4.5. Softwire46 Sub Options Encapsulation 523 The table below shows which encapsulated Sub Options are mandatory, 524 optional, or not permitted for each defined S46 Container Option. 526 +----------------+-------+-------+--------------------+ 527 | Sub Option | MAP-E | MAP-T | Lightweight 4over6 | 528 +----------------+-------+-------+--------------------+ 529 | S46-Rule | M | M | N/P | 530 +----------------+-------+-------+--------------------+ 531 | S46-BR | M | N/P | M | 532 +----------------+-------+-------+--------------------+ 533 | S46-DMR | N/P | M | N/P | 534 +----------------+-------+-------+--------------------+ 535 | S46-V4V6Bind | N/P | N/P | O | 536 +----------------+-------+-------+--------------------+ 537 | S46-PORTPARAMS | O | O | O | 538 +----------------+-------+-------+--------------------+ 540 M - Maandabdatory, O - Optional, N/P - Not Permitted 542 4.6. Table of attributes 544 The following table provides a guide to which attributes may be found 545 in which kinds of packets, and in what quantity. 547 Request Accept Reject Challenge Accounting # Attribute 548 Request 549 0-1 0-1 0 0 0-1 TBD1 Softwire46- 550 Configuration 551 0-1 0-1 0 0 0-1 1 User-Name 552 0-1 0 0 0 0 2 User-Password 553 0-1 0-1 0 0 0-1 6 Service-Type 554 0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator 556 The following table defines the meaning of the above table entries. 558 0 This attribute MUST NOT be present in packet. 559 0+ Zero or more instances of this attribute MAY be present in 560 packet. 561 0-1 Zero or one instance of this attribute MAY be present in 562 packet. 563 1 Exactly one instance of this attribute MUST be present in 564 packet. 566 5. Diameter Considerations 568 S46 Configuration using Diameter [RFC6733] is specified in [RFC7678]. 570 6. IANA Considerations 572 This document requires the assignment of one new RADIUS Attributes 573 Type in the "Radius Types" registry (currently located at 574 http://www.iana.org/assignments/radius-types for the following 575 attributes: 577 o Softwire46-Configuration Attribute TBD1 579 IANA should allocate the numbers from the standard RADIUS Attributes 580 space using the "IETF Review" policy [RFC5226]. 582 7. Security Considerations 584 Known security vulnerabilities of the RADIUS protocol are discussed 585 in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for 586 providing security when RADIUS is carried in IPv6 is discussed in 587 [RFC3162]. 589 A malicious user may use MAC address proofing and/or dictionary 590 attack on the shared password that has been preconfigured on the 591 DHCPv6 server to get unauthorized configuration information. 593 Security considerations for MAP specific between MAP CE and BNG are 594 discussed in [RFC7597]. Security considerations for Lightweight 595 4over6 are discussed in [RFC7596]. Furthermore, generic DHCPv6 596 security mechanisms can be applied DHCPv6 intercommunication between 597 CE and BNG. 599 Security considerations for the Diameter protocol are discussed in 600 [RFC6733]. 602 8. Acknowledgements 604 The authors would like to thank the valuable comments made by Peter 605 Lothberg, Wojciech Dec, and Suresh Krishnan for this document. This 606 document was merged with draft-sun-softwire-lw4over6-radext-01, 607 thanks to everyone who contributed to this draft. 609 This document was produced using the xml2rfc tool [RFC7749]. 611 9. References 613 9.1. Normative References 615 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 616 Requirement Levels", BCP 14, RFC 2119, 617 DOI 10.17487/RFC2119, March 1997, 618 . 620 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 621 "Remote Authentication Dial In User Service (RADIUS)", 622 RFC 2865, DOI 10.17487/RFC2865, June 2000, 623 . 625 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 626 Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, 627 . 629 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", 630 RFC 3162, DOI 10.17487/RFC3162, August 2001, 631 . 633 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 634 C., and M. Carney, "Dynamic Host Configuration Protocol 635 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 636 2003, . 638 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, 639 "IEEE 802.1X Remote Authentication Dial In User Service 640 (RADIUS) Usage Guidelines", RFC 3580, 641 DOI 10.17487/RFC3580, September 2003, 642 . 644 [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication 645 Dial In User Service (RADIUS) Implementation Issues and 646 Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December 647 2007, . 649 [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", 650 BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, 651 . 653 [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User 654 Service (RADIUS) Protocol Extensions", RFC 6929, 655 DOI 10.17487/RFC6929, April 2013, 656 . 658 9.2. Informative References 660 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 661 Implementation in Roaming", RFC 2607, 662 DOI 10.17487/RFC2607, June 1999, 663 . 665 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 666 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 667 December 2005, . 669 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 670 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 671 DOI 10.17487/RFC5226, May 2008, 672 . 674 [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to 675 the IPv4 Address Shortage", RFC 6346, 676 DOI 10.17487/RFC6346, August 2011, 677 . 679 [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, 680 Ed., "Diameter Base Protocol", RFC 6733, 681 DOI 10.17487/RFC6733, October 2012, 682 . 684 [RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and 685 P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, 686 DOI 10.17487/RFC6887, April 2013, 687 . 689 [RFC7341] Sun, Q., Cui, Y., Siodelski, M., Krishnan, S., and I. 690 Farrer, "DHCPv4-over-DHCPv6 (DHCP 4o6) Transport", 691 RFC 7341, DOI 10.17487/RFC7341, August 2014, 692 . 694 [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. 695 Farrer, "Lightweight 4over6: An Extension to the Dual- 696 Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, 697 July 2015, . 699 [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., 700 Murakami, T., and T. Taylor, Ed., "Mapping of Address and 701 Port with Encapsulation (MAP-E)", RFC 7597, 702 DOI 10.17487/RFC7597, July 2015, 703 . 705 [RFC7598] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, 706 W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for 707 Configuration of Softwire Address and Port-Mapped 708 Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, 709 . 711 [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., 712 and T. Murakami, "Mapping of Address and Port using 713 Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July 714 2015, . 716 [RFC7678] Zhou, C., Taylor, T., Sun, Q., and M. Boucadair, 717 "Attribute-Value Pairs for Provisioning Customer Equipment 718 Supporting IPv4-Over-IPv6 Transitional Solutions", 719 RFC 7678, DOI 10.17487/RFC7678, October 2015, 720 . 722 [RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", 723 RFC 7749, DOI 10.17487/RFC7749, February 2016, 724 . 726 Additional Authors 727 Qiong Sun 728 China Telecom 729 Beijing China 730 Email: sunqiong@ctbri.com.cn 732 Qi Sun 733 Tsinghua University 734 Department of Computer Science, Tsinghua University 735 Beijing 100084 736 P.R.China 737 Phone: +86-10-6278-5822 738 Email: sunqibupt@gmail.com 740 Cathy Zhou 741 Huawei Technologies 742 Bantian, Longgang District 743 Shenzhen 518129 744 Email: cathy.zhou@huawei.com 746 Tina Tsou 747 Huawei Technologies(USA) 748 2330 Central Expressway 749 Santa Clara, CA 95050 750 USA 751 Email: Tina.Tsou.Zouting@huawei.com 753 ZiLong Liu 754 Tsinghua University 755 Beijing 100084 756 P.R.China 757 Phone: +86-10-6278-5822 758 Email: liuzilong8266@126.com 760 Yong Cui 761 Tsinghua University 762 Beijing 100084 763 P.R.China 764 Phone: +86-10-62603059 765 Email: yong@csnet1.cs.tsinghua.edu.cn 767 Authors' Addresses 768 Sheng Jiang 769 Huawei Technologies Co., Ltd 770 Q14, Huawei Campus, No.156 Beiqing Road 771 Hai-Dian District, Beijing, 100095 772 P.R. China 774 Email: jiangsheng@huawei.com 776 Yu Fu 777 CNNIC 778 No.4 South 4th Street, Zhongguancun 779 Hai-Dian District, Beijing, 100190 780 P.R. China 782 Email: fuyu@cnnic.cn 784 Bing Liu 785 Huawei Technologies Co., Ltd 786 Q14, Huawei Campus, No.156 Beiqing Road 787 Hai-Dian District, Beijing, 100095 788 P.R. China 790 Email: leo.liubing@huawei.com 792 Peter Deacon 793 IEA Software, Inc. 794 P.O. Box 1170 795 Veradale, WA 99037 796 USA 798 Email: peterd@iea-software.com 800 Chongfeng Xie 801 China Telecom 802 Beijing 803 P.R. China 805 Email: xiechf@ctbri.com.cn 806 Tianxiang Li 807 Tsinghua University 808 Beijing 100084 809 P.R.China 811 Email: peter416733@gmail.com