idnits 2.17.1 draft-ietf-softwire-map-radius-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1218 has weird spacing: '...uration tlv ...' -- The document date (June 26, 2018) is 2124 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) == Missing Reference: 'RFC 8114' is mentioned on line 1304, but not defined ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). 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 28, 2018 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 M. Boucadair 15 Orange 16 June 26, 2018 18 RADIUS Attributes for Address plus Port based Softwire Mechanisms 19 draft-ietf-softwire-map-radius-16 21 Abstract 23 IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6 24 connectivity services simultaneously during the IPv4/IPv6 co- 25 existence period. DHCPv6 options have been defined for configuring 26 clients to use MAP-E, MAP-T, Lightweight 4over6 and Multicast Basic 27 Bridging BroadBand (mB4) in multicast scenarios. However, in many 28 networks, the configuration information may be stored in an AAA 29 server, while user configuration information is mainly provided by 30 the BNG through the DHCPv6 protocol. This document defines three new 31 RADIUS attributes that carry CE or mB4 configuration information from 32 an AAA server to BNG. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at https://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on December 28, 2018. 50 Copyright Notice 52 Copyright (c) 2018 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 (https://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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 3. Configuration process with RADIUS . . . . . . . . . . . . . . 4 70 4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 7 71 4.1. Softwire46-Configuration Attribute . . . . . . . . . . . 8 72 4.2. Softwire46 TLVs . . . . . . . . . . . . . . . . . . . . . 9 73 4.3. Softwire46 Sub TLVs . . . . . . . . . . . . . . . . . . . 11 74 4.4. The format of Softwire46 Sub TLVs . . . . . . . . . . . . 13 75 4.4.1. S46-Rule Sub TLV . . . . . . . . . . . . . . . . . . 13 76 4.4.2. S46-BR Sub TLV . . . . . . . . . . . . . . . . . . . 14 77 4.4.3. S46-DMR Sub TLV . . . . . . . . . . . . . . . . . . . 15 78 4.4.4. S46-V4V6Bind Sub TLV . . . . . . . . . . . . . . . . 16 79 4.4.5. S46-PORTPARAMS Sub TLV . . . . . . . . . . . . . . . 16 80 4.5. Sub-TLVs for S46-Rule Sub TLV . . . . . . . . . . . . . . 17 81 4.5.1. Rule-IPv6-Prefix sub-TLV . . . . . . . . . . . . . . 17 82 4.5.2. Rule-IPv4-Prefix Sub-TLV . . . . . . . . . . . . . . 18 83 4.5.3. EA-Length Sub-TLV . . . . . . . . . . . . . . . . . . 19 84 4.6. Sub-TLVs for S46-v4v6Bind Sub TLV . . . . . . . . . . . . 19 85 4.6.1. The IPv4-address sub-TLV . . . . . . . . . . . . . . 19 86 4.6.2. The Bind-IPv6-Prefix Sub-TLV . . . . . . . . . . . . 19 87 4.7. Sub-TLVs for S46-PORTPARAMS Sub TLV . . . . . . . . . . . 20 88 4.7.1. The PSID-offset sub-TLV . . . . . . . . . . . . . . . 20 89 4.7.2. The PSID-len sub-TLV . . . . . . . . . . . . . . . . 21 90 4.7.3. The PSID sub-TLV . . . . . . . . . . . . . . . . . . 21 91 4.8. Softwire46-Priority Attribute . . . . . . . . . . . . . . 21 92 4.9. Softwire46-Multicast Attribute . . . . . . . . . . . . . 22 93 4.9.1. ASM-Prefix64 TLV . . . . . . . . . . . . . . . . . . 24 94 4.9.2. SSM-Prefix64 TLV . . . . . . . . . . . . . . . . . . 25 95 4.9.3. U-Prefix64 TLV . . . . . . . . . . . . . . . . . . . 26 97 4.10. Table of attributes . . . . . . . . . . . . . . . . . . . 27 98 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 28 99 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 100 6.1. New RADIUS Attributes . . . . . . . . . . . . . . . . . . 28 101 6.2. New RADIUS TLVs . . . . . . . . . . . . . . . . . . . . . 29 102 6.3. S46 Mechanisms and Their Identifying Option Codes . . . . 29 103 7. Security Considerations . . . . . . . . . . . . . . . . . . . 30 104 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 30 105 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 106 9.1. Normative References . . . . . . . . . . . . . . . . . . 31 107 9.2. Informative References . . . . . . . . . . . . . . . . . 32 108 Additional Authors . . . . . . . . . . . . . . . . . . . . . . . 34 109 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35 111 1. Introduction 113 Recently, providers have started deployment and transition to IPv6. 114 Many IPv4 service continuity mechanisms based on the Address plus 115 Port (A+P) [RFC6346] have been proposed for running IPv4 over 116 IPv6-only infrastructure. Mapping of Address and Port with 117 Encapsulation (MAP-E)[RFC7597] and Mapping of Address and Port using 118 Translation (MAP-T) [RFC7599] are stateless mechanisms for running 119 IPv4 over IPv6-only infrastructure. Lightweight 4over6 [RFC7596] is 120 a hub-and-spoke IPv4-over-IPv6 tunneling mechanism, with complete 121 independence of IPv4 and IPv6 addressing. And all these mechanisms 122 are unicast. MAP-E, MAP-T, and Lightweight 4over6 Customer Edge (CE) 123 devices may be provisioned by means of Dynamic Host Configuration 124 Protocol for IPv6 (DHCPv6) [RFC3315]. [RFC7598] defines DHCPv6 125 options for provisioning CEs for unicast softwires. 127 [RFC8114] specifies a generic solution for delivery of IPv4 multicast 128 services to IPv4 clients over an IPv6 multicast network. The 129 solution applies also to lw4o6 and MAP-E. [RFC8115] defines a DHCPv6 130 PREFIX64 option to convey the IPv6 prefixes to be used for 131 constructing IPv4-embedded IPv6 addresses to inform the mB4 element 132 of the PREFIX64. 134 In many networks, user configuration information may be stored in an 135 Authentication, Authorization, and Accounting (AAA) server. 136 Currently, the AAA servers communicate using the Remote 137 Authentication Dial In User Service (RADIUS) [RFC2865] protocol. In 138 a fixed line broadband network, a Broadband Network Gateway (BNG) 139 acts as the access gateway of users. A DHCPv6 server function is 140 assumed to embed in the BNG that allows it to locally handle any 141 DHCPv6 requests initiated by hosts. So the BNG is used in this 142 document to describe a device which functions as both the AAA client 143 and DHCPv6 sever. 145 Since the S46 configuration information is stored in an AAA servers 146 and user configuration information is mainly transmitted through 147 DHCPv6 protocol between the BNGs and hosts/CEs, new RADIUS attributes 148 are needed to propagate the information from the AAA servers to BNGs. 149 The RADIUS attributes designed in this document are especially for 150 the MAP-E[RFC7597], MAP-T [RFC7599] and Lightweight 4over6 [RFC7596], 151 providing enough information to form the corresponding DHCPv6 152 configuration options[RFC7598]. This document is not concerned with 153 the RADIUS attribute for Dual-Stack Lite [RFC6333] as it is already 154 covered in [RFC6519]. At the Section 4.9, a new RADIUS attribute is 155 defined to be used for carrying the Multicast-Prefixes-64, based on 156 the equivalent DHCPv6 option already specified in [RFC8115]. 158 2. Terminology 160 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 161 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 162 "OPTIONAL" in this document are to be interpreted as described in 163 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, 164 as shown here. 166 The terms DS-Lite multicast Basic Bridging BroadBand element (mB4) 167 and the DS-Lite multicast Address Family Transition Router element 168 (mAFTR) are defined in [RFC8114] . 170 3. Configuration process with RADIUS 172 The Figure 1 below illustrates how the RADIUS and DHCPv6 protocols 173 co-operate to provide CE with softwire configuration information. 174 The BNG acts as a RADIUS client and a DHCPv6 server. 176 CE BNG AAA Server 177 | | | 178 |-------1.DHCPv6 Solicit-------> | | 179 | (ORO w/container option code) | | 180 | |-------2.Access-Request------->| 181 | | (S46-Configuration attribute | 182 | |and/or S46-Multicast attribute)| 183 | |<------3.Access-Accept---------| 184 |<---4.DHCPv6 Advertisement----- | (S46-Configuration attribute | 185 | (container option) |and/or S46-Multicast attribute)| 186 |-------5.DHCPv6 Request------> | | 187 | (container Option) | | 188 |<------6.DHCPv6 Reply---------- | | 189 | (container option) | | 190 | | | 191 DHCPv6 RADIUS 193 Figure 1: the cooperation between DHCPv6 and RADIUS combined with 194 RADIUS authentication 196 1. For unicast, the CE initiates a DHCPv6 Solicit message that 197 includes an Option Request option(6) with the S46 Container option 198 codes as defined in[RFC7598]. As described in [RFC7598], 199 OPTION_S46_CONT_MAPE should be included for MAP-E, 200 OPTION_S46_CONT_MAPT for MAP-T, and OPTION_S46_CONT_LW for 201 Lightweight 4over6. For the multicast case, the the option number 202 for OPTION_V6_PREFIX64 (113) should be included in the client's ORO. 204 2. When the BNG receives the Solicit message, it SHOULD initiate a 205 RADIUS Access-Request message continaing: A User-Name attribute (1) 206 (with either a CE MAC address, interface-id or both), a User-password 207 attribute (2) (with a pre-configured shared password as defined in 208 [RFC2865], and the Softwire46-Configuration Attribute and/or 209 Softwire46-Multicast Attribute (as reuquested by the client). The 210 resulting message is sent to the RADIUS server. 212 3. If the authentication request is approved by the AAA server, and 213 suitable configuration is available, an Access-Accept message MUST be 214 acknowledged with the corresponding Softwire46-Configuration 215 Attribute or Softwire46-Multicast Attribute. 217 4. After receiving the Access-Accept message with the corresponding 218 Attribute, the BNG SHOULD respond to the DHCPv6 Client (CE) with an 219 Advertisement message. 221 5. On receipt of an Advertise message containing one or more of the 222 requested DHCPv6 softwire container options (94, 95, 96, or 113) the 223 CE MAY request configuration for the desired softwire mechanism(s) by 224 including the option code(s) in the ORO of the DHCPv6 Request 225 message. 227 6. When the BNG receives the client's DHCPv6 Request message, it 228 constructs a Reply message containing the softwire container options 229 enumerated in the ORO. The recommended format of the MAC address is 230 defined as Calling-Station-Id (Section 3.20 in [RFC3580] without the 231 SSID (Service Set Identifier) portion. It is for the IEEE 802.1X 232 Authenticators, the Calling-Station- Id attribute is used to store 233 the bridge or Access Point MAC address in ASCII format. 235 For Lightweight 4over6 [RFC7596], the subscriber's binding state 236 needs to be synchronized between the clients and the lwAFTR. This 237 can be achieved in two ways: pre-configuring the bindings statically 238 on both the AAA server and lwAFTR, or on-demand whereby the AAA 239 server updates the lwAFTR with the subscriber's binding state as it 240 is created or deleted. 242 The authorization operation could also be done independently after 243 the authentication process. In such a scenario, after the 244 authentication operation, the client MAY initiate a DHCPv6 Request 245 message that includes the corresponding S46 Container options. 246 Similar to the above scenario, the ORO with the corresponding S46 247 Container option code in the initial DHCPv6 request could be optional 248 if the network was planned as being S46-enabled by default. When the 249 BNG receives the DHCPv6 Request, it SHOULD initiate the RADIUS 250 Access-Request message, which MUST contain a Service-Type attribute 251 (6) with the value Authorize Only (17), the corresponding 252 Softwire46-Configuration Attribute, and a State attribute obtained 253 from the previous authentication process according to [RFC5080]. If 254 the authorization request is approved by an AAA server, an Access- 255 Accept message MUST be acknowledged with the corresponding 256 Softwire46-Configuration Attribute. The BNG SHOULD then send the 257 DHCPv6 Reply message containing the S46 Container option. 259 There are three notices need to be considered: 261 o In both the above-mentioned scenarios, Message-authenticator (type 262 80) [RFC2869] SHOULD be used to protect both Access-Request and 263 Access-Accept messages. 265 o If the BNG does not receive the corresponding 266 Softwire46-Configuration Attribute in the Access-Accept message it 267 MAY fallback to a pre-configured default S46 configuration, if 268 any. If the BNG does not have any pre-configured default S46 269 configuration, or if the BNG receives an Access-Reject, then S46 270 connection cannot be established. 272 o As specified in [RFC3315], section 18.1.4, "Creation and 273 Transmission of Rebind Messages ", if the DHCPv6 server to which 274 the DHCPv6 Renew message was sent at time T1 has not responded by 275 time T2, the CE (DHCPv6 client) SHOULD enter the Rebind state and 276 attempt to contact any available server. In this situation, the 277 secondary BNG receiving the DHCPv6 message MUST initiate a new 278 Access-Request message towards the AAA server. The secondary BNG 279 MAY include the Softwire46-Configuration Attribute in its Access- 280 Request message. 282 In both the above-mentioned scenarios, Message-authenticator (type 283 80) [RFC2869] SHOULD be used to protect both Access-Request and 284 Access-Accept messages. 286 If the BNG does not receive the corresponding 287 Softwire46-Configuration Attribute in the Access-Accept message it 288 MAY fallback to a pre-configured default S46 configuration, if any. 289 If the BNG does not have any pre-configured default S46 290 configuration, or if the BNG receives an Access-Reject, then S46 291 connection cannot be established. 293 As specified in [RFC3315], section 18.1.4, "Creation and Transmission 294 of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew 295 message was sent at time T1 has not responded by time T2, the CE 296 (DHCPv6 client) SHOULD enter the Rebind state and attempt to contact 297 any available server. In this situation, the secondary BNG receiving 298 the DHCPv6 message MUST initiate a new Access-Request message towards 299 the AAA server. The secondary BNG MAY include the 300 Softwire46-Configuration Attribute in its Access-Request message. 302 4. Attributes 304 This section defines the Softwire46-Configuration Attribute, 305 Softwire46-Priority Attribute, and Softwire46-Multicast Attribute. 306 The attribute design follows [RFC6158] and refers to [RFC6929]. 308 The Softwire46-Configuration Attribute carries the configuration 309 information for MAP-E, MAP-T, and Lightweight 4over6. The 310 configuration information for each S46 mechanism is carried in the 311 corresponding Softwire46 TLVs. Different Sub TLVs are required for 312 each type of Softwire46 TLVs. The RADIUS attribute for Dual-Stack 313 Lite [RFC6333] is defined in [RFC6519]. 315 A client may be capable of supporting several different S46 316 mechanisms. Depending on the deployment scenario, a client might 317 request for more than one S46 mechanism at a time. The 318 Softwire46-Priority Attribute contains information allowing the 319 client to prioritize which mechanism to use, corresponding to 320 OPTION_S46_PRIORITY defined in [RFC8026]. 322 The Softwire46-Multicast Attirbute conveys the IPv6 prefixes to be 323 used in [RFC8114] to synthesize IPv4-embedded IPv6 addresses. The 324 BNG SHALL use the IPv6 prefixes returned in the RADIUS 325 Softwire46-Multicast Attirbute to populate the DHCPv6 PREFIX64 Option 326 [RFC8115]. 328 4.1. Softwire46-Configuration Attribute 330 This attribute is of type "tlv" as defined in the RADIUS Protocol 331 Extensions [RFC6929]. It contains some sub-attributes, and the 332 requirements are as follows: 334 The Softwire46-Configuration Attribute MAY contain the S46-MAP-E TLV 335 (see Section 4.2). 337 The Softwire46-Configuration Attribute MAY contain the S46-MAP-T TLV 338 (see Section 4.2). 340 The Softwire46-Configuration Attribute MAY contain the S46- 341 Lightweight-4over6 TLV (see Section 4.2). 343 The Softwire46-Configuration Attribute MUST contain at least one 344 Softwire46 TLV in the attribute. 346 The Softwire46-Configuration Attribute conveys the configuration 347 information for MAP-E, MAP-T, and Lightweight 4over6. The BNG SHALL 348 use the configuration information returned in the RADIUS Attribute to 349 populate the DHCPv6 Softwire46 Container Option defined in section 5 350 of [RFC7598]. 352 The Softwire46-Configuration Attribute MAY appear in an Access-Accept 353 packet. It MAY also appear in an Access-Request packet. 355 The Softwire46-Configuration Attribute MAY appear in a CoA-Request 356 packet. 358 The Softwire46-Configuration Attribute MAY appear in an Accounting- 359 Request packet. 361 The Softwire46-Configuration Attribute MUST NOT appear in any other 362 RADIUS packet. 364 The Softwire46-Configuration Attribute can only encapsulate 365 Softwire46 TLV. The Softwire46-Configuration Attribute is structured 366 as follows: 368 0 1 2 3 369 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 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | Type | Length | Extended-Type | Value ... 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 Type 374 241 (To be confirmed by IANA). 375 Length 376 This field indicates the total length in bytes of all fields of 377 this attribute, including the Type, Length, Extended-Type, and the 378 entire length of the embedded TLVs. 379 Extended-Type 380 TBD1 381 Value 382 This field contains a set of TLVs as follows: 383 S46-MAP-E TLV 384 This TLV contains the S46-Rule Sub TLV, S46-BR Sub TLV, 385 S46-PORTPARAMS Sub TLV. Refer to Section 4.4. 386 S46-MAP-T TLV 387 This TLV contains the S46-Rule Sub TLV, S46-DMR Sub TLV, 388 S46-PORTPARAMS Sub TLV. Refer to Section 4.4. 389 S46-Lightweight-4over6 TLV 390 This TLV contains the S46-BR Sub TLV,S46-V4V6Bind Sub 391 TLV, S46-PORTPARAMS TLV. Refer to Section 4.4. 393 Softwire46-Configuration Attribute is associated with the following 394 identifier: 241.Extended-Type(TBD1). 396 4.2. Softwire46 TLVs 398 The Softwire46 TLV can only be encapsulated in the 399 Softwire46-Configuration Attribute. Depending on the deployment 400 scenario, a client might request for more than one transition 401 mechanism at a time, there MUST be at least one Softwire46 TLV 402 encapsulated in one Softwire46-Configuration Attribute. There MUST 403 be at most one instance of each type of Softwire46 TLV encapsulated 404 in one Softwire46-Configuration Attribute. 406 There are three types of Softwire46 TLV, namely S46-MAP-E TLV, 407 S46-MAP-T TLV, S46-Lightweight 4over6 TLV. Each type of Softwire46 408 TLV contains a number of sub TLVs, defined in Section 4.4. The 409 hierarchy of the Softwire46 TLV is shown in Figure 2. Section 4.3 410 describes which Sub TLVs are mandatory, optional, or not permitted 411 for each defined Softwire46 TLV. 413 / 414 / | 1.Rule-IPv6-Prefix 415 | | Sub-TLV 416 | 1.S46-Rule Sub TLV-----+ 2.Rule-IPv4-Prefix 417 S46-MAP-E TLV | | Sub-TLV 418 | 2.S46-BR Sub TLV | 3.EA Length Sub- 419 S46-MAP-T TLV---------+ 3.S46-DMR Sub TLV \ TLV 420 | 421 S46-Lightweight | /1.IPv4-address 422 -4over6 TLV | | Sub-TLV 423 | 4.S46-v4v6Bind Sub TLV --| 2.Bind-IPv6-Prefix 424 | \ Sub-TLV 425 | /1.PSID-offset 426 | | Sub-TLV 427 | 5.S46-PORTPARAMS Sub TLV --| 2.PSID-len 428 | | Sub-TLV 429 \ \3.PSID Sub- 430 TLV 432 Figure 2: Softwire46 TLVs Hierarchy 434 The format of S46-MAP-E TLV is shown as below: 436 0 1 2 3 437 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 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | TLV-Type | TLV-Length | TLV-Value ... 440 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 441 TLV-Type 442 TBD2 443 TLV-Length 444 The TLV-Length field is one octet and indicates the length of this 445 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 446 TLV-Value 447 This field contains a set of TLVs as follows: 448 It MUST contain the S46-Rule Sub TLV, defined in Section 4.4.1 449 It MUST contain the S46-BR Sub TLV, defined in Section 4.4.2 450 It MAY contain the S46-PORTPARAMS Sub TLV, defined in Section 4.4.5 452 The format of S46-MAP-T TLV is shown as below: 454 0 1 2 3 455 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 456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | TLV-Type | TLV-Length | TLV-Value ... 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 TLV-Type 460 TBD3 461 TLV-Length 462 The TLV-Length field is one octet and indicates the length of this 463 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 464 TLV-Value 465 This field contains a set of TLVs as follows: 466 It MUST contain the S46-Rule Sub TLV, defined in Section 4.4.1 467 It MUST contain the S46-DMR Sub TLV, defined in Section 4.4.3 468 It MAY contain the S46-PORTPARAMS Sub TLV, defined in Section 4.4.5 470 The format of S46-Lightweight 4over6 TLV is shown as below: 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 | TLV-Type | TLV-Length | TLV-Value ... 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 TLV-Type 478 TBD4 479 TLV-Length 480 The TLV-Length field is one octet and indicates the length of this 481 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 482 TLV-Value 483 This field contains a set of TLVs as follows: 484 It MUST contain the S46-BR Sub TLV, defined in Section 4.4.2 485 It MAY contain the S46-V4V6Bind Sub TLV, defined in Section 4.4.4 486 It MAY contain the S46-PORTPARAMS Sub TLV, defined in Section 4.4.5 488 4.3. Softwire46 Sub TLVs 490 The table below shows which encapsulated Sub TLVs are mandatory, 491 optional, or not permitted for each defined Softwire46 TLV. 493 +----------------+-------+-------+--------------------+ 494 | Sub TLV | MAP-E | MAP-T | Lightweight 4over6 | 495 +----------------+-------+-------+--------------------+ 496 | S46-BR | M | N/P | M | 497 +----------------+-------+-------+--------------------+ 498 | S46-Rule | M | M | N/P | 499 +----------------+-------+-------+--------------------+ 500 | S46-DMR | N/P | M | N/P | 501 +----------------+-------+-------+--------------------+ 502 | S46-V4V6Bind | N/P | N/P | O | 503 +----------------+-------+-------+--------------------+ 504 | S46-PORTPARAMS | O | O | O | 505 +----------------+-------+-------+--------------------+ 507 M - Mandatory, O - Optional, N/P - Not Permitted 509 According to the table described above, the Fig.2 had beed structured 510 into Figure 3, Figure 4 and Figure 5: 512 / (Mandatory) /1.Rule-IPv6-Prefix 513 | | sub-TLV 514 | 1.S46-Rule ------------+ 2.Rule-IPv4-Prefix 515 | Sub TLV | sub-TLV 516 | | 3.EA-Length 517 S46-MAP-E TLV--------+ \ sub-TLV 518 | 2.S46-BR Sub TLV 519 - - - - - - - - - - - - - - - - - - - - - - - - - 520 | (Optional) /1.PSID-offset 521 | | sub-TLV 522 | 3.S46-PORTPARAMS -------+ 2.PSID-len 523 | Sub TLV | sub-TLV 524 | | 3.PSID 525 \ \ sub-TLV 527 Figure 3: S46-MAP-E TLV Hierarchy 528 / (Mandatory) /1.Rule-IPv6-Prefix 529 | | sub-TLV 530 | 1.S46-Rule ------------+ 2.Rule-IPv4-Prefix 531 | Sub TLV | sub-TLV 532 | | 3.EA-Length 533 S46-MAP-T TLV--------+ \ sub-TLV 534 | 2.S46-DMR Sub TLV 535 - - - - - - - - - - - - - - - - - - - - - - - - - 536 | (Optional) /1.PSID-offset 537 | | sub-TLV 538 | 3.S46-PORTPARAMS -------+ 2.PSID-len 539 | Sub TLV | sub-TLV 540 | | 3.PSID 541 \ \ sub-TLV 543 Figure 4: S46-MAP-T TLV Hierarchy 545 / (Mandatory) 546 | 547 | 1.S46-BR Sub TLV 548 - - - - - - - - - - - - - - - - - - - - - - - - - 549 | (Optional) 550 S46-Lightweight ---+ /1.IPv4-address 551 --4over6 TLV | | sub-TLV 552 | 2.S46-v4v6Bind Sub TLV --| 2.Bind-IPv6-Prefix 553 | \ sub-TLV 554 | /1.PSID-offset 555 | | sub-TLV 556 | 3.S46-PORTPARAMS -------+ 2.PSID-len 557 | Sub TLV | sub-TLV 558 | | 3.PSID-sub-TLV 559 \ \ 561 Figure 5: S46-Lightweight 4over6 TLV Hierarchy 563 4.4. The format of Softwire46 Sub TLVs 565 4.4.1. S46-Rule Sub TLV 567 The S46-Rule Sub TLV can only be encapsulated in the S46-MAP-E TLV or 568 the S46-MAP-T TLV. Depending on deployment scenario, one Basic 569 Mapping Rule and zero or more Forwarding Mapping Rules MUST be 570 included in one S46-MAP-E TLV or S46-MAP-T TLV. 572 Each type of S46-Rule Sub TLV also contains a number of sub-TLVs, 573 including Rule-IPv6-Prefix sub-TLV, Rule-IPv4-Prefix sub-TLV, and EA- 574 Length sub-TLV. The structure of the sub-TLVs for S46-Rule Sub TLV 575 is defined in section 4.5. 577 0 1 2 3 578 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 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | TLV-Type | TLV-Length | TLV-Value ... 581 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 582 TLV-Type 583 1 Basic Mapping Rule (Not Forwarding Mapping Rule) 584 2 Forwarding Mapping Rule (Not Basic Mapping Rule) 585 3 Basic & Forwarding Mapping Rule 586 TLV-Length 587 The TLV-Length field is one octet and indicates the length of this 588 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 589 TLV-Value 590 This field contains a set of TLVs as follows: 591 Rule-IPv6-Prefix sub-TLV 592 This TLV contains an IPv6 prefix that appears in a MAP rule. 593 Refer to Section 4.5.1. 594 Rule-IPv4-Prefix sub-TLV 595 This TLV contains an IPv4 prefix that appears in a MAP rule. 596 Refer to Section 4.5.2. 597 EA-Length sub-TLV 598 This TLV contains the information of Embedded-Address(EA) 599 bit length. Refer to Section 4.5.3. 601 4.4.2. S46-BR Sub TLV 603 The S46-BR Sub TLV can only be encapsulated in the S46-MAP-E TLV or 604 S46-Lightweight 4over6 TLV. There MUST be at least one S46-BR Sub 605 TLV included in each S46-MAP-E TLV or S46-Lightweight--4over6 TLV. 607 0 1 2 3 608 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 609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 610 | TLV-Type | TLV-Length | | 611 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 612 | | 613 | BR-ipv6-address | 614 | | 615 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 616 | | 617 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 618 TLV-Type 619 4 620 TLV-Length 621 18 octets 622 BR-ipv6-address 623 IPv6 address. A fixed-length field of 16 octets that specifies 624 the IPv6 address for the S46 BR. 626 4.4.3. S46-DMR Sub TLV 628 The S46-DMR Sub TLV can only appear in the S46-MAP-T TLV. There MUST 629 be exactly one S46-DMR Sub TLV included in one S46-MAP-T TLV. 631 0 1 2 3 632 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 633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 634 | TLV-Type | TLV-Length | Reserved |dmr-prefix6-len| 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 | dmr-ipv6-prefix | 637 | (variable length) | 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 640 TLV-Type 641 5 642 TLV-Type 643 4 + length of dmr-ipv6-prefix specified in octets 644 Reserved 645 This field is reserved. It should be set to all zeros. 646 dmr-prefix6-len 647 An 8 bits long field that expresses the bitmask length of 648 the IPv6 prefix specified in the dmr-ipv6-prefix field. 649 Allowed values range from 0 to 96. 650 dmr-ipv6-prefix 651 IPv6 Prefix. A variable-length field specifying the IPv6 652 prefix or address for the BR. This field is right-padded 653 with zeros to the nearest octet boundary when 654 dmr-prefix6-len is not divisible by 8. 656 4.4.4. S46-V4V6Bind Sub TLV 658 The S46-V4V6Bind Sub TLV can only be encapsulated in the S46- 659 Lightweight-4over6 TLV. There MUST be exactly one S46-V4V6Bind Sub 660 TLV included in each S46-Lightweight-4over6 TLV. 662 0 1 2 3 663 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 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 665 | TLV-Type | TLV-Length | TLV-Value ... 666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 667 TLV-Type 668 6 669 TLV-Length 670 The TLV-Length field is one octet and indicates the length of this 671 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 672 TLV-Value 673 This field contains a set of TLVs as follows: 674 IPv4-address sub-TLV 675 This TLV contains an IPv4 address that MAY be used to 676 specify the full or shared IPv4 address of the CE. 677 Refer to Section 4.6.1. 678 Bind-IPv6-Prefix sub-TLV 679 This TLV contains the IPv6 prefix or address for the S46 CE. 680 Refer to Section 4.6.2. 682 4.4.5. S46-PORTPARAMS Sub TLV 684 The S46-PORTPARAMS Sub TLV specifies optional port set information 685 that MAY be provided to CEs. The S46-PORTPARAMS Sub TLV can be 686 included optionally by each type of Softwire46 TLVs . 688 0 1 2 3 689 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 690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 691 | TLV-Type | TLV-Length | TLV-Value ... 692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 TLV-Type 694 7 695 TLV-Length 696 The TLV-Length field is one octet and indicates the length of this 697 TLV, including the TLV-Type, TLV-Length, and TLV-Value fields. 698 TLV-Value 699 This field contains a set of TLVs as follows: 700 PSID-offset sub-TLV 701 This TLV pecifies the numeric value for the S46 algorithm's 702 excluded port range/offset bits (a bits). 703 Refer to Section 4.7.1. 704 PSID-len sub-TLV 705 This TLV specifies the number of significant bits in the 706 PSID field (also known as 'k'). 707 Refer to Section 4.7.2. 708 PSID sub-TLV 709 This TLV specifies PSID value. 710 Refer to Section 4.7.3. 712 4.5. Sub-TLVs for S46-Rule Sub TLV 714 There are three types of S46-Rule sub-TLVs, namely Basic Mapping 715 Rule, Forwarding Mapping Rule, Basic and Forwarding Mapping Rule. 716 Each type of S46-Rule Sub TLV also contains a number of sub-TLVs. 717 The Rule-IPv6-Prefix sub-TLV is necessary for every type of S46-Rule 718 Sub TLV. It should appear for once and only once. 720 4.5.1. Rule-IPv6-Prefix sub-TLV 722 The Rule-IPv6-Prefix sub-TLV is necessary for every S46-Rule Sub TLV. 723 There MUST be exactly one Rule-IPv6-Prefix sub-TLV encapsulated in 724 each type of S46-Rule Sub TLV. 726 The Rule-IPv6-Prefix sub-TLV follows the framed IPv6 prefix designed 727 in [RFC3162] and [RFC8044]. 729 0 1 2 3 730 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 731 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 732 | TLV-Type | TLV-Length | Reserved |ruleprefix6-len| 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 734 | | 735 | rule-ipv6-prefix | 736 | | 737 | | 738 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 739 TLV-Type 740 8 741 TLV-Length 742 20 743 Reserved 744 This field is reserved. It is always set to zero. This field 745 is one octet in length. 746 Ruleprefix6-len 747 The length of IPv6 prefix, specified in the rule-ipv6-prefix 748 field, expressed in bits. 749 rule-ipv6-prefix 750 IPv6 Prefix. A 128 bits long field that specifies an IPv6 751 prefix that appears in a MAP rule. 753 4.5.2. Rule-IPv4-Prefix Sub-TLV 755 0 1 2 3 756 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 757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 758 | TLV-Type | TLV-Length | Reserved |ruleprefix4-len| 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 760 | rule-ipv4-prefix | 761 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 762 TLV-Type 763 9 764 TLV-Length 765 8 766 Reserved 767 This field is reserved. It is always set to zero. This field 768 is one octet in length. 769 Ruleprefix4-len 770 The length of IPv4 prefix, specified in the rule-ipv4-prefix 771 field, expressed in bits. 772 rule-ipv4-prefix 773 IPv4 Prefix. A 32 bits long field that specifies an IPv4 774 prefix that appears in a MAP rule. 776 4.5.3. EA-Length Sub-TLV 778 0 1 2 3 779 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 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 781 | TLV-Type | TLV-Length | EA-len | 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 TLV-Type 784 10 785 TLV-Length 786 4 787 EA-len 788 Integer. A 16 bits long field that specifies the 789 Embedded-Address(EA) bit length. Allowed values range 790 from 0 to 48. 792 4.6. Sub-TLVs for S46-v4v6Bind Sub TLV 794 4.6.1. The IPv4-address sub-TLV 796 The IPv4-address sub-TLV MAY be used to specify the full or shared 797 IPv4 address of the CE. 799 0 1 2 3 800 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 801 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 802 | TLV-Type | TLV-Length | ipv4-address | 803 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 804 | ipv4-address | 805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 TLV-Type 807 11 808 TLV-Length 809 6 810 ipv4-address 811 IPv4 address. A 32 bits long field that specifies an IPv4 812 address that appears in the V4V6Bind Option. 814 4.6.2. The Bind-IPv6-Prefix Sub-TLV 816 The bind-ipv6-prefix field specified in this field is used by the CE 817 to identify the correct prefix to be used for the tunnel source. 819 0 1 2 3 820 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 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | TLV-Type | TLV-Length | Reserved |bindprefix6-len| 823 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 824 | | 825 | bind-ipv6-prefix | 826 | (variable length) | 827 | | 828 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 829 TLV-Type 830 12 831 TLV-Length 832 20 833 Reserved 834 This field is reserved. It is always set to zero. This field 835 is one octet in length. 836 bindprefix6-len 837 Integer. An 8 bits long field that expresses the bitmask 838 length of the IPv6 prefix specified in the bind-ipv6-prefix 839 field. Allowed values range from 0 to 96. 840 bind-ipv6-prefix 841 IPv6 prefix. A variable-length field specifying the IPv6 842 prefix or address for the S46 CE. This field is right-padded 843 with zeros to the nearest octet boundary when bindprefix6-len 844 is not divisible by 8. 846 4.7. Sub-TLVs for S46-PORTPARAMS Sub TLV 848 4.7.1. The PSID-offset sub-TLV 850 0 1 2 851 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 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 853 | TLV-Type | TLV-Length | PSID-Offset | 854 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 855 TLV-Type 856 13 857 TLV-Length 858 3 859 PSID-Offset 860 Integer. An 8 bits long field that specifies the 861 numeric value for the S46 algorithm's excluded 862 port range/offset bits (a bits), as per Section 5.1 863 of RFC7597. Allowed values are between 0 and 15. 864 Default values for this field are specific to the 865 Softwire mechanism being implemented and are defined 866 in the relevant specification document. 868 4.7.2. The PSID-len sub-TLV 870 0 1 2 871 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 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | TLV-Type | TLV-Length | PSID-len | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 TLV-Type 876 14 877 TLV-Length 878 3 879 PSID-len 880 Integer. An 8 bits long field that specifies the 881 number of significant bits in the PSID field (also 882 known as 'k'). When set to 0, the PSID field is to 883 be ignored. After the first 'a' bits, there are k 884 bits in the port number representing the value of 885 the PSID. Subsequently, the address sharing ratio 886 would be 2 ^k. 888 4.7.3. The PSID sub-TLV 890 0 1 2 3 891 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 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 893 | TLV-Type | TLV-Length | PSID | 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 TLV-Type 896 15 897 TLV-Length 898 4 (the length of the PSID Sub Option) 899 PSID (Port-set ID) 900 Integer. An explicit 16-bit (unsigned word) PSID value. 901 The PSID value algorithmically identifies a set of ports 902 assigned to a CE. The first k bits on the left of this 903 2-octet field is the PSID value. The remaining (16-k) bits 904 on the right are padding zeros. 906 4.8. Softwire46-Priority Attribute 908 The Softwire46-Priority Attribute defines a 16-bit S46-option-code 909 field to contain the information allowing the client to prioritize 910 which mechanism to use, corresponding to OPTION_S46_PRIORITY defined 911 in [RFC8026]. 913 The Softwire46-Priority Attribute MAY appear in an Access-Accept 914 packet. It MAY also appear in an Access-Request packet. 916 The Softwire46-Priority Attribute MAY appear in a CoA-Request packet. 918 The Softwire46-Priority Attribute MAY appear in an Accounting-Request 919 packet. 921 The Softwire46-Priority Attribute MUST NOT appear in any other RADIUS 922 packet. 924 The S46-Priority Attribute is structured as follows: 926 0 1 2 3 927 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 928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 929 | Type | Length | Extended-Type | ... 930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 ... S46-option-code | S46-option-code | 932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 934 Type 935 241 (To be confirmed by IANA) 936 Length 937 This field indicates the total length in bytes of all fields 938 of this attribute, including the Type, Length, Extended-Type, 939 and the entire length of the S46-option-code. 940 Extended-Type 941 TBD5 942 S46-option-code 943 Integer. A 16-bit IANA-registered option code of the 944 DHCPv6 option that is used to identify the softwire 945 mechanisms. Refer to section 5 of RFC7598. S46 mechanisms are 946 prioritized in the appearance order of the 947 S46-option-code(s) in the Softwire46-Priority Attribute. 948 A Softwire46-Priority Attribute MUST contain at least one 949 S46-option-code. The option codes of the corresponding 950 S46 mechanisms are listed in Section 6.3. 952 Softwire46-Priority Attribute is associated with the following 953 identifier: 241.Extended-Type(TBD5). 955 4.9. Softwire46-Multicast Attribute 957 The Softwire46-Multicast attribute conveys the IPv6 prefixes to be 958 used to synthesize IPv4-embedded IPv6 addresses as per [RFC8114]. 959 The BNG SHALL use the IPv6 prefixes returned in the RADIUS 960 Softwire46-Multicast attribute to populate the DHCPv6 PREFIX64 Option 961 [RFC8115]. 963 This attribute MAY be used in Access-Request packets as a hint to the 964 RADIUS server. For example, if the BNG is pre-configured with 965 Softwire46-Multicast, these prefixes MAY be inserted in the 966 attribute. The RADIUS server MAY ignore the hint sent by the BNG, 967 and it MAY assign a different Softwire46-Multicast attribute. 969 The Softwire46-Multicast Attribute MAY appear in an Access-Accept 970 packet. It MAY also appear in an Access-Request packet. 972 The Softwire46-Multicast Attribute MAY appear in a CoA-Request 973 packet. 975 The Softwire46-Multicast Attribute MAY appear in an Accounting- 976 Request packet. 978 The Softwire46-Multicast Attribute MUST NOT appear in any other 979 RADIUS packet. 981 This attribute is of type "TLV" as defined in the RADIUS Protocol 982 Extensions [RFC6929]. It contains some sub-attributes: 984 o The Softwire46-Multicast Attribute MAY contain the ASM-Prefix64 985 TLV (see Section 4.9.1). 987 o The Softwire46-Multicast Attribute MAY contain the SSM-Prefix64 988 TLV (see Section 4.9.2). 990 o The Softwire46-Multicast Attribute MAY contain the U-Prefix64 TLV 991 (see Section 4.9.3). 993 The Softwire46-Multicast Attribute MUST include the ASM-Prefix64 TLV 994 or the SSM-Prefix64 TLV, and it MAY include both. 996 The U-Prefix64 TLV MUST be present when the SSM-Prefix64 TLV is 997 present. The U-Prefix64 TLV MAY be present when the ASM-Prefix64 TLV 998 is present. 1000 The format of the Softwire46-Multicast Attribute is shown in 1001 Figure 6. 1003 0 1 2 3 1004 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 1005 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1006 | Type | Length | Extended-Type | Value ... 1007 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1009 Figure 6 1011 Type 1013 241 (To be confirmed by IANA). 1015 Length 1017 This field indicates the total length in bytes of all fields of 1018 this attribute, including the Type, Length, Extended-Type, and the 1019 entire length of the embedded TLVs. 1021 Extended-Type 1023 TBD6. 1025 Value 1027 This field contains a set of TLVs as follows: 1029 ASM-Prefix64 TLV 1031 This TLV contains the ASM IPv6 prefix. Refer to Section 4.9.1. 1033 SSM-Prefix64 TLV 1035 This TLV contains the SSM IPv6 prefix. Refer to Section 4.9.2. 1037 U-Prefix64 TLV 1039 This TLV contains the IPv4 prefix used for address translation 1040 [RFC6052]. Refer to Section 4.9.3. 1042 Softwire46-Multicast Attribute is associated with the following 1043 identifier: 241.Extended-Type(TBD6). 1045 4.9.1. ASM-Prefix64 TLV 1047 The format of ASM-Prefix64 TLV is shown in Figure 7. 1049 0 1 2 3 1050 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 1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 | TLV-Type | Reserved | Prefix-Length |ASM Prefix64 ... 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 ... ASM Prefix64 ... 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 ... ASM Prefix64 ... 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 ... ASM Prefix64 | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 Figure 7 1063 TLV-Type 1065 16 1067 Reserved 1069 This field is reserved. It is always set to zero. This field is 1070 one octet in length. 1072 Prefix-Length 1074 The length of the prefix, in bits. 1076 ASM Prefix64 1078 IPv6 prefix. This field specifies the IPv6 multicast prefix to be 1079 used to synthesize the IPv4-embedded IPv6 addresses of the 1080 multicast groups in the ASM mode. The conveyed multicast IPv6 1081 prefix MUST belong to the ASM range. 1083 4.9.2. SSM-Prefix64 TLV 1085 The format of SSM-Prefix64 TLV is shown in Figure 8. 1087 0 1 2 3 1088 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 1089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1090 | TLV-Type | Reserved |Prefix-Length | SSM Prefix64 ... 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1092 ... SSM Prefix64 ... 1093 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1094 ... SSM Prefix64 ... 1095 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1096 ... SSM Prefix64 | 1097 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1099 Figure 8 1101 TLV-Type 1103 17 1105 Reserved 1107 This field is reserved. It is always set to zero. This field is 1108 one octet in length. 1110 Prefix-Length 1112 The length of the prefix, in bits. 1114 SSM Prefix64 1116 IPv6 prefix. This field specifies the IPv6 multicast prefix to be 1117 used to synthesize the IPv4-embedded IPv6 addresses of the 1118 multicast groups in the SSM mode. The conveyed multicast IPv6 1119 prefix MUST belong to the SSM range. 1121 4.9.3. U-Prefix64 TLV 1123 The format of U-Prefix64 TLV is shown in Figure 9. 1125 0 1 2 3 1126 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 1127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1128 | TLV-Type | Reserved | Prefix-Length |Unicast Prefix64 1129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1130 ... Unicast Prefix64 ... 1131 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1132 ... Unicast Prefix64 ... 1133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1134 ... Unicast Prefix64 | 1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1137 Figure 9 1139 TLV-Type 1141 18 1143 Reserved 1145 This field is reserved. It is always set to zero. This field is 1146 one octet in length. 1148 Prefix-Length 1150 The length of the prefix, in bits. 1152 Unicast Prefix64 1154 IPv6 prefix. This field identifies the IPv6 unicast prefix to be 1155 used in SSM mode for constructing the IPv4-embedded IPv6 addresses 1156 representing the IPv4 multicast sources in the IPv6 domain. It 1157 may also be used to extract the IPv4 address from the received 1158 multicast data flows. 1160 4.10. Table of attributes 1162 This document proposes three new RADIUS attributes, and their formats 1163 are as follows: 1165 o Softwire46-Configuration Attribute: 241.TB1 1167 o Softwire46-Priority Attribute: 241.TB5 1169 o Softwire46-Multicast Attribute: 241.TB6 1171 The following table describes which attributes may be found, in which 1172 kinds of packets and in what quantity. 1174 Request Accept Reject Challenge Accounting # Attribute 1175 Request 1176 0-1 0-1 0 0 0-1 241.TBD1 Softwire46- 1177 Configuration 1178 0-1 0-1 0 0 0-1 241.TBD5 Softwire46- 1179 Priority 1180 0-1 0-1 0 0 0-1 241.TBD6 Softwire46- 1181 Multicast 1183 The following table defines the meaning of the above table entries. 1185 0 This attribute MUST NOT be present in packet. 1186 0+ Zero or more instances of this attribute MAY be present in 1187 packet. 1188 0-1 Zero or one instance of this attribute MAY be present in 1189 packet. 1190 1 Exactly one instance of this attribute MUST be present in 1191 packet. 1193 5. Diameter Considerations 1195 S46 Configuration using Diameter [RFC6733] is specified in [RFC7678]. 1197 6. IANA Considerations 1199 For this document, IANA has made new code point assignments for 1200 RADIUS attributes as described in the following subsections. 1202 6.1. New RADIUS Attributes 1204 The Attribute Types defined in this document have been registered by 1205 IANA from the RADIUS namespace as described in the "IANA 1206 Considerations" section of [RFC3575], in accordance with BCP 26 1207 [RFC5226]. For RADIUS packets, attributes, and registries created by 1208 this document, IANA has placed them at 1209 . 1211 In particular, this document defines three new RADIUS attributes, as 1212 follows, from the Short Extended Space of 1213 [RFC6929].Softwire46-Configuration Attribute, Softwire46-Priority 1214 Attribute, and Softwire46-Multicast Attribute 1216 Type Description Data Type Reference 1217 ---- ----------- --------- --------- 1218 241.TB1 Softwire46-Configuration tlv Section 4.1 1219 241.TB5 Softwire46-Priority integer Section 4.8 1220 241.TB6 Softwire46-Multicast tlv Section 4.9 1222 6.2. New RADIUS TLVs 1224 IANA has created a new registry called "RADIUS Softwire46 1225 Configuration and Multicast TLVs". All TLVs in this registry have 1226 one or more parent RADIUS attributes in nesting (refer to 1227 [RFC6929]]). This registry contains the following TLVs: 1229 Value Description Data Type Reference 1230 ----- ----------- --------- --------- 1231 0 Reserved 1232 TB2 S46-MAP-E tlv Section 4.2 1233 TB3 S46-MAP-T tlv Section 4.2 1234 TB4 S46-Lightweight 4over6 tlv Section 4.2 1235 1 S46-Rule tlv Section 4.4.1 1236 2 S46-Rule tlv Section 4.4.1 1237 3 S46-Rule tlv Section 4.4.1 1238 4 S46-BR ipv6addr Section 4.4.2 1239 5 S46-DMR ipv6prefix Section 4.4.3 1240 6 S46-V4V6Bind tlv Section 4.4.4 1241 7 S46-PORTPARAMS tlv Section 4.4.5 1242 8 Rule-IPv6-Prefix ipv6prefix Section 4.5.1 1243 9 Rule-IPv4-Prefix ipv4prefix Section 4.5.2 1244 10 EA-Length integer Section 4.5.3 1245 11 IPv4-address ipv4addr Section 4.6.1 1246 12 Bind-IPv6-Prefix ipv6prefix Section 4.6.2 1247 13 PSID-offset integer Section 4.7.1 1248 14 PSID-len integer Section 4.7.2 1249 15 PSID integer Section 4.7.3 1250 16 ASM-Prefix64 ipv6prefix Section 4.9.1 1251 17 SSM-Prefix64 ipv6prefix Section 4.9.2 1252 18 U-Prefix64 ipv6prefix Section 4.9.3 1253 19-255 Unassigned, TB2,TB3,TB4 will be assigned by IANA 1255 The registration procedure for this registry is Standards Action as 1256 defined in [RFC5226]. 1258 6.3. S46 Mechanisms and Their Identifying Option Codes 1260 The Softwire46-Priority Attribute defines a 16-bit S46-option-code 1261 field, for which IANA is to create and maintain a new registry 1262 entitled "Option Codes Permitted in the Softwire46-Priority 1263 Attribute". This document requires IANA to register three option 1264 codes of the Softwire46 mechanisms permitted to be included in the 1265 Softwire46-Priority Attribute. The value of option code is 1266 corresponding to the TLV-Type defined in the Section 4.2. Additional 1267 options may be added to this list in the future using the IETF Review 1268 process described in Section 4.1 of [RFC5226]. 1270 The following table shows the option codes that are required and the 1271 S46 mechanisms that they represent. The option code for DS-Lite is 1272 derived from the IANA allocated RADIUS Attribute Type value for DS- 1273 Lite [RFC6519]. The option codes for MAP-E, MAP-T and Lightweight 1274 4over6 need to be determined. The option codes for MAP-E, MAP-T, and 1275 Lightweight 4over6 should also be used as the TLV-Type values for the 1276 MAP-E, MAP-T, and Lightweight 4over6 TLV defined in Section 4.2. 1278 +-------------+------------------+-----------+ 1279 | Option Code | S46 Mechanism | Reference | 1280 +-------------+------------------+-----------+ 1281 | TBD2 | MAP-E | RFC7597 | 1282 +-------------+------------------+-----------+ 1283 | TBD3 | MAP-T | RFC7599 | 1284 +-------------+------------------+-----------+ 1285 | TBD4 |Lightweight 4over6| RFC7596 | 1286 +-------------+------------------+-----------+ 1287 | 144 | DS-Lite | RFC6519 | 1288 +--------------------------------+-----------+ 1290 Table 1: Option Codes to S46 Mechanisms 1292 7. Security Considerations 1294 Known security vulnerabilities of the RADIUS protocol are discussed 1295 in [RFC2607], [RFC2865], and[RFC2869]. Use of IPsec [RFC4301] for 1296 providing security when RADIUS is carried in IPv6 is discussed in 1297 [RFC3162]. 1299 Specific security considerations for interactions between the MAP CE 1300 and the BNG are discussed in [RFC7597] and [RFC7599]. Security 1301 considerations for Lightweight 4over6 are discussed in [RFC7596]. 1302 Security considerations for DHCPv6-Based S46 Prioritization Mechanism 1303 are discussed in [RFC8026]. Security considerations for multicast 1304 scenarios are discussed in [RFC 8114]. Furthermore, generic DHCPv6 1305 security mechanisms can be applied to DHCPv6 intercommunication 1306 between the CE and the BNG. 1308 Security considerations for the Diameter protocol are discussed in 1309 [RFC6733]. 1311 8. Acknowledgements 1313 The authors would like to thank the valuable comments made by Peter 1314 Lothberg, Wojciech Dec, Ian Farrer, Suresh Krishnan, Qian Wang, Wei 1315 Meng and Cui Wang for this document. This document was merged with 1316 draft-sun-softwire-lw4over6-radext-01 and draft-wang-radext- 1317 multicast-radius-ext-00, thanks to everyone who contributed to this 1318 draft. 1320 This document was produced using the xml2rfc tool [RFC7991]. 1322 9. References 1324 9.1. Normative References 1326 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1327 Requirement Levels", BCP 14, RFC 2119, 1328 DOI 10.17487/RFC2119, March 1997, 1329 . 1331 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 1332 "Remote Authentication Dial In User Service (RADIUS)", 1333 RFC 2865, DOI 10.17487/RFC2865, June 2000, 1334 . 1336 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", 1337 RFC 3162, DOI 10.17487/RFC3162, August 2001, 1338 . 1340 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 1341 C., and M. Carney, "Dynamic Host Configuration Protocol 1342 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 1343 2003, . 1345 [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote 1346 Authentication Dial In User Service)", RFC 3575, 1347 DOI 10.17487/RFC3575, July 2003, 1348 . 1350 [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication 1351 Dial In User Service (RADIUS) Implementation Issues and 1352 Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December 1353 2007, . 1355 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1356 IANA Considerations Section in RFCs", RFC 5226, 1357 DOI 10.17487/RFC5226, May 2008, 1358 . 1360 [RFC6052] Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. 1361 Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, 1362 DOI 10.17487/RFC6052, October 2010, 1363 . 1365 [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines", 1366 BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011, 1367 . 1369 [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User 1370 Service (RADIUS) Protocol Extensions", RFC 6929, 1371 DOI 10.17487/RFC6929, April 2013, 1372 . 1374 [RFC8026] Boucadair, M. and I. Farrer, "Unified IPv4-in-IPv6 1375 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based 1376 Prioritization Mechanism", RFC 8026, DOI 10.17487/RFC8026, 1377 November 2016, . 1379 [RFC8044] DeKok, A., "Data Types in RADIUS", RFC 8044, 1380 DOI 10.17487/RFC8044, January 2017, 1381 . 1383 [RFC8114] Boucadair, M., Qin, C., Jacquenet, C., Lee, Y., and Q. 1384 Wang, "Delivery of IPv4 Multicast Services to IPv4 Clients 1385 over an IPv6 Multicast Network", RFC 8114, 1386 DOI 10.17487/RFC8114, March 2017, 1387 . 1389 [RFC8115] Boucadair, M., Qin, J., Tsou, T., and X. Deng, "DHCPv6 1390 Option for IPv4-Embedded Multicast and Unicast IPv6 1391 Prefixes", RFC 8115, DOI 10.17487/RFC8115, March 2017, 1392 . 1394 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1395 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1396 May 2017, . 1398 9.2. Informative References 1400 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 1401 Implementation in Roaming", RFC 2607, 1402 DOI 10.17487/RFC2607, June 1999, 1403 . 1405 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 1406 Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000, 1407 . 1409 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, 1410 "IEEE 802.1X Remote Authentication Dial In User Service 1411 (RADIUS) Usage Guidelines", RFC 3580, 1412 DOI 10.17487/RFC3580, September 2003, 1413 . 1415 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 1416 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 1417 December 2005, . 1419 [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 1420 Stack Lite Broadband Deployments Following IPv4 1421 Exhaustion", RFC 6333, DOI 10.17487/RFC6333, August 2011, 1422 . 1424 [RFC6346] Bush, R., Ed., "The Address plus Port (A+P) Approach to 1425 the IPv4 Address Shortage", RFC 6346, 1426 DOI 10.17487/RFC6346, August 2011, 1427 . 1429 [RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual- 1430 Stack Lite", RFC 6519, DOI 10.17487/RFC6519, February 1431 2012, . 1433 [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, 1434 Ed., "Diameter Base Protocol", RFC 6733, 1435 DOI 10.17487/RFC6733, October 2012, 1436 . 1438 [RFC7596] Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I. 1439 Farrer, "Lightweight 4over6: An Extension to the Dual- 1440 Stack Lite Architecture", RFC 7596, DOI 10.17487/RFC7596, 1441 July 2015, . 1443 [RFC7597] Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S., 1444 Murakami, T., and T. Taylor, Ed., "Mapping of Address and 1445 Port with Encapsulation (MAP-E)", RFC 7597, 1446 DOI 10.17487/RFC7597, July 2015, 1447 . 1449 [RFC7598] Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, 1450 W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for 1451 Configuration of Softwire Address and Port-Mapped 1452 Clients", RFC 7598, DOI 10.17487/RFC7598, July 2015, 1453 . 1455 [RFC7599] Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S., 1456 and T. Murakami, "Mapping of Address and Port using 1457 Translation (MAP-T)", RFC 7599, DOI 10.17487/RFC7599, July 1458 2015, . 1460 [RFC7678] Zhou, C., Taylor, T., Sun, Q., and M. Boucadair, 1461 "Attribute-Value Pairs for Provisioning Customer Equipment 1462 Supporting IPv4-Over-IPv6 Transitional Solutions", 1463 RFC 7678, DOI 10.17487/RFC7678, October 2015, 1464 . 1466 [RFC7991] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary", 1467 RFC 7991, DOI 10.17487/RFC7991, December 2016, 1468 . 1470 Additional Authors 1471 Qiong Sun 1472 China Telecom 1473 Beijing China 1474 Email: sunqiong@ctbri.com.cn 1476 Qi Sun 1477 Tsinghua University 1478 Department of Computer Science, Tsinghua University 1479 Beijing 100084 1480 P.R.China 1481 Phone: +86-10-6278-5822 1482 Email: sunqibupt@gmail.com 1484 Cathy Zhou 1485 Huawei Technologies 1486 Bantian, Longgang District 1487 Shenzhen 518129 1488 Email: cathy.zhou@huawei.com 1490 Tina Tsou 1491 Huawei Technologies(USA) 1492 2330 Central Expressway 1493 Santa Clara, CA 95050 1494 USA 1495 Email: Tina.Tsou.Zouting@huawei.com 1497 ZiLong Liu 1498 Tsinghua University 1499 Beijing 100084 1500 P.R.China 1501 Phone: +86-10-6278-5822 1502 Email: liuzilong8266@126.com 1504 Yong Cui 1505 Tsinghua University 1506 Beijing 100084 1507 P.R.China 1508 Phone: +86-10-62603059 1509 Email: yong@csnet1.cs.tsinghua.edu.cn 1511 Authors' Addresses 1512 Sheng Jiang 1513 Huawei Technologies Co., Ltd 1514 Q14, Huawei Campus, No.156 Beiqing Road 1515 Hai-Dian District, Beijing, 100095 1516 P.R. China 1518 Email: jiangsheng@huawei.com 1520 Yu Fu 1521 CNNIC 1522 No.4 South 4th Street, Zhongguancun 1523 Hai-Dian District, Beijing, 100190 1524 P.R. China 1526 Email: fuyu@cnnic.cn 1528 Bing Liu 1529 Huawei Technologies Co., Ltd 1530 Q14, Huawei Campus, No.156 Beiqing Road 1531 Hai-Dian District, Beijing, 100095 1532 P.R. China 1534 Email: leo.liubing@huawei.com 1536 Peter Deacon 1537 IEA Software, Inc. 1538 P.O. Box 1170 1539 Veradale, WA 99037 1540 USA 1542 Email: peterd@iea-software.com 1544 Chongfeng Xie 1545 China Telecom 1546 Beijing 1547 P.R. China 1549 Email: xiechf.bri@chinatelecom.cn 1550 Tianxiang Li 1551 Tsinghua University 1552 Beijing 100084 1553 P.R.China 1555 Email: peter416733@gmail.com 1557 Mohamed Boucadair 1558 Orange 1559 Rennes, 35000 1560 France 1562 Email: mohamed.boucadair@orange.com