draft-ietf-softwire-dslite-radius-ext-00.txt   draft-ietf-softwire-dslite-radius-ext-01.txt 
softwire R. Maglione softwire R. Maglione
Internet-Draft Telecom Italia Internet-Draft Telecom Italia
Intended status: Standards Track A. Durand Intended status: Standards Track A. Durand
Expires: April 15, 2011 Juniper Networks Expires: July 2, 2011 Juniper Networks
October 12, 2010 December 29, 2010
RADIUS Extensions for Dual-Stack Lite RADIUS Extensions for Dual-Stack Lite
draft-ietf-softwire-dslite-radius-ext-00 draft-ietf-softwire-dslite-radius-ext-01
Abstract Abstract
Dual-Stack Lite is a solution to offer both IPv4 and IPv6 Dual-Stack Lite is a solution to offer both IPv4 and IPv6
connectivity to customers which are addressed only with an IPv6 connectivity to customers which are addressed only with an IPv6
prefix. DS-Lite requires to pre-configure the AFTR tunnel prefix. DS-Lite requires to pre-configure the AFTR tunnel
information on the B4 element. In many networks, the customer information on the B4 element. In many networks, the customer
profile information may be stored in AAA servers while client profile information may be stored in AAA servers while client
configurations are mainly provided through DHC protocol. This configurations are mainly provided through DHC protocol. This
document specifies two new RADIUS attributes to carry Dual-Stack Lite document specifies one new RADIUS attribute to carry Dual-Stack Lite
Address Family Transition Router (AFTR) IPv6 address and name; the Address Family Transition Router (AFTR) name; the RADIUS attribute is
RADIUS attributes are defined based on the equivalent DHCPv6 options defined based on the equivalent DHCPv6 option already specified in
already specified in draft-ietf-softwire-ds-lite-tunnel-option. draft-ietf-softwire-ds-lite-tunnel-option. This RADIUS attribute is
These RADIUS attributes are meant to be used between the RADIUS meant to be used between the RADIUS Server and the NAS, it is not
Server and the NAS, they are not intended to be used directly between intended to be used directly between the B4 element and the RADIUS
the B4 element and the RADIUS Server. Server.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 15, 2011. This Internet-Draft will expire on July 2, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 10 skipping to change at page 3, line 10
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. DS-Lite Configuration with RADIUS and DHCPv6 . . . . . . . . . 5 3. DS-Lite Configuration with RADIUS and DHCPv6 . . . . . . . . . 5
4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. RADIUS Attribute . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. DS-Lite-Tunnel-Addr . . . . . . . . . . . . . . . . . . . . 6 4.1. DS-Lite-Tunnel-Name . . . . . . . . . . . . . . . . . . . . 7
4.2. DS-Lite-Tunnel-Name . . . . . . . . . . . . . . . . . . . . 6 5. Table of attributes . . . . . . . . . . . . . . . . . . . . . . 8
5. Table of attributes . . . . . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 9
8. Normative References . . . . . . . . . . . . . . . . . . . . . 8 8. Normative References . . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Dual-Stack Lite [I-D.ietf-softwire-dual-stack-lite] is a solution to Dual-Stack Lite [I-D.ietf-softwire-dual-stack-lite] is a solution to
offer both IPv4 and IPv6 connectivity to customers which are offer both IPv4 and IPv6 connectivity to customers which are
addressed only with an IPv6 prefix (no IPv4 address is assigned to addressed only with an IPv6 prefix (no IPv4 address is assigned to
the attachment device). One of its key components is an IPv4-over- the attachment device). One of its key components is an IPv4-over-
IPv6 tunnel, but a DS-Lite Basic Bridging BroadBand (B4) will not IPv6 tunnel, but a DS-Lite Basic Bridging BroadBand (B4) will not
know if the network it is attached to offers Dual-Stack Lite support, know if the network it is attached to offers Dual-Stack Lite support,
and if it did, would not know the remote end of the tunnel to and if it did, would not know the remote end of the tunnel to
establish a connection. establish a connection.
To inform the B4 of the AFTR's location, either an IPv6 address or To inform the B4 of the AFTR's location, a Fully Qualified Domain
Fully Qualified Domain Name (FQDN) may be used. Once this Name (FQDN) may be used. Once this information is conveyed, the
information is conveyed, the presence of the configuration indicating presence of the configuration indicating the AFTR's location also
the AFTR's location also informs a host to initiate Dual-Stack Lite informs a host to initiate Dual-Stack Lite (DS-Lite) service and
(DS-Lite) service and become a Softwire Initiator. become a Softwire Initiator.
The draft draft-ietf-softwire-ds-lite-tunnel-option The draft draft-ietf-softwire-ds-lite-tunnel-option
[I-D.ietf-softwire-ds-lite-tunnel-option] specifies two DHCPv6 [I-D.ietf-softwire-ds-lite-tunnel-option] specifies a DHCPv6 option
options which are meant to be used by a Dual-Stack Lite client (Basic which is meant to be used by a Dual-Stack Lite client (Basic Bridging
Bridging BroadBand element, B4) to discover its Address Family BroadBand element, B4) to discover its Address Family Transition
Transition Router (AFTR) address. In order to be able to populate Router (AFTR) name. In order to be able to populate such option the
such options the DHCPv6 Server must be pre-provisioned with the DHCPv6 Server must be pre-provisioned with the Address Family
Address Family Transition Router (AFTR) address or name. Transition Router (AFTR) name.
In Broadband environments, customer profile may be managed by AAA In Broadband environments, customer profile may be managed by AAA
servers, together with user Authentication, Authorization, and servers, together with user Authentication, Authorization, and
Accounting (AAA). RADIUS protocol [RFC2865] is usually used by AAA Accounting (AAA). RADIUS protocol [RFC2865] is usually used by AAA
Servers to communicate with network elements. Servers to communicate with network elements.
[I-D.ietf-radext-ipv6-access] describes a typical broadband network [I-D.ietf-radext-ipv6-access] describes a typical broadband network
scenario in which the Network Access Server (NAS) acts as the access scenario in which the Network Access Server (NAS) acts as the access
gateway for the users (hosts or CPEs) and the NAS embeds a DHCPv6 gateway for the users (hosts or CPEs) and the NAS embeds a DHCPv6
Server function that allows it to locally handle any DHCPv6 requests Server function that allows it to locally handle any DHCPv6 requests
issued by the clients. issued by the clients.
Since the DS-Lite AFTR information can be stored in AAA servers and Since the DS-Lite AFTR information can be stored in AAA servers and
the client configuration is mainly provided through DHC protocol the client configuration is mainly provided through DHC protocol
running between the NAS and the requesting clients, new RADIUS running between the NAS and the requesting clients, a new RADIUS
attributes are needed to send AFTR information from AAA server to the attribute is needed to send AFTR information from AAA server to the
NAS. NAS.
This document aims at defining two new RADIUS attributes to be used This document aims at defining a new RADIUS attribute to be used for
for carrying the DS-Lite Tunnel Name and DS-Lite Tunnel Address, carrying the DS-Lite Tunnel Name, based on the equivalent DHCPv6
based on the equivalent DHCPv6 options already specified in option already specified in [I-D.ietf-softwire-ds-lite-tunnel-option]
[I-D.ietf-softwire-ds-lite-tunnel-option]
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The terms DS-Lite Basic Bridging BroadBand element (B4) and the DS- The terms DS-Lite Basic Bridging BroadBand element (B4) and the DS-
Lite Address Family Transition Router element (AFTR) are defined in Lite Address Family Transition Router element (AFTR) are defined in
[I-D.ietf-softwire-dual-stack-lite] [I-D.ietf-softwire-dual-stack-lite]
3. DS-Lite Configuration with RADIUS and DHCPv6 3. DS-Lite Configuration with RADIUS and DHCPv6
The Figure 1 illustrates how the RADIUS protocol and DHCPv6 work The Figure 1 illustrates how the RADIUS protocol and DHCPv6 work
together to accomplish DS-Lite configuration on the B4 element. together to accomplish DS-Lite configuration on the B4 element when a
PPP Session is used to provide connectivity to the user.
B4 NAS AAA
| | Server
| | |
| | |
| |-----Access Request -------->|
| | |
| |<----Access Accept(
| | DS-Lite-Tunnel-Add |
| | DS-Lite-Tunnel-Name) |
| | |
|------DHCPv6 Request----->| |
| (DS-Lite tunnel Option) | |
| | |
|<-----DHCPv6 Reply--------| |
| (DS-Lite tunnel option) | |
DHCPv6 RADIUS
Figure 1: RADIUS and DHCPv6 Message Flow
The Network Access Server (NAS) operates as a client of RADIUS and as The Network Access Server (NAS) operates as a client of RADIUS and as
DHCP Server for DHC protocol. The NAS initially sends a RADIUS DHCP Server for DHC protocol. The NAS initially sends a RADIUS
Access Request message to the RADIUS server, requesting Access Request message to the RADIUS server, requesting
authentication. Once the RADIUS server receives the request, it authentication. Once the RADIUS server receives the request, it
validates the sending client and if the request is approved, the AAA validates the sending client and if the request is approved, the AAA
server replies with an Access Accept message including a list of server replies with an Access Accept message including a list of
attribute-value pairs that describe the parameters to be used for attribute-value pairs that describe the parameters to be used for
this session. This list may also contain the AFTR Tunnel IPv6 this session. This list may also contain the AFTR Tunnel Name. When
Address and/or the AFTR Tunnel Name. When the NAS receives a DHCPv6 the NAS receives a DHCPv6 client request containing the DS-Lite
client request containing the DS-Lite tunnel Option, the NAS shall tunnel Option, the NAS shall use the address returned in the RADIUS
use the address returned in the RADIUS DS-Lite-Tunnel-Addr attribute DS-Lite-Tunnel-Addr attribute to populate the DHCPv6
to populate the DHCPv6 OPTION_DS_LITE_ADDR option in the DHCPv6 reply OPTION_DS_LITE_ADDR option in the DHCPv6 reply message.
message.
4. Attributes
This section specifies the format of the two new RADIUS attributes. B4 NAS AAA
| | Server
| | |
|----PPP LCP Config Request------> | |
| | |
| |----Access-Request ---->|
| | |
| |<---- Access-Accept-----|
| | (DS-Lite-Tunnel-Name) |
|<-----PPP LCP Config ACK ----- | |
| | |
| | |
|------ PPP IPv6CP Config Req ---->| |
| | |
|<----- PPP IPv6CP Config ACK -----| |
| | |
|------- DHCPv6 Solicit -------->| |
| | |
|<-------DHCPv6 Advertisement -----| |
| (DHCPv6 OPTION_DS_LITE_NAME) | |
| | |
|------- DHCPv6 Request -------->| |
| | |
|<-------- DHCPv6 Reply --------- | |
| (DHCPv6 OPTION_DS_LITE_NAME) | |
4.1. DS-Lite-Tunnel-Addr DHCPv6 RADIUS
Description Figure 1: RADIUS and DHCPv6 Message Flow for a PPP Session
The DS-Lite-Tunnel-Addr RADIUS attribute contains a 128 bit IPv6 The Figure 2 illustrates how the RADIUS protocol and DHCPv6 work
address that identifies the location of the remote tunnel endpoint, together to accomplish DS-Lite configuration on the B4 element when
expected to be located at an AFTR. The NAS shall use the address an IP Session is used to provide connectivity to the user.
returned in the RADIUS DS-Lite-Tunnel-Addr attribute to populate the
DHCPv6 OPTION_DS_LITE_ADDR option
[I-D.ietf-softwire-ds-lite-tunnel-option].
This attribute MAY be used in Access-Accept packets and it MAY be The only difference between this message flow and previous one is
present in Accounting-Request records where the Acct-Status-Type is that in this scenario the interaction between NAS and AAA/ RADIUS
set to Start, Stop or Interim-Update. The DS-Lite-Tunnel-Addr RADIUS Server is triggered by the DHCPv6 Solicit message received by the NAS
attribute and MUST NOT appear more than once in a message. from the B4 acting as DHCPv6 client, while in case of a PPP Session
the trigger is the PPP LCP Config Request message received by the
NAS.
A summary of the DS-Lite-Tunnel-Addr RADIUS attribute format is shown B4 NAS AAA
below. The fields are transmitted from left to right. | | Server
|------ DHCPv6 Solicit ---------> | |
| | |
| |----Access-Request ---->|
| | |
| |<-Access-Accept---------|
| | (DS-Lite-Tunnel-Name) |
| | |
|<-------DHCPv6 Advertisement------| |
| (DHCPv6 OPTION_DS_LITE_NAME) | |
| | |
|------- DHCPv6 Request -------->| |
| | |
| | |
| <---- DHCPv6 Reply ---- | |
| (DHCPv6 OPTION_DS_LITE_NAME) | |
0 1 2 3 DHCPv6 RADIUS
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | DS-Lite-Tunnel-Addr |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DS-Lite-Tunnel-Addr (IPv6 Address)(cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Figure 2: RADIUS and DHCPv6 Message Flow for a IP Session
TBA1 for DS-Lite-Tunnel-Addr. 4. RADIUS Attribute
Length:
16 octets
DS-Lite-Tunnel-Addr: This section specifies the format of the new RADIUS attribute.
A 128-bit IPv6 address of the DS-Lite AFTR.
4.2. DS-Lite-Tunnel-Name 4.1. DS-Lite-Tunnel-Name
Description Description
The DS-Lite-Tunnel-Name RADIUS attribute contains a Fully Qualified The DS-Lite-Tunnel-Name RADIUS attribute contains a Fully Qualified
Domain Name that refers to the AFTR the client is requested to Domain Name that refers to the AFTR the client is requested to
establish a connection with. The NAS shall use the name returned in establish a connection with. The NAS shall use the name returned in
the RADIUS DS-Lite-Tunnel-Name attribute to populate the DHCPv6 the RADIUS DS-Lite-Tunnel-Name attribute to populate the DHCPv6
OPTION_DS_LITE_NAME option [I-D.ietf-softwire-ds-lite-tunnel-option] OPTION_DS_LITE_NAME option [I-D.ietf-softwire-ds-lite-tunnel-option]
This attribute MAY be used in Access-Accept packets and it MAY be This attribute MAY be used in Access-Accept packets and it MAY be
skipping to change at page 7, line 27 skipping to change at page 8, line 15
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | DS-Lite-Tunnel-Name (FQDN) | | Type | Length | DS-Lite-Tunnel-Name (FQDN) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| DS-Lite-Tunnel-Name (FQDN) (cont) | | DS-Lite-Tunnel-Name (FQDN) (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
TBA2 for DS-Lite-Tunnel-Name. TBA1 for DS-Lite-Tunnel-Name.
Length: Length:
Length in octets of the DS-Lite-Tunnel-Name (FQDN) This field indicates the total length in octets of this
attribute including the Type, the Length fields and the length
in octets of the DS-Lite-Tunnel-Name field
DS-Lite-Tunnel-Name: DS-Lite-Tunnel-Name:
A single Fully Qualified Domain Name of the remote tunnel A single Fully Qualified Domain Name of the remote tunnel
endpoint, located at the DS-Lite AFTR. endpoint, located at the DS-Lite AFTR.
5. Table of attributes 5. Table of attributes
The following table provides a guide to which attributes may be found The following table provides a guide to which attributes may be found
in which kinds of packets, and in what quantity. in which kinds of packets, and in what quantity.
Request Accept Reject Challenge Accounting # Attribute Request Accept Reject Challenge Accounting # Attribute
Request Request
0-1 0-1 0 0 0-1 TBA1 DS-Lite-Tunnel-Addr 0-1 0-1 0 0 0-1 TBA1 DS-Lite-Tunnel-Name
0-1 0-1 0 0 0-1 TBA2 DS-Lite-Tunnel-Name
The following table defines the meaning of the above table entries. The following table defines the meaning of the above table entries.
0 This attribute MUST NOT be present in packet. 0 This attribute MUST NOT be present in packet.
0+ Zero or more instances of this attribute MAY be present in 0+ Zero or more instances of this attribute MAY be present in
packet. packet.
0-1 Zero or one instance of this attribute MAY be present in packet. 0-1 Zero or one instance of this attribute MAY be present in packet.
6. Security Considerations 6. Security Considerations
This document has no additional security considerations beyond those This document has no additional security considerations beyond those
already identified in [RFC2865] already identified in [RFC2865]
[I-D.ietf-softwire-dual-stack-lite] discusses DS-Lite related [I-D.ietf-softwire-dual-stack-lite] discusses DS-Lite related
security issues. security issues.
7. IANA Considerations 7. IANA Considerations
This document requests the allocation of two new Radius attribute This document requests the allocation of a new Radius attribute types
types from the IANA registry "Radius Attribute Types" located at from the IANA registry "Radius Attribute Types" located at
http://www.iana.org/assignments/radius-types http://www.iana.org/assignments/radius-types
DS-Lite-Tunnel-Addr - TBA1 DS-Lite-Tunnel-Name - TBA1
DS-Lite-Tunnel-Name - TBA2
8. Normative References 8. Normative References
[I-D.ietf-radext-ipv6-access] [I-D.ietf-radext-ipv6-access]
Lourdelet, B., Dec, W., Sarikaya, B., Zorn, G., and D. Lourdelet, B., Dec, W., Sarikaya, B., Zorn, G., and D.
Miles, "RADIUS attributes for IPv6 Access Networks", Miles, "RADIUS attributes for IPv6 Access Networks",
draft-ietf-radext-ipv6-access-02 (work in progress), draft-ietf-radext-ipv6-access-02 (work in progress),
July 2010. July 2010.
[I-D.ietf-softwire-ds-lite-tunnel-option] [I-D.ietf-softwire-ds-lite-tunnel-option]
Hankins, D. and T. Mrugalski, "Dynamic Host Configuration Hankins, D. and T. Mrugalski, "Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) Option for Dual- Stack Lite", Protocol for IPv6 (DHCPv6) Option for Dual- Stack Lite",
draft-ietf-softwire-ds-lite-tunnel-option-05 (work in draft-ietf-softwire-ds-lite-tunnel-option-07 (work in
progress), September 2010. progress), December 2010.
[I-D.ietf-softwire-dual-stack-lite] [I-D.ietf-softwire-dual-stack-lite]
Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
Stack Lite Broadband Deployments Following IPv4 Stack Lite Broadband Deployments Following IPv4
Exhaustion", draft-ietf-softwire-dual-stack-lite-06 (work Exhaustion", draft-ietf-softwire-dual-stack-lite-06 (work
in progress), August 2010. in progress), August 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
 End of changes. 29 change blocks. 
102 lines changed or deleted 107 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/