idnits 2.17.1 draft-ietf-softwire-map-radius-06.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 (June 17, 2016) is 2863 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) ** 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: 3 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: December 19, 2016 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 June 17, 2016 16 RADIUS Attribute for MAP 17 draft-ietf-softwire-map-radius-06 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 December 19, 2016. 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. MAP-Configuration Attribute . . . . . . . . . . . . . . . 6 72 4.2. S46 Container Options . . . . . . . . . . . . . . . . . . 7 73 4.3. Sub Options for S46 Container Option . . . . . . . . . . 7 74 4.3.1. S46-Rule Sub Option . . . . . . . . . . . . . . . . . 8 75 4.3.2. S46-BR Sub Option . . . . . . . . . . . . . . . . . . 8 76 4.3.3. S46-DMR Sub Option . . . . . . . . . . . . . . . . . 9 77 4.3.4. S46-V4V6Bind Sub Option . . . . . . . . . . . . . . . 10 78 4.3.5. S46-PORTPARAMS Sub Option . . . . . . . . . . . . . . 10 79 4.4. Sub Options for S46-RULE Sub Option . . . . . . . . . . . 11 80 4.4.1. Rule-IPv6-Prefix Sub Option . . . . . . . . . . . . . 11 81 4.4.2. Rule-IPv4-Prefix Sub Option . . . . . . . . . . . . . 12 82 4.4.3. EA Length Sub Option . . . . . . . . . . . . . . . . 13 83 4.5. Table of attributes . . . . . . . . . . . . . . . . . . . 13 84 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 13 85 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 86 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 87 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 88 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 89 9.1. Normative References . . . . . . . . . . . . . . . . . . 15 90 9.2. Informative References . . . . . . . . . . . . . . . . . 15 91 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 17 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 94 1. Introduction 96 Recently providers start to deploy IPv6 and consider how to transit 97 to IPv6. Many transition mechanisms have been proposed for running 98 IPv4 over IPv6-only infrastructure, including MAP-E, MAP-T, and 99 Lightweight 4over6. Mapping of Address and Port with 100 Encapsulation(MAP-E)[RFC7597], Mapping of Address and Port with using 101 Translation(MAP-T)[RFC7599] are stateless mechanisms for running IPv4 102 over IPv6-only infrastructure. Lightweight 4over6[RFC7596] is a hub- 103 and-spoke IPv4-over-IPv6 tunneling mechanism, with complete 104 independence of IPv4 and IPv6 addressing. They provide both IPv4 and 105 IPv6 connectivity services simultaneously during the IPv4/IPv6 co- 106 existing period. MAP-E, MAP-T and Lightweight 4over6 have adopted 107 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315] as 108 auto-configuring protocol. The Customer Edge (CE) uses DHCPv6 109 options to discover the Border Relay (BR) and get MAP configurations. 111 In many networks, user configuration information may be stored by AAA 112 (Authentication, Authorization, and Accounting) servers. Current AAA 113 servers communicate using the Remote Authentication Dial In User 114 Service (RADIUS) [RFC2865] protocol. In a fixed line broadband 115 network, the Broadband Network Gateways (BNGs) act as the access 116 gateway of users. The BNGs are assumed to embed a DHCPv6 server 117 function that allows them to locally handle any DHCPv6 requests 118 initiated by hosts. 120 Since the MAP configuration information is stored in AAA servers and 121 user configuration is mainly transmitted through DHCPv6 protocol 122 between BNGs and hosts/CEs, new RADIUS attributes are needed to 123 propagate the information from AAA servers to BNGs. The RADIUS 124 attributes designed in this document are especially for the MAP- 125 E[RFC7597], MAP-T[RFC7599] and Lightweight 4over6[RFC7596], providing 126 enough information to form the correspondent DHCPv6 configuration 127 options[RFC7598]. 129 2. Terminology 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in [RFC2119]. 135 3. Configuration process with RADIUS 137 The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 138 cooperate to provide CE with MAP configuration information. 140 CE BNG AAA Server 141 | | | 142 |------DHCPv6 Solicit----->| | 143 | (Option Request w/container option) | 144 | |-------Access-Request------->| 145 | | (Map attriubte) | 146 | | | 147 | |<-------Access-Accept--------| 148 |<---DHCPv6 Advertisement--| (MAP attriubte) | 149 | | | 150 |------DHCPv6 Request---->| | 151 | (container Option) | | 152 |<---- -DHCPv6 Reply-------| | 153 | (cointainer option) | | 154 | | | 155 DHCPv6 RADIUS 157 Figure 1: the cooperation between DHCPv6 and RADIUS combining with 158 RADIUS authentication 160 The BNG acts as a RADIUS client and as a DHCPv6 server. First, CE 161 MAY initiate a DHCPv6 Solicit message that includes an Option Request 162 option (6) [RFC3315] with the Container options as defined 163 in[RFC7598]. OPTION_S46_CONT_MAPE should be included for MAP- 164 E[RFC7597], OPTION_S46_CONT_MAPT for MAP-T[RFC7599], and 165 OPTION_S46_CONT_LW for Lightweight 4over6[RFC7596]. But note that 166 the ORO (Option Request option) with the MAP option could be optional 167 if the network was planned as MAP-enabled as default. When BNG 168 receives the SOLICIT, it SHOULD initiates radius Access-Request 169 message, in which the User-Name attribute (1) SHOULD be filled by the 170 CE MAC address or interface-id or both, to the RADIUS server and the 171 User-password attribute (2) SHOULD be filled by the shared password 172 that has been preconfigured on the DHCPv6 server, requesting 173 authentication as defined in [RFC2865] with the corresponding MAP- 174 Configuration Attribute, which will be defined in the next Section. 176 If the authentication request is approved by the AAA server, an 177 Access-Accept message MUST be acknowledged with the corresponding 178 MAP-Configuration Attribute. After receiving the Access-Accept 179 message with the corresponding Attribute, the BNG SHOULD respond the 180 user an Advertisement message. Then the user can requests for the 181 corresponding Container option, and the BNG SHOULD reply the user 182 with the message containing the Container option. The recommended 183 format of the MAC address is defined as Calling-Station-Id 184 (Section 3.20 in [RFC3580] without the SSID (Service Set Identifier) 185 portion. 187 For Lightweight 4over6 [RFC7596], the subscriber's binding state 188 should be synchronized between AAA server and the lwAFTR. If the 189 bindings are pre-configured statically in both AAA server and lwAFTR, 190 the AAA server does not need to configure lwAFTR anymore. Otherwise, 191 if the bindings are locally creately in AAA server on-demand, it 192 should inform the lwAFTR with the subscriber's binding state, to 193 synchronise the binding information of the lwB4 with the lwAFTR. In 194 the Lightweight 4over6 scenario, the lwB4 could also be configured 195 through DHCPv4-over-DHCPv6 [RFC7341] as well as PCP [RFC6887], in 196 which the lwB4 act a PCP client and the BNG act as both a Radius 197 client and a PCP server. 199 Figure 2 describes another scenario, in which the authorization 200 operation is not coupled with authentication. Authorization is done 201 independently after the authentication process. As similar to above 202 scenario, the ORO with the corresponding MAP option in the initial 203 DHCPv6 request could be optional if the network was planned as MAP- 204 enabled as default. 206 CE BNG AAA Server 207 | | | 208 |------DHCPv6 Request---->| | 209 |(Option Request w/container option) | 210 | |-------Access-Request------->| 211 | | (MAP attribute) | 212 | | | 213 | |<-------Access-Accept--------| 214 | | (MAP attribute) | 215 |<-----DHCPv6 Reply--------| | 216 | (container option) | | 217 | | | 218 DHCPv6 RADIUS 220 Figure 2: the cooperation between DHCPv6 and RADIUS decoupled with 221 RADIUS authentication 223 In the above mentioned scenario, the Access-Request packet SHOULD 224 contain a Service-Type attribute (6) with the value Authorize Only 225 (17); thus, according to [RFC5080], the Access-Request packet MUST 226 contain a State attribute that obtained from the previous 227 authentication process. 229 In both above-mentioned scenarios, Message-authenticator (type 80) 230 [RFC2869] SHOULD be used to protect both Access-Request and Access- 231 Accept messages. 233 After receiving the corresponding MAP-Configuration Attribute in the 234 initial Access-Accept, the BNG SHOULD store the received MAP 235 configuration parameters locally. When the CE sends a DHCPv6 Request 236 message to request an extension of the lifetimes for the assigned 237 address, the BNG does not have to initiate a new Access-Request 238 towards the AAA server to request the MAP configuration parameters. 239 The BNG could retrieve the previously stored MAP configuration 240 parameters and use them in its reply. 242 If the BNG does not receive the corresponding MAP-Configuration 243 Attribute in the Access-Accept it MAY fallback to a pre-configured 244 default MAP configuration, if any. If the BNG does not have any pre- 245 configured default MAP configuration or if the BNG receives an 246 Access-Reject, the MAP cannot be established. 248 As specified in [RFC3315], section 18.1.4, "Creation and Transmission 249 of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew 250 message was sent at time T1 has not responded by time T2, the CE 251 (DHCPv6 client) SHOULD enter the Rebind state and attempt to contact 252 any available server. In this situation, the secondary BNG receiving 253 the DHCPv6 message MUST initiate a new Access-Request towards the AAA 254 server. The secondary BNG MAY include the MAP-Configuration 255 Attribute in its Access-Request. 257 4. Attributes 259 This section defines S46 Attributes which are used in the MAP 260 scenario. The attribute design follows [RFC6158] and refers 261 to[RFC6929]. 263 The S46 attributes are designed following the simplify principle. 264 Different sub options are required for each type of S46 Container 265 option. 267 4.1. MAP-Configuration Attribute 269 The MAP-Configuration Attribute is structured as follows: 271 0 1 2 3 272 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 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | Type | Length | | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 276 | | 277 + S46 Container Option(s) + 278 | | 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 Type 281 TBD 282 Length 283 2 + the length of the S46 Container option(s) 284 S46 Container Option (s) 285 A variable field that may contains one or more S46 Container option(s), 286 defined in Section 4.2 288 4.2. S46 Container Options 290 Depending on the deployment scenario, a client might request for more 291 than one transition mechanism at a time, at least one S46 Container 292 option MUST be included in one MAP-Configuration Attribute. 294 0 1 2 3 295 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 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | Type | Length | | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 299 | | 300 + Sub Options + 301 | | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 Type 304 1 MAP-E Container Option 305 2 MAP-T Container Option 306 3 Lightweight 4over6 Container Option 307 Length 308 2 + the length of the sub options 309 Sub Option 310 A variable field that contains necessary sub options defined in 311 Section 4.3 and zero or several optional sub options, defined 312 in Section 4.4 314 4.3. Sub Options for S46 Container Option 315 4.3.1. S46-Rule Sub Option 317 Depending on deployment scenario, one Basic Mapping Rule and zero or 318 more Forwarding Mapping Rules MUST be included in one MAP-E or MAP-T 319 Container Option. 321 0 1 2 3 322 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 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 | SubType | SubLen | | 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 326 | | 327 + Sub Options + 328 | | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 SubType 331 1 Basic Mapping Rule (Not Forwarding Mapping Rule) 332 2 Forwarding Mapping Rule (Not Basic Mapping Rule) 333 3 Basic & Forwarding Mapping Rule 334 SubLen 335 2 + the length of the sub options 336 Sub Option 337 A variable field that contains sub options defined in 338 Section 4.4 340 4.3.2. S46-BR Sub Option 342 There MUST be atleast one S46-BR Sub Option included in one S46 343 Container Option. 345 0 1 2 3 346 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 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | SubType | SubLen | BR-ipv6-address | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 350 | BR-ipv6-address | 351 + + 352 | BR-ipv6-address | 353 + + 354 | BR-ipv6-address | 355 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | BR-ipv6-address | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 SubType 359 4 (SubType number, for the S46-BR sub option) 360 SubLen 361 18 (the length of the S46-BR sub option) 362 BR-ipv6-address 363 a 128-bits field that specifies the IPv6 address for the BR. 365 4.3.3. S46-DMR Sub Option 367 There MUST be exactly one S46-DMR Sub Option included in one MAP-T 368 Container Option. 370 0 1 2 3 371 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 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 | SubType | SubLen |dmr-prefix6-len|dmr-ipv6-prefix| 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 375 | dmr-ipv6-prefix | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 SubType 379 5 (SubType number, for the S46-DMR sub option) 380 SubLen 381 8 (the length of the Rule-IPv4-Prefix6 sub option) 382 dmr-prefix6-len 383 length of the IPv6 prefix, specified in the dmr-ipv6-prefix 384 field, expressed in bits 385 dmr-ipv6-prefix 386 a 32-bits field that specifies an IPv6 prefix that appears in 387 the Default Mapping Rule 389 4.3.4. S46-V4V6Bind Sub Option 391 There MUST be atmost one S46-RULE Sub Option included in each 392 Lightweight 4over6 Container Option. 394 0 1 2 3 395 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 396 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 397 | SubType | SubLen | ipv4-address | 398 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 399 | (Continued) |bindprefix6-len| | 400 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 401 | bind-ipv6-prefix | 402 + + 403 | bind-ipv6-prefix | 404 + + 405 | bind-ipv6-prefix | 406 + +-+-+-+-+-+-+-+-+ 407 | bind-ipv6-prefix | 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 410 SubType 411 6 (SubType number, for the S46-V4V6Bind sub option) 412 SubLen 413 23 (the length of the S46-V4V6Bind sub option) 414 Prefix4-len 415 length of the IPv4 prefix, specified in the rule-ipv4-prefix 416 field, expressed in bits 417 ipv4-address 418 a 32-bits field that specifies an IPv4 address that appears in 419 the V4V6Bind Option 420 bindprefix6-len 421 length of the IPv6 prefix, specified in the bind-ipv6-prefix 422 field, expressed in bits 423 rule-ipv6-prefix 424 a 128-bits field that specifies an IPv6 prefix that appears in 425 the V4V6Bind Option 427 4.3.5. S46-PORTPARAMS Sub Option 429 The S46-PORTPARAMS sub option specifies optional port set information 430 that MAY be provided to CEs. The S46-PORTPARAMS sub option canbe 431 included optionally by each type of S46 Container Option. 433 0 1 2 3 434 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 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 | SubType | SubLen | PSID-Offset | PSID-len | 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | PSID | 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 SubType 442 7 (SubType number, for the S46-PORTPARAMS Sub Option sub option) 443 SubLen 444 6 (the length of the S46-PORTPARAMS Sub Option sub option) 445 PSID Offset 446 8 bits long field that specifies the numeric value for the S46 algorithm's excluded 447 port range/ offset bits (a bits), as per Section 5.1 of RFC 7597. 448 Allowed values are between 0 and 15. Default values for this field are specific to the 449 Softwire mechanism being implemented and are defined in the relevant specification document. 450 PSID-len 451 Bit length value of the number of significant bits in the PSID 452 field. (also known as 'k'). When set to 0, the PSID field is to 453 be ignored. After the first 'a' bits, there are k bits in the 454 port number representing valid of PSID. Subsequently, the 455 address sharing ratio would be 2 ^k. 456 PSID (Port-set ID) 457 Explicit 16-bit (unsigned word) PSID value. The PSID value 458 algorithmically identifies a set of ports assigned to a CE. The 459 first k-bits on the left of this 2-octets field is the PSID 460 value. The remaining (16-k) bits on the right are padding zeros. 462 4.4. Sub Options for S46-RULE Sub Option 464 4.4.1. Rule-IPv6-Prefix Sub Option 466 The Rule-IPv6-Prefix Sub Option is necessary for every S46-RULE sub 467 option. It should appear for once and only once. 469 The IPv6 Prefix sub option is followed the framed IPv6 prefix 470 designed in [RFC3162]. 472 0 1 2 3 473 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 474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 475 | SubType | SubLen | Reserved | prefix6-len | 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 | | 478 | rule-ipv6-prefix | 479 | | 480 | | 481 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 SubType 483 8 (SubType number, for the Rule-IPv6-Prefix6 sub option) 484 SubLen 485 20 (the length of the Rule-IPv6-Prefix6 sub option) 486 Reserved 487 Reserved for future usage. It should be set to all zero 488 prefix6-len 489 length of the IPv6 prefix, specified in the rule-ipv6-prefix 490 field, expressed in bits 491 rule-ipv6-prefix 492 a 128-bits field that specifies an IPv6 prefix that appears in 493 a MAP rule 495 4.4.2. Rule-IPv4-Prefix Sub Option 497 0 1 2 3 498 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 499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 500 | SubType | SubLen | Reserved | prefix4-len | 501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 502 | rule-ipv4-prefix | 503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 505 SubType 506 9 (SubType number, for the Rule-IPv4-Prefix6 sub option) 507 SubLen 508 8 (the length of the Rule-IPv4-Prefix6 sub option) 509 Reserved 510 Reserved for future usage. It should be set to all zero 511 Prefix4-len 512 length of the IPv6 prefix, specified in the rule-ipv6-prefix 513 field, expressed in bits 514 rule-ipv4-prefix 515 a 32-bits field that specifies an IPv4 prefix that appears in 516 a MAP rule 518 4.4.3. EA Length Sub Option 520 0 1 2 3 521 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 522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 523 | SubType | SubLen | EA-len | 524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 526 SubType 527 10 (SubType number, for the EA Length sub option) 528 SubLen 529 4 (the length of the EA Length sub option) 530 EA-len 531 16 bits long field that specifies the Embedded-Address (EA) 532 bit length. Allowed values range from 0 to 48 534 4.5. Table of attributes 536 The following table provides a guide to which attributes may be found 537 in which kinds of packets, and in what quantity. 539 Request Accept Reject Challenge Accounting # Attribute 540 Request 541 0-1 0-1 0 0 0-1 TBD1 MAP- 542 Configuration 543 0-1 0-1 0 0 0-1 1 User-Name 544 0-1 0 0 0 0 2 User-Password 545 0-1 0-1 0 0 0-1 6 Service-Type 546 0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator 548 The following table defines the meaning of the above table entries. 550 0 This attribute MUST NOT be present in packet. 551 0+ Zero or more instances of this attribute MAY be present in 552 packet. 553 0-1 Zero or one instance of this attribute MAY be present in 554 packet. 555 1 Exactly one instance of this attribute MUST be present in 556 packet. 558 5. Diameter Considerations 560 This attribute is usable within either RADIUS or Diameter [RFC6733]. 561 Since the Attributes defined in this document will be allocated from 562 the standard RADIUS type space, no special handling is required by 563 Diameter entities. 565 6. IANA Considerations 567 This document requires the assignment of two new RADIUS Attributes 568 Types in the "Radius Types" registry (currently located at 569 http://www.iana.org/assignments/radius-types for the following 570 attributes: 572 o MAP-Configuration TBD1 574 IANA should allocate the numbers from the standard RADIUS Attributes 575 space using the "IETF Review" policy [RFC5226]. 577 7. Security Considerations 579 In softwire scenarios, both CE and BNG are within a provider network, 580 which can be considered as a closed network and a lower security 581 threat environment. A similar consideration can be applied to the 582 RADIUS message exchange between BNG and the AAA server. 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 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", 626 RFC 3162, DOI 10.17487/RFC3162, August 2001, 627 . 629 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 630 C., and M. Carney, "Dynamic Host Configuration Protocol 631 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 632 2003, . 634 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, 635 "IEEE 802.1X Remote Authentication Dial In User Service 636 (RADIUS) Usage Guidelines", RFC 3580, 637 DOI 10.17487/RFC3580, September 2003, 638 . 640 [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication 641 Dial In User Service (RADIUS) Implementation Issues and 642 Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December 643 2007, . 645 [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", 646 BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, 647 . 649 [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User 650 Service (RADIUS) Protocol Extensions", RFC 6929, 651 DOI 10.17487/RFC6929, April 2013, 652 . 654 9.2. Informative References 656 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 657 Implementation in Roaming", RFC 2607, 658 DOI 10.17487/RFC2607, June 1999, 659 . 661 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 662 Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, 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 [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, 675 Ed., "Diameter Base Protocol", RFC 6733, 676 DOI 10.17487/RFC6733, October 2012, 677 . 679 [RFC6887] Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R., and 680 P. Selkirk, "Port Control Protocol (PCP)", RFC 6887, 681 DOI 10.17487/RFC6887, April 2013, 682 . 684 [RFC7341] Sun, Q., Cui, Y., Siodelski, M., Krishnan, S., and I. 685 Farrer, "DHCPv4-over-DHCPv6 (DHCP 4o6) Transport", 686 RFC 7341, DOI 10.17487/RFC7341, August 2014, 687 . 689 [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. 690 Farrer, "Lightweight 4over6: An Extension to the Dual- 691 Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, 692 July 2015, . 694 [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., 695 Murakami, T., and T. Taylor, Ed., "Mapping of Address and 696 Port with Encapsulation (MAP-E)", RFC 7597, 697 DOI 10.17487/RFC7597, July 2015, 698 . 700 [RFC7598] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, 701 W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for 702 Configuration of Softwire Address and Port-Mapped 703 Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, 704 . 706 [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., 707 and T. Murakami, "Mapping of Address and Port using 708 Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July 709 2015, . 711 [RFC7749] Reschke, J., "The "xml2rfc" Version 2 Vocabulary", 712 RFC 7749, DOI 10.17487/RFC7749, February 2016, 713 . 715 Additional Authors 716 Qiong Sun 717 China Telecom 718 Beijing China 719 Email: sunqiong@ctbri.com.cn 721 Qi Sun 722 Tsinghua University 723 Department of Computer Science, Tsinghua University 724 Beijing 100084 725 P.R.China 726 Phone: +86-10-6278-5822 727 Email: sunqibupt@gmail.com 729 Cathy Zhou 730 Huawei Technologies 731 Bantian, Longgang District 732 Shenzhen 518129 733 Email: cathy.zhou@huawei.com 735 Tina Tsou 736 Huawei Technologies(USA) 737 2330 Central Expressway 738 Santa Clara, CA 95050 739 USA 740 Email: Tina.Tsou.Zouting@huawei.com 742 ZiLong Liu 743 Tsinghua University 744 Beijing 100084 745 P.R.China 746 Phone: +86-10-6278-5822 747 Email: liuzilong8266@126.com 749 Yong Cui 750 Tsinghua University 751 Beijing 100084 752 P.R.China 753 Phone: +86-10-62603059 754 Email: yong@csnet1.cs.tsinghua.edu.cn 756 Authors' Addresses 757 Sheng Jiang 758 Huawei Technologies Co., Ltd 759 Q14, Huawei Campus, No.156 Beiqing Road 760 Hai-Dian District, Beijing, 100095 761 P.R. China 763 Email: jiangsheng@huawei.com 765 Yu Fu 766 CNNIC 767 No.4 South 4th Street, Zhongguancun 768 Hai-Dian District, Beijing, 100190 769 P.R. China 771 Email: fuyu@cnnic.cn 773 Bing Liu 774 Huawei Technologies Co., Ltd 775 Q14, Huawei Campus, No.156 Beiqing Road 776 Hai-Dian District, Beijing, 100095 777 P.R. China 779 Email: leo.liubing@huawei.com 781 Peter Deacon 782 IEA Software, Inc. 783 P.O. Box 1170 784 Veradale, WA 99037 785 USA 787 Email: peterd@iea-software.com 789 Chongfeng Xie 790 China Telecom 791 Beijing 792 P.R. China 794 Email: xiechf@ctbri.com.cn 795 Tianxiang Li 796 Tsinghua University 797 Beijing 100084 798 P.R.China 800 Email: peter416733@gmail.com