idnits 2.17.1 draft-ietf-softwire-dslite-radius-ext-02.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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 4, 2011) is 4794 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) == Outdated reference: A later version (-16) exists of draft-ietf-radext-ipv6-access-03 == Outdated reference: A later version (-10) exists of draft-ietf-softwire-ds-lite-tunnel-option-09 == Outdated reference: A later version (-11) exists of draft-ietf-softwire-dual-stack-lite-07 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 softwire R. Maglione 3 Internet-Draft Telecom Italia 4 Intended status: Standards Track A. Durand 5 Expires: September 5, 2011 Juniper Networks 6 March 4, 2011 8 RADIUS Extensions for Dual-Stack Lite 9 draft-ietf-softwire-dslite-radius-ext-02 11 Abstract 13 Dual-Stack Lite is a solution to offer both IPv4 and IPv6 14 connectivity to customers which are addressed only with an IPv6 15 prefix. DS-Lite requires to pre-configure the AFTR tunnel 16 information on the B4 element. In many networks, the customer 17 profile information may be stored in AAA servers while client 18 configurations are mainly provided through DHC protocol. This 19 document specifies one new RADIUS attribute to carry Dual-Stack Lite 20 Address Family Transition Router (AFTR) name; the RADIUS attribute is 21 defined based on the equivalent DHCPv6 option already specified in 22 draft-ietf-softwire-ds-lite-tunnel-option. This RADIUS attribute is 23 meant to be used between the RADIUS Server and the NAS, it is not 24 intended to be used directly between the B4 element and the RADIUS 25 Server. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 5, 2011. 44 Copyright Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 This document may contain material from IETF Documents or IETF 60 Contributions published or made publicly available before November 61 10, 2008. The person(s) controlling the copyright in some of this 62 material may not have granted the IETF Trust the right to allow 63 modifications of such material outside the IETF Standards Process. 64 Without obtaining an adequate license from the person(s) controlling 65 the copyright in such materials, this document may not be modified 66 outside the IETF Standards Process, and derivative works of it may 67 not be created outside the IETF Standards Process, except to format 68 it for publication as an RFC or to translate it into languages other 69 than English. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 74 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 3. DS-Lite Configuration with RADIUS and DHCPv6 . . . . . . . . . 5 76 4. RADIUS Attribute . . . . . . . . . . . . . . . . . . . . . . . 7 77 4.1. DS-Lite-Tunnel-Name . . . . . . . . . . . . . . . . . . . . 7 78 5. Table of attributes . . . . . . . . . . . . . . . . . . . . . . 8 79 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 80 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9 81 8. Normative References . . . . . . . . . . . . . . . . . . . . . 9 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 84 1. Introduction 86 Dual-Stack Lite [I-D.ietf-softwire-dual-stack-lite] is a solution to 87 offer both IPv4 and IPv6 connectivity to customers which are 88 addressed only with an IPv6 prefix (no IPv4 address is assigned to 89 the attachment device). One of its key components is an IPv4-over- 90 IPv6 tunnel, but a DS-Lite Basic Bridging BroadBand (B4) will not 91 know if the network it is attached to offers Dual-Stack Lite support, 92 and if it did, would not know the remote end of the tunnel to 93 establish a connection. 95 To inform the B4 of the AFTR's location, a Fully Qualified Domain 96 Name (FQDN) may be used. Once this information is conveyed, the 97 presence of the configuration indicating the AFTR's location also 98 informs a host to initiate Dual-Stack Lite (DS-Lite) service and 99 become a Softwire Initiator. 101 The draft draft-ietf-softwire-ds-lite-tunnel-option 102 [I-D.ietf-softwire-ds-lite-tunnel-option] specifies a DHCPv6 option 103 which is meant to be used by a Dual-Stack Lite client (Basic Bridging 104 BroadBand element, B4) to discover its Address Family Transition 105 Router (AFTR) name. In order to be able to populate such option the 106 DHCPv6 Server must be pre-provisioned with the Address Family 107 Transition Router (AFTR) name. 109 In Broadband environments, customer profile may be managed by AAA 110 servers, together with user Authentication, Authorization, and 111 Accounting (AAA). RADIUS protocol [RFC2865] is usually used by AAA 112 Servers to communicate with network elements. 113 [I-D.ietf-radext-ipv6-access] describes a typical broadband network 114 scenario in which the Network Access Server (NAS) acts as the access 115 gateway for the users (hosts or CPEs) and the NAS embeds a DHCPv6 116 Server function that allows it to locally handle any DHCPv6 requests 117 issued by the clients. 119 Since the DS-Lite AFTR information can be stored in AAA servers and 120 the client configuration is mainly provided through DHC protocol 121 running between the NAS and the requesting clients, a new RADIUS 122 attribute is needed to send AFTR information from AAA server to the 123 NAS. 125 This document aims at defining a new RADIUS attribute to be used for 126 carrying the DS-Lite Tunnel Name, based on the equivalent DHCPv6 127 option already specified in [I-D.ietf-softwire-ds-lite-tunnel-option] 129 2. Terminology 131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 133 document are to be interpreted as described in [RFC2119]. 135 The terms DS-Lite Basic Bridging BroadBand element (B4) and the DS- 136 Lite Address Family Transition Router element (AFTR) are defined in 137 [I-D.ietf-softwire-dual-stack-lite] 139 3. DS-Lite Configuration with RADIUS and DHCPv6 141 The Figure 1 illustrates how the RADIUS protocol and DHCPv6 work 142 together to accomplish DS-Lite configuration on the B4 element when a 143 PPP Session is used to provide connectivity to the user. 145 The Network Access Server (NAS) operates as a client of RADIUS and as 146 DHCP Server for DHC protocol. The NAS initially sends a RADIUS 147 Access Request message to the RADIUS server, requesting 148 authentication. Once the RADIUS server receives the request, it 149 validates the sending client and if the request is approved, the AAA 150 server replies with an Access Accept message including a list of 151 attribute-value pairs that describe the parameters to be used for 152 this session. This list may also contain the AFTR Tunnel Name. When 153 the NAS receives a DHCPv6 client request containing the DS-Lite 154 tunnel Option, the NAS shall use the address returned in the RADIUS 155 DS-Lite-Tunnel-Addr attribute to populate the DHCPv6 156 OPTION_DS_LITE_ADDR option in the DHCPv6 reply message. 158 B4 NAS AAA 159 | | Server 160 | | | 161 |----PPP LCP Config Request------> | | 162 | | | 163 | |----Access-Request ---->| 164 | | | 165 | |<---- Access-Accept-----| 166 | | (DS-Lite-Tunnel-Name) | 167 |<-----PPP LCP Config ACK ----- | | 168 | | | 169 | | | 170 |------ PPP IPv6CP Config Req ---->| | 171 | | | 172 |<----- PPP IPv6CP Config ACK -----| | 173 | | | 174 |------- DHCPv6 Solicit -------->| | 175 | | | 176 |<-------DHCPv6 Advertisement -----| | 177 | (DHCPv6 OPTION_DS_LITE_NAME) | | 178 | | | 179 |------- DHCPv6 Request -------->| | 180 | | | 181 |<-------- DHCPv6 Reply --------- | | 182 | (DHCPv6 OPTION_DS_LITE_NAME) | | 184 DHCPv6 RADIUS 186 Figure 1: RADIUS and DHCPv6 Message Flow for a PPP Session 188 The Figure 2 illustrates how the RADIUS protocol and DHCPv6 work 189 together to accomplish DS-Lite configuration on the B4 element when 190 an IP Session is used to provide connectivity to the user. 192 The only difference between this message flow and previous one is 193 that in this scenario the interaction between NAS and AAA/ RADIUS 194 Server is triggered by the DHCPv6 Solicit message received by the NAS 195 from the B4 acting as DHCPv6 client, while in case of a PPP Session 196 the trigger is the PPP LCP Config Request message received by the 197 NAS. 199 B4 NAS AAA 200 | | Server 201 |------ DHCPv6 Solicit ---------> | | 202 | | | 203 | |----Access-Request ---->| 204 | | | 205 | |<-Access-Accept---------| 206 | | (DS-Lite-Tunnel-Name) | 207 | | | 208 |<-------DHCPv6 Advertisement------| | 209 | (DHCPv6 OPTION_DS_LITE_NAME) | | 210 | | | 211 |------- DHCPv6 Request -------->| | 212 | | | 213 | | | 214 | <---- DHCPv6 Reply ---- | | 215 | (DHCPv6 OPTION_DS_LITE_NAME) | | 217 DHCPv6 RADIUS 219 Figure 2: RADIUS and DHCPv6 Message Flow for an IP Session 221 4. RADIUS Attribute 223 This section specifies the format of the new RADIUS attribute. 225 4.1. DS-Lite-Tunnel-Name 227 Description 229 The DS-Lite-Tunnel-Name RADIUS attribute contains a Fully Qualified 230 Domain Name that refers to the AFTR the client is requested to 231 establish a connection with. The NAS shall use the name returned in 232 the RADIUS DS-Lite-Tunnel-Name attribute to populate the DHCPv6 233 OPTION_DS_LITE_NAME option [I-D.ietf-softwire-ds-lite-tunnel-option] 235 This attribute MAY be used in Access-Accept packets and it MAY be 236 present in Accounting-Request records where the Acct-Status-Type is 237 set to Start, Stop or Interim-Update. The DS-Lite-Tunnel-Name RADIUS 238 attribute and MUST NOT appear more than once in a message. 240 A summary of the DS-Lite-Tunnel-Name RADIUS attribute format is shown 241 below. The fields are transmitted from left to right. 243 0 1 2 3 244 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 245 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 | Type | Length | DS-Lite-Tunnel-Name (FQDN) | 247 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 248 | DS-Lite-Tunnel-Name (FQDN) (cont) | 249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 Type: 253 TBA1 for DS-Lite-Tunnel-Name. 254 Length: 255 This field indicates the total length in octets of this 256 attribute including the Type, the Length fields and the length 257 in octets of the DS-Lite-Tunnel-Name field 259 DS-Lite-Tunnel-Name: 260 A single Fully Qualified Domain Name of the remote tunnel 261 endpoint, located at the DS-Lite AFTR. 263 5. Table of attributes 265 The following table provides a guide to which attributes may be found 266 in which kinds of packets, and in what quantity. 268 Request Accept Reject Challenge Accounting # Attribute 269 Request 270 0-1 0-1 0 0 0-1 TBA1 DS-Lite-Tunnel-Name 272 The following table defines the meaning of the above table entries. 274 0 This attribute MUST NOT be present in packet. 275 0+ Zero or more instances of this attribute MAY be present in 276 packet. 277 0-1 Zero or one instance of this attribute MAY be present in packet. 279 6. Security Considerations 281 This document has no additional security considerations beyond those 282 already identified in [RFC2865] 284 [I-D.ietf-softwire-dual-stack-lite] discusses DS-Lite related 285 security issues. 287 7. IANA Considerations 289 This document requests the allocation of a new Radius attribute types 290 from the IANA registry "Radius Attribute Types" located at 291 http://www.iana.org/assignments/radius-types 293 DS-Lite-Tunnel-Name - TBA1 295 8. Normative References 297 [I-D.ietf-radext-ipv6-access] 298 Lourdelet, B., Dec, W., Sarikaya, B., Zorn, G., and D. 299 Miles, "RADIUS attributes for IPv6 Access Networks", 300 draft-ietf-radext-ipv6-access-03 (work in progress), 301 January 2011. 303 [I-D.ietf-softwire-ds-lite-tunnel-option] 304 Hankins, D. and T. Mrugalski, "Dynamic Host Configuration 305 Protocol for IPv6 (DHCPv6) Option for Dual- Stack Lite", 306 draft-ietf-softwire-ds-lite-tunnel-option-09 (work in 307 progress), March 2011. 309 [I-D.ietf-softwire-dual-stack-lite] 310 Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- 311 Stack Lite Broadband Deployments Following IPv4 312 Exhaustion", draft-ietf-softwire-dual-stack-lite-07 (work 313 in progress), March 2011. 315 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 316 Requirement Levels", BCP 14, RFC 2119, March 1997. 318 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 319 "Remote Authentication Dial In User Service (RADIUS)", 320 RFC 2865, June 2000. 322 Authors' Addresses 324 Roberta Maglione 325 Telecom Italia 326 Via Reiss Romoli 274 327 Torino 10148 328 Italy 330 Phone: 331 Email: roberta.maglione@telecomitalia.it 332 Alain Durand 333 Juniper Networks 334 1194 North Mathilda Avenue 335 Sunnyvale, CA 94089-1206 336 USA 338 Phone: 339 Fax: 340 Email: adurand@juniper.net 341 URI: