idnits 2.17.1 draft-guo-radext-softwire-concentrator-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 05, 2010) is 5044 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 3588 (Obsoleted by RFC 6733) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Dayong Guo 2 Internet Draft Sheng Jiang 3 Intended status: Standards Track Huawei Technologies Co., Ltd 4 Expires: January 07, 2011 July 05, 2010 6 RADIUS Attribute for Softwire Concentrator in IPv6 Transition 8 draft-guo-radext-softwire-concentrator-00.txt 10 Status of this Memo 12 This Internet-Draft is submitted in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF). Note that other groups may also distribute working 17 documents as Internet-Drafts. The list of current Internet-Drafts is 18 at http://datatracker.ietf.org/drafts/current/. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 This Internet-Draft will expire on January 07, 2011. 27 Copyright Notice 29 Copyright (c) 2010 IETF Trust and the persons identified as the 30 document authors. All rights reserved. 32 This document is subject to BCP 78 and the IETF Trust's Legal 33 Provisions Relating to IETF Documents 34 (http://trustee.ietf.org/license-info) in effect on the date of 35 publication of this document. Please review these documents 36 carefully, as they describe your rights and restrictions with respect 37 to this document. Code Components extracted from this document must 38 include Simplified BSD License text as described in Section 4.e of 39 the Trust Legal Provisions and are provided without warranty as 40 described in the Simplified BSD License. 42 Abstract 44 6rd and DS-Lite are two most popular methods to provide both IPv4 and 45 IPv6 connectivity services simultaneously during the IPv4/IPv6 co- 46 existing period. Both mechanisms need to configure the softwire 47 concentrator information on the host. In many networks, the 48 information may be stored in AAA servers while user configuration is 49 mainly through DHC protocol. This document defines several RADIUS 50 attributes that carries softwire concentrator information. 52 Table of Contents 54 1. Introduction.................................................3 55 2. Terminology..................................................3 56 3. Softwire Concentrator Configuration with RADIUS..............3 57 4. Attributes...................................................4 58 4.1. DS-Lite-Add Attribute...................................4 59 4.2. DS-Lite-Name Attribute..................................5 60 4.3. 6rd Attribute...........................................6 61 4.4. Table of attributes.....................................6 62 5. Diameter Considerations......................................7 63 6. Security Considerations......................................7 64 7. IANA Considerations..........................................7 65 8. Acknowledgments..............................................7 66 9. References...................................................8 67 9.1. Normative References....................................8 68 9.2. Informative References..................................8 70 1. Introduction 72 Recently providers start to deploy IPv6 and consider how to transit 73 to IPv6. 6rd [I-D.ietf-softwire-ipv6-6rd] and DS-Lite 74 [I-D.ietf-softwire-ds-lite] are two most popular methods to provide 75 both IPv4 and IPv6 connectivity services simultaneously during the 76 IPv4/IPv6 co-existing period. 6rd is used to provide IPv6 77 connectivity service through IPv4-only infrastructure while DS-Lite 78 is aiming to provide IPv4 connectivity service through IPv6-only 79 network. 81 Both 6rd and DS-Lite adopt DHCP as auto-configuring protocol. In DS- 82 lite, The DHCPv6 options are used to discover the IPv6 address or 83 name of the AFTR (i.e. softwire concentrator) 84 [I-D.ietf-softwire-ds-lite-tunnel-option]. Similarly the 6rd CPE 85 extends DHCP option to discover 6rd border relay (i.e. softwire 86 concentrator) and to configuring IPv6 address and prefix. 88 In many networks, user configuration information may be managed by 89 AAA servers, together with user Authentication, Authorization, and 90 Accounting (AAA). Current AAA servers communicate using the RADIUS 91 (Remote Authentication Dial In User Service, [RFC2865]) protocol. 92 [I-D.ietf-radext-ipv6-access] describes a fixed line broadband 93 network scenario in which the Broadband Network Gateways (BNGs) act 94 as the access gateway of users (hosts or CPEs). The BNGs are assumed 95 to embed a DHCPv6 server function that allows them to locally handle 96 any DHCPv6 requests issued by hosts. 98 Since the 6rd/DS-Lite softwire concentrator information is stored in 99 AAA servers and user configuration is mainly through DHC protocol 100 between BNGs and hosts. New RADIUS attributes are needed to propagate 101 these information from AAA servers to BNGs. 103 2. Terminology 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in RFC2119 [RFC2119]. 109 3. Softwire Concentrator Configuration with RADIUS 111 The below Figure 1 illustrates how the RADIUS protocol and DHCPv6 are 112 cooperated to provide users/hosts with DS-Lite configuration. 6rd has 113 the same operation. 115 User/host BNG AAA Server 116 | | | 117 |----------Solicit-------->| | 118 | |---Request (DS-Lite-Addr)--->| 119 | | | 120 | |<---Accept (DS-Lite-Addr)----| 121 |<--------Advertise--------| | 122 | | | 123 |----------Request-------->| | 124 | (DS-Lite tunnel Option) | | 125 |<----------Reply----------| | 126 | (DS-Lite tunnel option) | | 127 | | | 128 DHCPv6 RADIUS 129 Figure 1: the cooperation between DHCPv6 and RADIUS 131 BNGs act as a bridge between user and AAA server. First, a BNG 132 receives a user DHCPv6 solicit. It initiates the BNG to request 133 correspondent user authentication relevant from an AAA server using 134 RADIUS protocol. A DS-Lite-Addr request may be also sent in the same 135 message. If the user authentication is approved by the AAA server, an 136 Accept message is acknowledged with the DS-Lite-Addr attribute, 137 defined in the next Section. After the BNG responds to the user with 138 an Advertise message, the user requests for a DS-Lite tunnel Option. 139 Then, the BNG can reply the user using DHCPv6 protocol. 141 4. Attributes 143 This section defines three RADIUS attributes that carries softwire 144 concentrator information. DS-Lite-Addr Attribute and DS-Lite-Name 145 Attribute can be used in DS-Lite scenario independently. 6rd 146 Attribute should be used in the 6rd scenario. 148 4.1. DS-Lite-Add Attribute 150 The DS-Lite-Add Attribute is structured as follows: 152 0 1 2 3 153 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 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Type | Length | | 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 157 | | 158 | DS-Lite tunnel-endpoint-addr (IPv6 Address) | 159 | | 160 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 Type TBD1 166 Length 18 168 DS-Lite tunnel-endpoint-addr The address of DS-Lite is used to 169 establish tunnel. In the DS-Lite scenarios the 170 Address Family Transition Router element (AFTR) is 171 an IPv6 address. 173 4.2. DS-Lite-Name Attribute 175 The DS-Lite-Name Attribute is structured as follows: 177 0 1 2 3 178 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 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | Type | Length | | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 182 | | 183 | Name of DS-Lite tunnel-endpoint (FQDN) | 184 | | 185 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 186 | | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 Type TBD2 191 Length The length of the entire attribute, in bytes. 193 Name of DS-Lite tunnel-endpoint The Fully Qualified Domain 194 Name of softwire concentrator. In the DS-Lite 195 scenarios, it is the domain name of Address Family 196 Transition Router element (AFTR). 198 4.3. 6rd Attribute 200 The 6rd Attribute is structured as follows: 202 0 1 2 3 203 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 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | Type | Length | IPv4MaskLen | 6rdPrefixLen | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | | 208 | 6rdPrefix | 209 | | 210 | | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | 6rdBRIPv4Address(es) | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 Type TBD3 217 Length the length of the DHCP option in octets (22 octets 218 with one BR IPv4 address). 220 IPv4MaskLen The number of high-order bits that are identical 221 across all CE IPv4 addresses within a given 6rd 222 domain. This may be any value between 0 and 32. 223 Any value greater than 32 is invalid. 225 6rdPrefixLen The IPv6 Prefix length of the Service Provider's 226 6rd IPv6 prefix in number of bits. The 227 6rdPrefixLen MUST be less than or equal to 128. 229 6rdPrefix The Service Provider's 6rd IPv6 prefix represented 230 as a 16 octet IPv6 address. The bits after the 231 6rdPrefixlen number of bits in the prefix SHOULD 232 be set to zero. 234 6rdBRIPv4Address One or more IPv4 addresses of the 6rd Border 235 Relay(s) for a given 6rd domain. 237 4.4. Table of attributes 239 The following table provides a guide to which attributes may be found 240 in which kinds of packets, and in what quantity. 242 Request Accept Reject Challenge Accounting # Attribute 243 Request 244 0+ 0+ 0 0 0+ TBD1 DS-Lite-Addr 245 0+ 0+ 0 0 0+ TBD2 DS-Lite-Name 246 0+ 0+ 0 0 0+ TBD3 6rd 248 5. Diameter Considerations 250 This attribute is usable within either RADIUS or Diameter [RFC3588]. 251 Since the Attributes defined in this document will be allocated from 252 the standard RADIUS type space, no special handling is required by 253 Diameter entities. 255 6. Security Considerations 257 In DS-Lite scenarios, the RADIUS protocol is run over IPv6. In 6rd 258 scenarios, the RADIUS protocol is run over IPv4. Known security 259 vulnerabilities of the RADIUS protocol are discussed in RFC 2607 260 [RFC2607], RFC 2865 [RFC2865], and RFC 2869 [RFC2869]. Use of IPsec 261 [RFC4301] for providing security when RADIUS is carried in IPv6 is 262 discussed in RFC 3162 [RFC3162]. 264 Security considerations for the Diameter protocol are discussed in 265 RFC 3588 [RFC3588]. 267 7. IANA Considerations 269 This document requires the assignment of two new RADIUS Attribute 270 Types in the "Radius Types" registry (currently located at 271 http://www.iana.org/assignments/radius-types for the following 272 attributes: 274 o DS-Lite-Add 275 o DS-Lite-Name 276 o 6rd 278 IANA should allocate these numbers from the standard RADIUS 279 Attributes space using the "IETF Review" policy [RFC5226]. 281 8. Acknowledgments 283 The authors would like to thank Maglione Roberta, Telecom Italia, for 284 valuable comments. 286 9. Change Log [RFC Editor please remove] 288 draft-guo-radext-softwire-concentrator-00, original version, 2010-07- 289 05. 291 10. References 293 10.1. Normative References 295 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 296 Requirement Levels", BCP 14, RFC 2119, March 1997. 298 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 299 "Remote Authentication Dial In User Service (RADIUS)", RFC 300 2865, June 2000. 302 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 303 3162, August 2001. 305 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J., 306 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 308 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 309 Internet Protocol", RFC 4301, December 2005. 311 [RFC5226] T. Narten, H. Alvestrand, "Guidelines for Writing an IANA 312 Considerations Section in RFCs", RFC 5226, May 2008. 314 10.2. Informative References 316 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy 317 Implementation in Roaming", RFC 2607, June 1999. 319 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 320 Extensions", RFC 2869, June 2000. 322 [I-D.ietf-radext-ipv6-access] Lourdelet, B., et al., "RADIUS 323 attributes for IPv6 Access Networks", draft-ietf-radext- 324 ipv6-access, work in progress, April 2010. 326 [I-D.ietf-softwire-ds-lite] Durand A., et al., "Dual-stack lite 327 broadband deployments post IPv4 exhaustion", draft-ietf- 328 softwire-dual-stack-lite, work in progress, March 2010. 330 [I-D.ietf-softwire-ds-lite-tunnel-option] Hankins, D. and T. 331 Mrugalski, "Dynamic Host Configuration Protocol for IPv6 332 (DHCPv6) Options for Dual-Stack Lite", draft-ietf-softwire- 333 ds-lite-tunnel-option, work in progress, March 2010. 335 [I-D.ietf-softwire-ipv6-6rd] Townsley W., et al., "IPv6 via IPv4 336 Service Provider Networks (6rd)", draft-ietf-softwire-ipv6- 337 6rd, (work in progress), March 2010. 339 Author's Addresses 341 Dayong Guo 342 Huawei Technologies Co., Ltd 343 Huawei Building, No.3 Xinxi Rd., 344 Shang-Di Information Industry Base, Hai-Dian District, Beijing 100085 345 P.R. China 346 Email: guoseu@huawei.com 348 Sheng Jiang 349 Huawei Technologies Co., Ltd 350 Huawei Building, No.3 Xinxi Rd., 351 Shang-Di Information Industry Base, Hai-Dian District, Beijing 100085 352 P.R. China 353 Email: shengjiang@huawei.com