draft-ietf-softwire-dslite-radius-ext-07.txt   rfc6519.txt 
softwire R. Maglione Internet Engineering Task Force (IETF) R. Maglione
Internet-Draft Telecom Italia Request for Comments: 6519 Telecom Italia
Intended status: Standards Track A. Durand Category: Standards Track A. Durand
Expires: April 19, 2012 Juniper Networks ISSN: 2070-1721 Juniper Networks
October 17, 2011 February 2012
RADIUS Extensions for Dual-Stack Lite RADIUS Extensions for Dual-Stack Lite
draft-ietf-softwire-dslite-radius-ext-07
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 that are addressed only with an IPv6
prefix. Dual-Stack Lite requires to pre-configure the Dual-Stack prefix. Dual-Stack Lite requires pre-configuration of the Dual-Stack
Lite Address Family Transition Router (AFTR) tunnel information on Lite Address Family Transition Router (AFTR) tunnel information on
the Basic Bridging BroadBand (B4) element. In many networks, the the Basic Bridging BroadBand (B4) element. In many networks, the
customer profile information may be stored in Authentication customer profile information may be stored in Authentication,
Authorization and Accounting (AAA) servers while client Authorization, and Accounting (AAA) servers, while client
configurations are mainly provided through Dynamic Host Configuration configurations are mainly provided through the Dynamic Host
Protocol (DHCP). This document specifies a new Remote Authentication Configuration Protocol (DHCP). This document specifies a new Remote
Dial In User Service (RADIUS) attribute to carry Dual-Stack Lite Authentication Dial-In User Service (RADIUS) attribute to carry the
Address Family Transition Router Tunnel name; the RADIUS attribute is Dual-Stack Lite AFTR tunnel name; the RADIUS attribute is defined
defined based on the equivalent DHCPv6 OPTION_AFTR_NAME option. This based on the equivalent DHCPv6 OPTION_AFTR_NAME option. This RADIUS
RADIUS attribute is meant to be used between the RADIUS Server and attribute is meant to be used between the RADIUS server and the
the Network Access Server (NAS), it is not intended to be used Network Access Server (NAS); it is not intended to be used directly
directly between the Basic Bridging BroadBand element and the RADIUS between the B4 element and the RADIUS server.
Server.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on April 19, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6519.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the
Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 7 skipping to change at page 2, line 34
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
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 ....................................................3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology .....................................................4
3. DS-Lite Configuration with RADIUS and DHCPv6 . . . . . . . . . 5 3. DS-Lite Configuration with RADIUS and DHCPv6 ....................4
4. RADIUS Attribute . . . . . . . . . . . . . . . . . . . . . . . 8 4. RADIUS Attribute ................................................7
4.1. DS-Lite-Tunnel-Name . . . . . . . . . . . . . . . . . . . 8 4.1. DS-Lite-Tunnel-Name ........................................7
5. Table of attributes . . . . . . . . . . . . . . . . . . . . . 10 5. Table of Attributes .............................................9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations .........................................9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 7. IANA Considerations .............................................9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. References .....................................................10
8.1. Normative References . . . . . . . . . . . . . . . . . . . 10 8.1. Normative References ......................................10
8.2. Informative References . . . . . . . . . . . . . . . . . . 11 8.2. Informative References ....................................10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Dual-Stack Lite [RFC6333] is a solution to offer both IPv4 and IPv6 Dual-Stack Lite [RFC6333] is a solution to offer both IPv4 and IPv6
connectivity to customers which are addressed only with an IPv6 connectivity to customers that are addressed only with an IPv6 prefix
prefix (no IPv4 address is assigned to the attachment device). One (no IPv4 address is assigned to the attachment device). One of its
of its key components is an IPv4-over-IPv6 tunnel, but a Dual-Stack- key components is an IPv4-over-IPv6 tunnel, but a Dual-Stack-Lite
Lite Basic Bridging BroadBand (B4) will not know if the network it is Basic Bridging BroadBand (B4) element will not know if the network to
attached to offers Dual-Stack Lite support, and if it did, would not which it is attached offers Dual-Stack Lite support. Even if the B4
know the remote end of the tunnel to establish a connection. did know, it would not know the remote end of the tunnel to which it
could establish a connection.
To inform the Basic Bridging BroadBand (B4) of the Address Family To inform the B4 element of the location of the Address Family
Transition Router's (AFTR) location, a Fully Qualified Domain Name Transition Router (AFTR), a Fully Qualified Domain Name (FQDN) may be
(FQDN) may be used. Once this information is conveyed, the presence used. Once this information is conveyed, the presence of the
of the configuration indicating the AFTR's location also informs a configuration indicating the AFTR's location also informs a host to
host to initiate Dual-Stack Lite (DS-Lite) service and become a initiate Dual-Stack Lite (DS-Lite) service and become a Softwire
Softwire Initiator. Initiator.
[RFC6334] specifies a DHCPv6 option which is meant to be used by a [RFC6334] specifies a DHCPv6 option that is meant to be used by a
Dual-Stack Lite client (Basic Bridging BroadBand element, B4) to DS-Lite client (B4 element) to discover its AFTR name. In order to
discover its Address Family Transition Router (AFTR) name. In order be able to populate such an option, the DHCPv6 server must be
to be able to populate such option the DHCPv6 Server must be pre- pre-provisioned with the AFTR name.
provisioned with the Address Family Transition Router (AFTR) name.
In Broadband environments, customer profile may be managed by AAA In broadband environments, a customer profile may be managed by
servers, together with user Authentication, Authorization, and Authentication, Authorization, and Accounting (AAA) servers, together
Accounting (AAA). Remote Authentication Dial In User Service with AAA for users. The Remote Authentication Dial-In User Service
(RADIUS) protocol [RFC2865] is usually used by AAA Servers to (RADIUS) protocol [RFC2865] is usually used by AAA servers to
communicate with network elements. [I-D.ietf-radext-ipv6-access] communicate with network elements. [RADIUS-IPv6] describes a typical
describes a typical broadband network scenario in which the Network broadband network scenario in which the Network Access Server (NAS)
Access Server (NAS) acts as the access gateway for the users (hosts acts as the access gateway for the users (hosts or Customer Premises
or CPEs) and the NAS embeds a DHCPv6 Server function that allows it Equipment (CPE) devices) and also embeds a DHCPv6 server function
to locally handle any DHCPv6 requests issued by the clients. that allows it to locally handle any DHCPv6 requests 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 Dynamic Host the client configuration is mainly provided through DHCP running
Configuration Protocol (DHCP) running between the NAS and the between the NAS and the requesting clients, a new RADIUS attribute is
requesting clients, a new RADIUS attribute is needed to send AFTR needed to send AFTR information from the AAA server to the NAS.
information from AAA server to the NAS.
This document aims at defining a new RADIUS attribute to be used for This document defines a new RADIUS attribute to be used for carrying
carrying the DS-Lite Tunnel Name, based on the equivalent DHCPv6 the DS-Lite Tunnel Name, based on the equivalent DHCPv6 option
option already specified in [RFC6334] already specified in [RFC6334].
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
Lite Address Family Transition Router element (AFTR) are defined in DS-Lite Address Family Transition Router element (AFTR) are defined
[RFC6333] in [RFC6333].
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 Figure 1 illustrates how the RADIUS protocol and DHCPv6 work together
together to accomplish DS-Lite configuration on the B4 element when a to accomplish DS-Lite configuration on the B4 element when a PPP
PPP Session is used to provide connectivity to the user. session is used to provide connectivity to the user.
The Network Access Server (NAS) operates as a client of RADIUS and as The NAS operates as a client of RADIUS and as a DHCP Server. The NAS
DHCP Server for DHC protocol. The NAS initially sends a RADIUS initially sends a RADIUS Access-Request message to the RADIUS server,
Access Request message to the RADIUS server, requesting requesting authentication. Once the RADIUS server receives the
authentication. Once the RADIUS server receives the request, it request, it validates the sending client, and if the request is
validates the sending client and if the request is approved, the AAA approved, the AAA server replies with an Access-Accept message
server replies with an Access Accept message including a list of including a list of attribute-value pairs that describe the
attribute-value pairs that describe the parameters to be used for parameters to be used for this session. This list MAY also contain
this session. This list MAY also contain the AFTR Tunnel Name. When the AFTR tunnel name. When the NAS receives a DHCPv6 client request
the NAS receives a DHCPv6 client request containing the DS-Lite containing the DS-Lite tunnel option, the NAS SHALL use the name
tunnel Option, the NAS SHALL use the name returned in the RADIUS DS- returned in the RADIUS DS-Lite-Tunnel-Name attribute to populate the
Lite-Tunnel-Name attribute to populate the DHCPv6 OPTION_AFTR_NAME DHCPv6 OPTION_AFTR_NAME option in the DHCPv6 reply message.
option in the DHCPv6 reply message.
B4 NAS AAA B4 NAS AAA
| | Server | | Server
| | | | | |
|----PPP LCP Config Request------> | | |----PPP LCP Config-Request------> | |
| | | | | |
| |----Access-Request ---->| | |----Access-Request ---->|
| | | | | |
| |<---- Access-Accept-----| | |<---- Access-Accept-----|
| | (DS-Lite-Tunnel-Name) | | | (DS-Lite-Tunnel-Name) |
|<-----PPP LCP Config ACK ------- | | |<-----PPP LCP Config-ACK ------- | |
| | | | | |
| | | | | |
|------ PPP IPv6CP Config Req ---->| | |--- PPP IPv6CP Config-Request --->| |
| | | | | |
|<----- PPP IPv6CP Config ACK -----| | |<----- PPP IPv6CP Config-ACK -----| |
| | | | | |
|------- DHCPv6 Solicit -------->| | |------- DHCPv6 Solicit -------->| |
| | | | | |
|<-------DHCPv6 Advertisement -----| | |<-------DHCPv6 Advertisement -----| |
| (DHCPv6 OPTION_AFTR_NAME) | | | (DHCPv6 OPTION_AFTR_NAME) | |
| | | | | |
|------- DHCPv6 Request -------->| | |------- DHCPv6 Request -------->| |
| | | | | |
|<-------- DHCPv6 Reply ---------- | | |<-------- DHCPv6 Reply ---------- | |
| (DHCPv6 OPTION_AFTR_NAME) | | | (DHCPv6 OPTION_AFTR_NAME) | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 1: RADIUS and DHCPv6 Message Flow for a PPP Session Figure 1: RADIUS and DHCPv6 Message Flow for a PPP Session
The Figure 2 illustrates how the RADIUS protocol and DHCPv6 work Figure 2 illustrates how the RADIUS protocol and DHCPv6 work together
together to accomplish DS-Lite configuration on the B4 element when to accomplish DS-Lite configuration on the B4 element when an IP
an IP Session is used to provide connectivity to the user. session is used to provide connectivity to the user.
The only difference between this message flow and previous one is The only difference between this message flow and the previous one is
that in this scenario the interaction between NAS and AAA/ RADIUS that in this scenario, the interaction between the NAS and the AAA/
Server is triggered by the DHCPv6 Solicit message received by the NAS RADIUS server is triggered by the DHCPv6 Solicit message received by
from the B4 acting as DHCPv6 client, while in case of a PPP Session the NAS from the B4 acting as a DHCPv6 client, while in the case of a
the trigger is the PPP LCP Config Request message received by the PPP session, the trigger is the PPP Link Control Protocol (LCP)
NAS. Config-Request message received by the NAS.
B4 NAS AAA B4 NAS AAA
| | Server | | Server
|------ DHCPv6 Solicit ---------> | | |------ DHCPv6 Solicit ---------> | |
| | | | | |
| |----Access-Request ---->| | |----Access-Request ---->|
| | | | | |
| |<---Access-Accept-------| | |<---Access-Accept-------|
| | (DS-Lite-Tunnel-Name) | | | (DS-Lite-Tunnel-Name) |
| | | | | |
skipping to change at page 7, line 27 skipping to change at page 6, line 27
|------- DHCPv6 Request -------->| | |------- DHCPv6 Request -------->| |
| | | | | |
| | | | | |
|<----- DHCPv6 Reply ------------- | | |<----- DHCPv6 Reply ------------- | |
| (DHCPv6 OPTION_AFTR_NAME) | | | (DHCPv6 OPTION_AFTR_NAME) | |
DHCPv6 RADIUS DHCPv6 RADIUS
Figure 2: RADIUS and DHCPv6 Message Flow for an IP Session Figure 2: RADIUS and DHCPv6 Message Flow for an IP Session
In the scenario depicted in Figure 2 the Access-Request packet In the scenario depicted in Figure 2, the Access-Request packet
contains a Service-Type attribute with the value Authorize Only (17), contains a Service-Type attribute with the value Authorize Only (17);
thus according to [RFC5080] the Access-Request packet MUST contain a thus, according to [RFC5080], the Access-Request packet MUST contain
State attribute. a State attribute.
After receiving the DS-Lite-Tunnel-Name in the initial Access-Accept After receiving the DS-Lite-Tunnel-Name attribute in the initial
the NAS MUST store the received AFTR Tunnel Name locally. When the Access-Accept packet, the NAS MUST store the received AFTR tunnel
B4 sends a DHCPv6 Renew message to request an extension of the name locally. When the B4 sends a DHCPv6 Renew message to request an
lifetimes for the assigned address or prefix, the NAS does not have extension of the lifetimes for the assigned address or prefix, the
to initiate a new Access-Request towards the AAA server to request NAS does not have to initiate a new Access-Request packet towards the
the AFTR tunnel name. The NAS retrieves the previously stored AFTR AAA server to request the AFTR tunnel name. The NAS retrieves the
tunnel name and uses it in its reply. previously stored AFTR tunnel name and uses it in its reply.
According to [RFC3315] if the DHCPv6 server to which the DHCPv6 Renew According to [RFC3315], if the DHCPv6 server to which the DHCPv6
message was sent at time T1 has not responded, the DHCPv6 client Renew message was sent at time T1 has not responded, the DHCPv6
initiates a Rebind/Reply message exchange with any available server. client initiates a Rebind/Reply message exchange with any available
In this scenario the NAS receiving the DHCPv6 rebind message MUST server. In this scenario, the NAS receiving the DHCPv6 Rebind
initiate a new Access-Request towards the AAA server. The NAS MAY message MUST initiate a new Access-Request message towards the AAA
include the DS-Lite-Tunnel-Name attribute in its Access-Request. server. The NAS MAY include the DS-Lite-Tunnel-Name attribute in its
Access-Request message.
If the NAS does not receive the DS-Lite-Tunnel-Name attribute in the If the NAS does not receive the DS-Lite-Tunnel-Name attribute in the
Access-Accept it MAY fallback to a pre-configured default tunnel Access-Accept message, it MAY fall back to a pre-configured default
name, if any. If the NAS does not have any pre-configured default tunnel name, if any. If the NAS does not have any pre-configured
tunnel name or if the NAS receives an Access-Reject, the IPv4 over default tunnel name or if the NAS receives an Access-Reject message,
IPv6 tunnel cannot be established, thus the B4 element has only IPv6 the IPv4-over-IPv6 tunnel cannot be established; thus, the B4 element
connectivity. has only IPv6 connectivity.
4. RADIUS Attribute 4. RADIUS Attribute
This section specifies the format of the new RADIUS attribute. This section specifies the format of the new RADIUS attribute.
4.1. DS-Lite-Tunnel-Name 4.1. DS-Lite-Tunnel-Name
Description
The DS-Lite-Tunnel-Name RADIUS attribute contains a Fully Qualified The DS-Lite-Tunnel-Name RADIUS attribute contains an FQDN that refers
Domain Name that refers to the AFTR the client is requested to to the AFTR to which the client is requested to establish a
establish a connection with. The NAS SHALL use the name returned in connection. The NAS SHALL use the name returned in the RADIUS
the RADIUS DS-Lite-Tunnel-Name attribute to populate the DHCPv6 DS-Lite-Tunnel-Name attribute to populate the DHCPv6 OPTION_AFTR_NAME
OPTION_AFTR_NAME option [RFC6334] option [RFC6334].
This attribute MAY be used in Access-Request packets as a hint to the This attribute MAY be used in Access-Request packets as a hint to the
RADIUS server; for example if the NAS is pre-configured with a RADIUS server; for example, if the NAS is pre-configured with a
default tunnel name, this name MAY be inserted in the attribute. The default tunnel name, this name MAY be inserted in the attribute. The
RADIUS server MAY ignore the hint sent by the NAS and it MAY assign a RADIUS server MAY ignore the hint sent by the NAS, and it MAY assign
different AFTR tunnel name. a different AFTR tunnel name.
If the NAS includes the DS-Lite-Tunnel-Name attribute, but the AAA If the NAS includes the DS-Lite-Tunnel-Name attribute, but the AAA
server does not recognize it, this attribute MUST be ignored by the server does not recognize it, this attribute MUST be ignored by the
AAA Server. AAA server.
If the NAS does not receive DS-Lite-Tunnel-Name attribute in the If the NAS does not receive the DS-Lite-Tunnel-Name attribute in the
Access-Accept it MAY fallback to a pre-configured default tunnel Access-Accept message, it MAY fall back to a pre-configured default
name, if any. If the NAS does not have any pre-configured default tunnel name, if any. If the NAS does not have any pre-configured
tunnel name, the tunnel can not be established. default tunnel name, the tunnel cannot be established.
If the NAS is pre-provisioned with a default AFTR tunnel name and the If the NAS is pre-provisioned with a default AFTR tunnel name and the
AFTR tunnel name received in Access-Accept is different from the AFTR tunnel name received in the Access-Accept message is different
configured default, then the AFTR tunnel name received in the Access- from the configured default, then the AFTR tunnel name received in
Accept message MUST be used for the session. the Access-Accept message MUST be used for the session.
If the NAS cannot support the received AFTR tunnel name for any If the NAS cannot support the received AFTR tunnel name for any
reason, the tunnel SHOULD NOT be established. reason, the tunnel SHOULD NOT be established.
When the Access-Request is triggered by a DHCPv6 Rebind message if When the Access-Request message is triggered by a DHCPv6 Rebind
the AFTR tunnel name received in the Access-Accept is different from message, if the AFTR tunnel name received in the Access-Accept
the currently used one for that session, the NAS MUST force the B4 to message is different from the currently used one for that session,
re-establish the tunnel using the new AFTR name received in the the NAS MUST force the B4 to re-establish the tunnel using the new
Access-Accept message. AFTR name received in the Access-Accept message.
If an implementation includes the Change-of-Authorization (CoA) If an implementation includes Change-of-Authorization (CoA) messages
messages [RFC5176], they could be used to modify the current [RFC5176], they could be used to modify the current established
established DS-Lite tunnel. When the NAS receives a CoA Request DS-Lite tunnel. When the NAS receives a CoA Request message
message containing the DS-Lite-Tunnel-Name attribute, the NAS MUST containing the DS-Lite-Tunnel-Name attribute, the NAS MUST send a
send a Reconfigure message to a B4 to inform the B4 that the NAS has Reconfigure message to a B4 to inform the B4 that the NAS has new or
new or updated configuration parameters and that the B4 is to updated configuration parameters and that the B4 is to initiate a
initiate a Renew/Reply or Information-request/Reply transaction with Renew/Reply or Information-Request/Reply transaction with the NAS in
the NAS in order to receive the updated information. order to receive the updated information.
Upon receiving an AFTR tunnel name different from the currently used Upon receiving an AFTR tunnel name different from the currently used
one, the B4 MUST terminate the current DS-Lite tunnel and the B4 MUST one, the B4 MUST terminate the current DS-Lite tunnel, and the B4
establish a new DS-LITE tunnel with the specified AFTR. MUST establish a new DS-Lite tunnel with the specified AFTR.
The DS-Lite-Tunnel-Name RADIUS attribute MAY be present in The DS-Lite-Tunnel-Name RADIUS attribute MAY be present in
Accounting-Request records where the Acct-Status-Type is set to Accounting-Request records where the Acct-Status-Type is set to
Start, Stop or Interim-Update. The DS-Lite-Tunnel-Name RADIUS Start, Stop, or Interim-Update. The DS-Lite-Tunnel-Name RADIUS
attribute MUST NOT appear more than once in a message. attribute MUST NOT appear more than once in a message.
A summary of the DS-Lite-Tunnel-Name RADIUS attribute format is shown A summary of the DS-Lite-Tunnel-Name RADIUS attribute format is shown
below. The fields are transmitted from left to right. below. The fields are transmitted from left to right.
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)...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
TBA1 for DS-Lite-Tunnel-Name. 144 for DS-Lite-Tunnel-Name.
Length: Length:
This field indicates the total length in octets of this This field indicates the total length in octets of this
attribute including the Type, the Length fields and the length attribute including the Type and Length fields, and the length
in octets of the DS-Lite-Tunnel-Name field 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
endpoint, located at the DS-Lite AFTR. This field contains a single FQDN of the remote tunnel endpoint,
located at the DS-Lite AFTR.
As the DS-Lite-Tunnel-Name attribute is used to populate the DHCPv6 As the DS-Lite-Tunnel-Name attribute is used to populate the DHCPv6
OPTION_AFTR_NAME option, the DS-Lite-Tunnel-Name field is formatted OPTION_AFTR_NAME option, the DS-Lite-Tunnel-Name field is formatted
as required in DHCPv6 (Section 8 of [RFC3315] "Representation and Use as required in DHCPv6 (Section 8 of [RFC3315] -- "Representation and
of Domain Names"). Briefly, the format described is using a single Use of Domain Names"). Briefly, the format described is using a
octet noting the length of one DNS label (limited to at most 63 single octet noting the length of one DNS label (limited to at most
octets), followed by the label contents. This repeats until all 63 octets), followed by the label contents. This repeats until all
labels in the FQDN are exhausted, including a terminating zero-length labels in the FQDN are exhausted, including a terminating zero-length
label. Any updates to Section 8 of [RFC3315] also apply to encoding label. Any updates to Section 8 of [RFC3315] also apply to the
of this field. encoding of this field.
The data type of DS-Lite-Tunnel-Name RADIUS attribute is a string The data type of the DS-Lite-Tunnel-Name RADIUS attribute is a string
with opaque encapsulation, according to section 5 of [RFC2865] with opaque encapsulation, according to Section 5 of [RFC2865].
5. Table of attributes 5. Table of Attributes
The following tables provide a guide to which attributes may be found The following tables provide 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.
Access- Access- Access- Challenge Accounting # Attribute Access- Access- Access- Challenge Accounting # Attribute
Request Accept Reject Request Request Accept Reject Request
0-1 0-1 0 0 0-1 TBA1 DS-Lite-Tunnel-Name 0-1 0-1 0 0 0-1 144 DS-Lite-Tunnel-Name
CoA-Request CoA-ACK CoA-NACK # Attribute CoA-Request CoA-ACK CoA-NACK # Attribute
0-1 0 0 TBA1 DS-Lite-Tunnel-Name 0-1 0 0 144 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 the 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 the
packet.
0-1 Zero or one instance of this attribute MAY be present in the
packet. 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] for RADIUS protocol and in [RFC5176] already identified in [RFC2865] for the RADIUS protocol and in
for CoA messages. [RFC5176] for CoA messages.
[RFC6333] discusses Dual-Stack Lite related security issues. [RFC6333] discusses security issues related to Dual-Stack Lite.
7. IANA Considerations 7. IANA Considerations
This document requests the allocation of a new Radius attribute types Per this document, IANA has allocated a new RADIUS attribute type
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-Name - TBA1 DS-Lite-Tunnel-Name - 144
8. References 8. References
8.1. Normative References 8.1. Normative References
[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.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", "Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000. RFC 2865, June 2000.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T.,
and M. Carney, "Dynamic Host Configuration Protocol for Perkins, C., and M. Carney, "Dynamic Host
IPv6 (DHCPv6)", RFC 3315, July 2003. Configuration Protocol for IPv6 (DHCPv6)", RFC 3315,
July 2003.
[RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication
Dial In User Service (RADIUS) Implementation Issues and Dial In User Service (RADIUS) Implementation Issues
Suggested Fixes", RFC 5080, December 2007. and Suggested Fixes", RFC 5080, December 2007.
[RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual- [RFC6333] Durand, A., Droms, R., Woodyatt, J., and Y. Lee,
Stack Lite Broadband Deployments Following IPv4 "Dual-Stack Lite Broadband Deployments Following IPv4
Exhaustion", RFC 6333, August 2011. Exhaustion", RFC 6333, August 2011.
[RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration [RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host
Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite", Configuration Protocol for IPv6 (DHCPv6) Option for
RFC 6334, August 2011. Dual-Stack Lite", RFC 6334, August 2011.
8.2. Informative References 8.2. Informative References
[I-D.ietf-radext-ipv6-access] [RADIUS-IPv6] Lourdelet, B., Dec, W., Ed., Sarikaya, B., Zorn, G.,
Lourdelet, B., Dec, W., Sarikaya, B., Zorn, G., and D. and D. Miles, "RADIUS attributes for IPv6 Access
Miles, "RADIUS attributes for IPv6 Access Networks", Networks", Work in Progress, November 2011.
draft-ietf-radext-ipv6-access-05 (work in progress),
July 2011.
[RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. [RFC5176] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 5176, Authentication Dial In User Service (RADIUS)",
January 2008. RFC 5176, January 2008.
Authors' Addresses Authors' Addresses
Roberta Maglione Roberta Maglione
Telecom Italia Telecom Italia
Via Reiss Romoli 274 Via Reiss Romoli 274
Torino 10148 Torino 10148
Italy Italy
Phone: EMail: roberta.maglione@telecomitalia.it
Email: roberta.maglione@telecomitalia.it
Alain Durand Alain Durand
Juniper Networks Juniper Networks
1194 North Mathilda Avenue 1194 North Mathilda Avenue
Sunnyvale, CA 94089-1206 Sunnyvale, CA 94089-1206
USA USA
Phone: EMail: adurand@juniper.net
Fax:
Email: adurand@juniper.net
URI:
 End of changes. 68 change blocks. 
227 lines changed or deleted 223 lines changed or added

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