idnits 2.17.1 draft-ietf-softwire-map-radius-00.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 is 1 instance of too long lines in the document, the longest one being 1 character 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 26, 2013) is 3949 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: 'RFC3580' is mentioned on line 166, but not defined == Unused Reference: 'I-D.ietf-radext-radius-extensions' is defined on line 595, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2869 ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Sheng Jiang (Editor) 2 Internet Draft Yu Fu 3 Intended status: Standards Track Bing Liu 4 Expires: December 27, 2013 Huawei Technologies Co., Ltd 5 Peter Deacon 6 IEA Software, Inc. 7 June 26, 2013 9 RADIUS Attribute for MAP 11 draft-ietf-softwire-map-radius-00.txt 13 Status of this Memo 15 This Internet-Draft is submitted in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF). Note that other groups may also distribute working 20 documents as Internet-Drafts. The list of current Internet-Drafts is 21 at http://datatracker.ietf.org/drafts/current/. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 This Internet-Draft will expire on December 27, 2013. 30 Copyright Notice 32 Copyright (c) 2012 IETF Trust and the persons identified as the 33 document authors. All rights reserved. 35 This document is subject to BCP 78 and the IETF Trust's Legal 36 Provisions Relating to IETF Documents 37 (http://trustee.ietf.org/license-info) in effect on the date of 38 publication of this document. Please review these documents 39 carefully, as they describe your rights and restrictions with respect 40 to this document. Code Components extracted from this document must 41 include Simplified BSD License text as described in Section 4.e of 42 the Trust Legal Provisions and are provided without warranty as 43 described in the Simplified BSD License. 45 Abstract 47 Mapping of Address and Port (MAP) is a stateless mechanism for 48 running IPv4 over IPv6-only infrastructure. It provides both IPv4 and 49 IPv6 connectivity services simultaneously during the IPv4/IPv6 co- 50 existing period. The Dynamic Host Configuration Protocol for IPv6 51 (DHCPv6) MAP options has been defined to configure MAP Customer Edge 52 (CE). However, in many networks, the configuration information may be 53 stored in Authentication Authorization and Accounting (AAA) servers 54 while user configuration is mainly from Broadband Network Gateway 55 (BNG) through DHCPv6 protocol. This document defines a Remote 56 Authentication Dial In User Service (RADIUS) attribute that carries 57 MAP configuration information from AAA server to BNG. The MAP RADIUS 58 attribute are designed following the simplify principle. It provides 59 just enough information to form the correspondent DHCPv6 MAP option. 61 Table of Contents 63 1. Introduction ................................................. 3 64 2. Terminology .................................................. 3 65 3. MAP Configuration process with RADIUS ........................ 3 66 4. Attributes ................................................... 6 67 4.1. MAP-Configuration Attribute ............................. 6 68 4.2. MAP Rule Options ........................................ 6 69 4.3. Sub Options for MAP Rule Option ......................... 7 70 4.3.1. Rule-IPv6-Prefix Sub Option ........................ 7 71 4.3.2. Rule-IPv4-Prefix Sub Option ........................ 8 72 4.3.3. Encapsulation/Translation Flag Sub Option........... 9 73 4.3.4. PSID Sub Option ................................... 10 74 4.3.5. PSID Length Sub Option ............................ 10 75 4.3.6. PSID Offset Sub Option ............................ 11 76 4.4. Table of attributes .................................... 11 77 5. Diameter Considerations ..................................... 12 78 6. Security Considerations ..................................... 12 79 7. IANA Considerations ......................................... 12 80 8. Acknowledgments ............................................. 12 81 9. References .................................................. 13 82 9.1. Normative References ................................... 13 83 9.2. Informative References ................................. 14 85 1. Introduction 87 Recently providers start to deploy IPv6 and consider how to transit 88 to IPv6. Mapping of Address and Port (MAP) 89 [I-D.ietf-softwire-map] is a stateless mechanism for running IPv4 90 over IPv6-only infrastructure. It provides both IPv4 and IPv6 91 connectivity services simultaneously during the IPv4/IPv6 co-existing 92 period. MAP has adopted Dynamic Host Configuration Protocol for IPv6 93 (DHCPv6) [RFC3315] as auto-configuring protocol. The MAP Customer 94 Edge (CE) uses the DHCPv6 extension options 95 [I-D.mdt-softwire-map-dhcp-option] to discover MAP Border Relay (in 96 tunnel model only) and to configure relevant MAP rules. 98 In many networks, user configuration information may be managed by 99 AAA (Authentication, Authorization, and Accounting) servers. Current 100 AAA servers communicate using the Remote Authentication Dial In User 101 Service (RADIUS) [RFC2865] protocol. In a fixed line broadband 102 network, the Broadband Network Gateways (BNGs) act as the access 103 gateway of users. The BNGs are assumed to embed a DHCPv6 server 104 function that allows them to locally handle any DHCPv6 requests 105 initiated by hosts. 107 Since the MAP configuration information is stored in AAA servers and 108 user configuration is mainly through DHCPv6 protocol between BNGs and 109 hosts/CEs, new RADIUS attributes are needed to propagate the 110 information from AAA servers to BNGs. The MAP RADIUS attribute are 111 designed following the simplify principle, while providing enough 112 information to form the correspondent DHCPv6 MAP option. 113 [I-D.mdt-softwire-map-dhcp-option]. 115 2. Terminology 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in RFC2119 [RFC2119]. 121 The terms MAP CE and MAP Border Relay are defined in 122 [I-D.ietf-softwire-map]. 124 3. MAP Configuration process with RADIUS 126 The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 127 cooperate to provide MAP CE with MAP configuration information. 129 MAP CE BNG AAA Server 130 | | | 131 |------DHCPv6 Solicit----->| | 132 |(Option Request w/ MAP option) | 133 | |--Access-Request(MAP Attr)-->| 134 | | | 135 | |<--Access-Accept(MAP Attr)---| 136 |<---DHCPv6 Advertisement--| | 137 | | | 138 |------DHCPv6 Request---->| | 139 | (MAP Option) | | 140 |<---- -DHCPv6 Reply-------| | 141 | (MAP option) | | 142 | | | 143 DHCPv6 RADIUS 144 Figure 1: the cooperation between DHCPv6 and RADIUS 145 combining with RADIUS authentication 147 BNGs act as a RADIUS client and as a DHCPv6 server. First, the MAP CE 148 MAY initiate a DHCPv6 Solicit message that includes an Option Request 149 option (6) [RFC3315] with the MAP option 150 [draft-ietf-softwire-map-dhcp] from the MAP CE. But note that the ORO 151 (Option Request option) with the MAP option could be optional if the 152 network was planned as MAP-enabled as default. When BNG receives the 153 SOLICIT, it SHOULD initiates radius Access-Request message, in which 154 the User-Name attribute (1) SHOULD be filled by the MAP CE MAC 155 address, to the RADIUS server and the User-password attribute (2) 156 SHOULD be filled by the shared MAP password that has been 157 preconfigured on the DHCPv6 server, requesting authentication as 158 defined in [RFC2865] with MAP-Configuration attribute, defined in the 159 next Section. If the authentication request is approved by the AAA 160 server, an Access-Accept message MUST be acknowledged with the IPv6- 161 MAP-Configuration Attribute. After receiving the Access-Accept 162 message with MAP-Configuration Attribute, the BNG SHOULD respond the 163 user an Advertisement message. Then the user can requests for a MAP 164 Option, the BNG SHOULD reply the user with the message containing the 165 MAP option. The recommended format of the MAC address is as defined 166 in Calling-Station-Id (Section 3.20 in [RFC3580]) without the SSID 167 (Service Set Identifier) portion. 169 Figure 2 describes another scenario, in which the authorization 170 operation is not coupled with authentication. Authorization relevant 171 to MAP is done independently after the authentication process. As 172 similar to above scenario, the ORO with the MAP option in the initial 173 DHCPv6 request could be optional if the network was planned as MAP- 174 enabled as default. 176 MAP CE BNG AAA Server 177 | | | 178 |------DHCPv6 Request---->| | 179 |(Option Request w/ MAP option) | 180 | |--Access-Request(MAP Attr)-->| 181 | | | 182 | |<--Access-Accept(MAP Attr)---| 183 | | | 184 |<-----DHCPv6 Reply--------| | 185 | (MAP option) | | 186 | | | 187 DHCPv6 RADIUS 188 Figure 2: the cooperation between DHCPv6 and RADIUS 189 decoupled with RADIUS authentication 191 In the abovementioned scenario, the Access-Request packet SHOULD 192 contain a Service-Type attribute (6) with the value Authorize Only 193 (17); thus, according to [RFC5080], the Access-Request packet MUST 194 contain a State attribute that obtained from the previous 195 authentication process. 197 In both above-mentioned scenarios, Message-authenticator (type 80) 198 [RFC2869] SHOULD be used to protect both Access-Request and Access- 199 Accept messages. 201 After receiving the MAP-Configuration Attribute in the initial 202 Access-Accept, the BNG SHOULD store the received MAP configuration 203 parameters locally. When the MAP CE sends a DHCPv6 Request message to 204 request an extension of the lifetimes for the assigned address, the 205 BNG does not have to initiate a new Access-Request towards the AAA 206 server to request the MAP configuration parameters. The BNG could 207 retrieve the previously stored MAP configuration parameters and use 208 them in its reply. 210 If the BNG does not receive the MAP-Configuration Attribute in the 211 Access-Accept it MAY fallback to a pre-configured default MAP 212 configuration, if any. If the BNG does not have any pre-configured 213 default MAP configuration or if the BNG receives an Access-Reject, 214 the tunnel cannot be established. 216 As specified in [RFC3315], section 18.1.4, "Creation and Transmission 217 of Rebind Messages ", if the DHCPv6 server to which the DHCPv6 Renew 218 message was sent at time T1 has not responded by time T2, the MAP CE 219 (DHCPv6 client) SHOULD enters the Rebind state and attempt to contact 220 any available server. In this situation, the secondary BNG receiving 221 the DHCPv6 message MUST initiate a new Access-Request towards the AAA 222 server. The secondary BNG MAY include the MAP-Configuration Attribute 223 in its Access-Request. 225 4. Attributes 227 This section defines MAP-Rule Attribute which is used in the MAP 228 scenario. The attribute design follows [RFC6158] and referring to [I- 229 D.ietf-radext-radius-extensions]. 231 The MAP RADIUS attribute are designed following the simplify 232 principle. The sub options are organized into two categories: the 233 necessary and the optional. 235 4.1. MAP-Configuration Attribute 237 The MAP-Configuration Attribute is structured as follows: 239 0 1 2 3 240 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 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 | Type | Length | | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 244 | | 245 + MAP Rule Option(s) + 246 | | 247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 Type 251 TBD 253 Length 255 2 + the length of the Rule option(s) 257 MAP Rule Option (s) 259 A variable field that may contains one or more Rule option(s), 260 defined in Section 4.2. 262 4.2. MAP Rule Options 264 Depending on deployment scenario, one Default Mapping rule and zero 265 or more other type Mapping Rules MUST be included in one 266 MAP-Configuration Attribute. 268 0 1 2 3 269 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 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Type | Length | | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 273 | | 274 + Sub Options + 275 | | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 Type 280 1 Basic Mapping Rule (Not Forwarding Mapping Rule) 282 2 Forwarding Mapping Rule (Not Basic Mapping Rule) 284 3 Default Mapping Rule 286 4 Basic & Forwarding Mapping Rule 288 Length 290 2 + the length of the sub options 292 Sub Option 294 A variable field that contains necessary sub options defined in 295 Section 4.3 and zero or several optional sub options, defined 296 in Section 4.4. 298 4.3. Sub Options for MAP Rule Option 300 The sub options do not include EA-Len Embedded-Address length , 301 because it can be calculated by the combine of prefix4len, prefix6- 302 len, PSID and offset bits. 304 4.3.1. Rule-IPv6-Prefix Sub Option 306 The Rule-IPv6-Prefix Sub Option is necessary for every MAP Rule 307 option. It should appear for once and only once. 309 The IPv6 Prefix sub option is follow the framed IPv6 prefix designed 310 in [RFC3162]. 312 0 1 2 3 313 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 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 | SubType | SubLen | Reserved | prefix6-len | 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 | | 318 | rule-ipv6-prefix | 319 | | 320 | | 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 323 SubType 325 1 (SubType number, for the Rule-IPv6-Prefix6 sub option) 327 SubLen 329 20 (the length of the Rule-IPv6-Prefix6 sub option) 331 Reserved 333 Reserved for future usage. It should be set to all zero. 335 prefix6-len 337 length of the IPv6 prefix, specified in the rule-ipv6-prefix 338 field, expressed in bits 340 rule-ipv6-prefix 342 a 128-bits field that specifies an IPv6 prefix that appears in 343 a MAP rule 345 "For the encapsulation mode the Rule IPv6 prefix can be the full IPv6 346 address of the BR." [I-D.ietf-softwire-map] 348 4.3.2. Rule-IPv4-Prefix Sub Option 350 0 1 2 3 351 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 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | SubType | SubLen | Reserved | prefix4-len | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | rule-ipv4-prefix | 356 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 SubType 359 2 (SubType number, for the Rule-IPv4-Prefix6 sub option) 361 SubLen 363 8 (the length of the Rule-IPv4-Prefix6 sub option) 365 Reserved 367 Reserved for future usage. It should be set to all zero. 369 Prefix4-len 371 length of the IPv6 prefix, specified in the rule-ipv6-prefix 372 field, expressed in bits 374 rule-ipv4-prefix 376 a 32-bits field that specifies an IPv4 prefix that appears in 377 a MAP rule 379 4.3.3. Encapsulation/Translation Flag Sub Option 381 0 1 2 3 382 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 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 384 | SubType | SubLen | E/T Flag | 385 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 SubType 389 3 (SubType number, for the E/T flag sub option) 391 SubLen 393 4 (the length of the E/T flag sub option) 395 E/T Flag 397 indicate the MAP transport mode: encapsulation or translation. 398 all 0 for encapsulation, all 1 for translation. 400 If this sub option is not present, the default is to be assumed as 401 encapsulation mode. 403 4.3.4. PSID Sub Option 405 0 1 2 3 406 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 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 408 | SubType | SubLen | PSID | 409 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 SubType 413 4 (SubType number, for the PSID Sub Option sub option) 415 SubLen 417 4 (the length of the PSID Sub Option sub option) 419 PSID (Port-set ID) 420 Explicit 16-bit (unsigned word) PSID value. The PSID value 421 algorithmically identifies a set of ports assigned to a CE. The 422 first k-bits on the left of this 2-octets field is the PSID 423 value. The remaining (16-k) bits on the right are padding zeros. 425 4.3.5. PSID Length Sub Option 427 0 1 2 3 428 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 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 | SubType | SubLen | PSID-len | 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 433 SubType 435 5 (SubType number, for the PSID Length sub option) 437 SubLen 439 4 (the length of the PSID Length sub option) 441 PSID-len 443 Bit length value of the number of significant bits in the PSID 444 field. (also known as 'k'). When set to 0, the PSID field is to 445 be ignored. After the first 'a' bits, there are k bits in the 446 port number representing valid of PSID. Subsequently, the 447 address sharing ratio would be 2 ^k. 449 4.3.6. PSID Offset Sub Option 451 0 1 2 3 452 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 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | SubType | SubLen | PSID Offset | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 SubType 459 6 (SubType number, for the PSID Offset sub option) 461 SubLen 463 4 (the length of the PSID Offset sub option) 465 PSID Offset 467 4 bits long field that specifies the numeric value for the MAP 468 algorithm's excluded port range/offset bits (A-bits), as per 469 section 5.1.1 in [I-D.ietf-softwire-map]. Default must be set 470 to 4. 472 4.4. Table of attributes 474 The following table provides a guide to which attributes may be found 475 in which kinds of packets, and in what quantity. 477 Request Accept Reject Challenge Accounting # Attribute 478 Request 479 0-1 0-1 0 0 0-1 TBD1 MAP- 480 Configuration 481 0-1 0-1 0 0 0-1 1 User-Name 482 0-1 0 0 0 0 2 User-Password 483 0-1 0-1 0 0 0-1 6 Service-Type 484 0-1 0-1 0-1 0-1 0-1 80 Message-Authenticator 486 The following table defines the meaning of the above table entries. 488 0 This attribute MUST NOT be present in packet. 489 0+ Zero or more instances of this attribute MAY be present in 490 packet. 491 0-1 Zero or one instance of this attribute MAY be present in 492 packet. 493 1 Exactly one instance of this attribute MUST be present in 494 packet. 496 5. Diameter Considerations 498 This attribute is usable within either RADIUS or Diameter [RFC6733]. 499 Since the Attributes defined in this document will be allocated from 500 the standard RADIUS type space, no special handling is required by 501 Diameter entities. 503 6. Security Considerations 505 In MAP scenarios, both CE and BNG are within a provider network, 506 which can be considered as a closed network and a lower security 507 threat environment. A similar consideration can be applied to the 508 RADIUS message exchange between BNG and the AAA server. 510 Known security vulnerabilities of the RADIUS protocol are discussed 511 in [RFC2607], [RFC2865], and [RFC2869]. Use of IPsec [RFC4301] for 512 providing security when RADIUS is carried in IPv6 is discussed in 513 [RFC3162]. 515 A malicious user may use MAC address proofing and/or dictionary 516 attack on the shared MAP password that has been preconfigured on the 517 DHCPv6 server to get unauthorized MAP configuration information. 519 Security considerations for MAP specific between MAP CE and BNG are 520 discussed in [I-D.ietf-softwire-map]. Furthermore, generic DHCPv6 521 security mechanisms can be applied DHCPv6 intercommunication between 522 MAP CE and BNG. 524 Security considerations for the Diameter protocol are discussed in 525 [RFC6733]. 527 7. IANA Considerations 529 This document requires the assignment of two new RADIUS Attributes 530 Types in the "Radius Types" registry (currently located at 531 http://www.iana.org/assignments/radius-types for the following 532 attributes: 534 o MAP-Configuration TBD1 536 IANA should allocate the numbers from the standard RADIUS Attributes 537 space using the "IETF Review" policy [RFC5226]. 539 8. Acknowledgments 541 The authors would like to thank for valuable comments from Peter 542 Lothberg, Wojciech Dec, and Suresh Krishnan .etc. 544 9. References 546 9.1. Normative References 548 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 549 Requirement Levels", BCP 14, RFC 2119, March 1997. 551 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 552 "Remote Authentication Dial In User Service (RADIUS)", RFC 553 2865, June 2000. 555 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 556 Extensions", RFC 2869, June 2000. 558 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 559 3162, August 2001. 561 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and 562 M. Carney, "Dynamic Host Configuration Protocol for IPv6 563 (DHCPv6)", RFC 3315, July 2003. 565 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 566 Internet Protocol", RFC 4301, December 2005. 568 [RFC5080] Nelson, D. and DeKok A., "Common Remote Authentication Dial 569 In User Service (RADIUS) Implementation Issues and 570 Suggested Fixes", RFC 5080, December 2007. 572 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 573 IANA Considerations Section in RFCs", RFC 5226, May 2008. 575 [RFC6158] DeKok, A. and G. Weber, "RADIUS Design Guidelines", RFC 576 6158, March 2011. 578 [RFC6733] V. Fajardo, Ed., J. Arkko, J. Loughney, G. Zorn, Ed., 579 "Diameter Base Protocol", RFC 6733, October 2012. 581 [I-D.ietf-softwire-map] 582 O. Troan, et al., "Mapping of Address and Port (MAP)", 583 draft-ietf-softwire-map, working in progress. 585 [I-D.mdt-softwire-map-dhcp-option] 586 T. Mrugalski, et al., "DHCPv6 Options for Mapping of 587 Address and Port", draft-mdt-softwire-map-dhcp-option, 588 working in progress. 590 9.2. Informative References 592 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 593 Implementation in Roaming", RFC 2607, June 1999. 595 [I-D.ietf-radext-radius-extensions] 596 DeKok, A. and A. Lior, "Remote Authentication Dial In User 597 Service (RADIUS) Protocol Extensions", draft-ietf-radext- 598 radius-extensions, work in process. 600 Author's Addresses 602 Sheng Jiang 603 Huawei Technologies Co., Ltd 604 Huawei Building, 156 Beiqing Rd. 605 Hai-Dian District, Beijing 100095 606 P.R. China 607 Email: jiangsheng@huawei.com 609 Yu Fu 610 Huawei Technologies Co., Ltd 611 Huawei Building, 156 Beiqing Rd. 612 Hai-Dian District, Beijing 100095 613 P.R. China 614 Email: eleven.fuyu@huawei.com 616 Bing Liu 617 Huawei Technologies Co., Ltd 618 Huawei Building, 156 Beiqing Rd. 619 Hai-Dian District, Beijing 100095 620 P.R. China 621 Email: leo.liubing@huawei.com 623 Peter Deacon 624 IEA Software, Inc. 625 P.O. Box 1170 626 Veradale, WA 99037 627 USA 628 EMail: peterd@iea-software.com