draft-ietf-dhc-dhcpv6-radius-opt-04.txt   draft-ietf-dhc-dhcpv6-radius-opt-05.txt 
DHC Working Group L. Yeh DHC Working Group L. Yeh
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track M. Boucadair Intended status: Standards Track M. Boucadair
Expires: May 9, 2013 France Telecom Expires: June 2, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
November 5, 2012 November 29, 2012
RADIUS Option for DHCPv6 Relay Agents on Broadband Access Server RADIUS Option for DHCPv6 Relay Agents on Broadband Access Server
draft-ietf-dhc-dhcpv6-radius-opt-04 draft-ietf-dhc-dhcpv6-radius-opt-05
Abstract Abstract
The DHCPv6 RADIUS option provides a mechanism to exchange The DHCPv6 RADIUS option provides a mechanism to exchange
authorization and identification information between relay agent and authorization and identification information between relay agent and
server. This mechanism is meant for the centralized DHCPv6 server to server. This mechanism is meant for the centralized DHCPv6 server to
select the right configuration for the requesting client based on the select the right configuration for the requesting client based on the
authorization information received from the RADIUS server, which is authorization information received from the RADIUS server, which is
not co-located with the DHCPv6 server. The NAS acts as DHCPv6 relay not co-located with the DHCPv6 server. The Network Access Server
agent and RADIUS client simultaneously in this document. (NAS) acts as DHCPv6 relay agent and RADIUS client simultaneously in
this document.
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 May 9, 2013. This Internet-Draft will expire on June 2, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 2, line 16 skipping to change at page 2, line 17
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Language . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Language . . . . . . . . . . . . . . . . . . . 3
3. Network Scenarios . . . . . . . . . . . . . . . . . . . . . . . 4 3. Network Scenarios . . . . . . . . . . . . . . . . . . . . . . . 4
4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 6 4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 6
5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 6 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 7
6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
skipping to change at page 3, line 20 skipping to change at page 3, line 20
[RFC3315], IPv6 prefix [RFC3633], etc. The stateless configuration [RFC3315], IPv6 prefix [RFC3633], etc. The stateless configuration
parameters [RFC3736] include, for example, DNS [RFC3646], or a FQDN parameters [RFC3736] include, for example, DNS [RFC3646], or a FQDN
of AFTR [RFC6334]. In this document, the DHCPv6 server is deployed of AFTR [RFC6334]. In this document, the DHCPv6 server is deployed
in the central part of an ISP network. in the central part of an ISP network.
RADIUS [RFC2865] is widely used as the centralized authentication, RADIUS [RFC2865] is widely used as the centralized authentication,
authorization and user management mechanism for the service provision authorization and user management mechanism for the service provision
in Broadband access network. [RFC3162], [RFC4818], [RFC6519] and in Broadband access network. [RFC3162], [RFC4818], [RFC6519] and
[I-D.ietf-radext-ipv6-access] specified attributes that support the [I-D.ietf-radext-ipv6-access] specified attributes that support the
service provision for IPv6-only and IPv6-transition access. RADIUS service provision for IPv6-only and IPv6-transition access. RADIUS
server authorizes the NAS to assign an IPv6 address or prefix from server authorizes the Network Access Server (NAS) to assign an IPv6
the indicated pool, or to assign an IPv6 address or prefix with an address or prefix from the indicated pool, or to assign an IPv6
explicitly indicated value, and other configuration parameters as per address or prefix with an explicitly indicated value, and other
the attributes for the subscribers. configuration parameters as per the attributes for the subscribers.
These mechanisms work well in the deployment scenarios where the NAS These mechanisms work well in the deployment scenarios where the NAS
acts as the distributed DHCPv6 server. In that case the NAS directly acts as the distributed DHCPv6 server. In that case the NAS directly
responds the DHCPv6 messages as per the indication conveyed by the responds the DHCPv6 messages as per the indication conveyed by the
attributes in the Access-Accept message from the RADIUS server. attributes in the Access-Accept message from the RADIUS server.
These mechanisms might also work well in the scenario where the These mechanisms might also work well in the scenario where the
centralized DHCPv6 server is co-located with the RADIUS server, where centralized DHCPv6 server is co-located with the RADIUS server, where
they can share the same database of the users. But when the NAS acts they can share the same database of the users. But when the NAS acts
as the relay agent and RADIUS client simultaneously, and the as the relay agent and RADIUS client simultaneously, and the
centralized DHCPv6 server is not located in the same place as the centralized DHCPv6 server is not located in the same place as the
skipping to change at page 4, line 33 skipping to change at page 4, line 33
| | | | | |
| |<--Access-Accept------------| | |<--Access-Accept------------|
| |(e.g. Delegated-IPv6-Prefix)| | |(e.g. Delegated-IPv6-Prefix)|
| | | | | |
DHCPv6 messages RADIUS messages DHCPv6 messages RADIUS messages
+-------+ +-------+
|DHCPv6 | |DHCPv6 |
|Server | |Server |
+-------+ +-------+
| | | | | |
| |---Relay-Forward----------->| | |---Relay-forward----------->|
| | (OPTION_RADIUS) | | | (OPTION_RADIUS) |
| | | | | |
| |<--Relay-Reply -------------| | |<--Relay-reply -------------|
|<--Advertise---------------| | |<--Advertise---------------| |
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
|---Request---------------->| | |---Request---------------->| |
| (e.g. IA_PD) |---Relay-Forward----------->| | (e.g. IA_PD) |---Relay-forward----------->|
| | (OPTION_RADIUS) | | | (OPTION_RADIUS) |
| | | | | |
| |<--Relay-Reply -------------| | |<--Relay-reply -------------|
|<--Reply-------------------| | |<--Reply-------------------| |
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
DHCPv6 messages DHCPv6 messages DHCPv6 messages DHCPv6 messages
Figure 1: Network scenario and message sequence when employing DHCPv6 Figure 1: Network scenario and message sequence when employing DHCPv6
RADIUS option in IPoE access RADIUS option in IPoE access
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
skipping to change at page 5, line 24 skipping to change at page 5, line 24
|<----PPP LCP Config-ACK----|(e.g. Delegated-IPv6-Prefix)| |<----PPP LCP Config-ACK----|(e.g. Delegated-IPv6-Prefix)|
| | | | | |
PPP messages RADIUS messages PPP messages RADIUS messages
+-------+ +-------+
|DHCPv6 | |DHCPv6 |
|Server | |Server |
+-------+ +-------+
| | | | | |
|---Solicit---------------->| | |---Solicit---------------->| |
| |---Relay-Forward----------->| | |---Relay-forward----------->|
| | (OPTION_RADIUS) | | | (OPTION_RADIUS) |
| | | | | |
| |<--Relay-Reply -------------| | |<--Relay-reply -------------|
|<--Advertise---------------| | |<--Advertise---------------| |
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
|---Request---------------->| | |---Request---------------->| |
| (e.g. IA_PD) |---Relay-Forward----------->| | (e.g. IA_PD) |---Relay-forward----------->|
| | (OPTION_RADIUS) | | (OPTION_RADIUS)
| | | | | |
| |<--Relay-Reply -------------| | |<--Relay-reply -------------|
|<--Reply-------------------| | |<--Reply-------------------| |
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
DHCPv6 messages DHCPv6 messages DHCPv6 messages DHCPv6 messages
Figure 2: Network scenario and message sequence when employing DHCPv6 Figure 2: Network scenario and message sequence when employing DHCPv6
RADIUS option in PPPoE access RADIUS option in PPPoE access
If the authorization through RADIUS fails, the associated message If the authentication or the authorization through RADIUS fails, the
sequences will stop. The NAS acting as the DHCPv6 relay agent will associated message sequences will stop. The NAS acting as the DHCPv6
not forward the message received from the client to the server. relay agent will not forward the message received from the client to
After receiving RENEW (5) message from the DHCPv6 client, the NAS the server. After receiving RENEW (5) message from the DHCPv6
does not have to initiate a new Access-Request/Access message client, the NAS does not have to initiate a new Access-Request/
exchange with the RADIUS server; but after receiving REBIND (6) Access-Accept message exchange with the RADIUS server; but after
message from the DHCPv6 client, the NAS has to initiate a new Access- receiving REBIND (6) message from the DHCPv6 client, the NAS has to
Request/Access message exchange with the RADIUS server. initiate a new Access-Request/Access-Accept message exchange with the
RADIUS server.
4. DHCPv6 RADIUS option 4. DHCPv6 RADIUS option
The OPTION_RADIUS is a stateless DHCPv6 option, and is used by the The OPTION_RADIUS is a stateless DHCPv6 option, and is used by the
relay agent to carry the authorization information of RADIUS relay agent to carry the authorization information of RADIUS
attributes received in the Access-Accept message. attributes received in the Access-Accept message.
The format of the OPTION_RADIUS option is defined as follows: The format of the OPTION_RADIUS option is defined as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_RADIUS | option-len | | OPTION_RADIUS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| option-data (List of RADIUS Attributes) | option-data (List of RADIUS Attributes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code TBD option-code TBD
option-len Length of the option-data in Octets option-len Length of the option-data in octets
option-data List of one or more RADIUS Attributes option-data List of one or more RADIUS Attributes
The option-data of OPTION_RADIUS is a list of one or more RADIUS The option-data of OPTION_RADIUS is a list of one or more RADIUS
attributes received in the Access-Accept message from the RADIUS attributes received in the Access-Accept message from the RADIUS
server. Only the attributes listed in the IANA Registry of 'RADIUS server. Only the attributes listed in the IANA Registry of 'RADIUS
Attributes Permitted in the DHCPv6 RADIUS option' Should be included Attributes Permitted in the DHCPv6 RADIUS option' SHOULD be included
in the OPTION_RADIUS. in the OPTION_RADIUS.
The RADIUS attributes listed in the below table are recommended as The RADIUS attributes listed in the below table are recommended as
the first batch of attributes in the IANA Registry of 'RADIUS the first batch of attributes in the IANA Registry of 'RADIUS
Attributes Permitted in the DHCPv6 RADIUS option'. Attributes Permitted in the DHCPv6 RADIUS option'. New RADIUS
attributes MAY be added to this list after the IETF Expert Review
[RFC5226].
Type Code Attribute Reference Type Code Attribute Reference
26 Vendor-Specific [RFC2865] 26 Vendor-Specific [RFC2865]
123 Delegated-IPv6-Prefix [RFC4818] 123 Delegated-IPv6-Prefix [RFC4818]
144 DS-Lite-Tunnel-Name [RFC6519] 144 DS-Lite-Tunnel-Name [RFC6519]
[TBD] Framed-IPv6-Address [I-D.ietf-radext-ipv6-access] [TBD] Framed-IPv6-Address [I-D.ietf-radext-ipv6-access]
[TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access] [TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access]
[TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access] [TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access]
[TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access] [TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access]
Note: The definition of the RADIUS attribute's 'Length' field in Note: The definition of the RADIUS attribute's 'Length' field in
section 5 of [RFC2865] is different from that of DHCPv6 option's section 5 of [RFC2865] includes the length of 'Type' and 'Length'
'option-len' field defined here. fields.
5. Relay Agent Behavior 5. Relay Agent Behavior
The DHCPv6 relay agent may include OPTION_RADIUS in the RELAY-FORW The DHCPv6 relay agent MAY include OPTION_RADIUS in the RELAY-FORW
(12) message. When the value in the attributes of Stateful-IPv6- (12) message. When the value in the attributes of Stateful-IPv6-
Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123) Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123)
or Framed-IPv6-Address in the Access-Accept message replied from or Framed-IPv6-Address in the Access-Accept message replied from
RADIUS server are valid, the relay agent that supports OPTION_RADIUS RADIUS server are valid, the relay agent that supports OPTION_RADIUS
SHOULD include these RADIUS attributes into the container option, SHOULD include these RADIUS attributes into the container option,
OPTION_RADIUS. OPTION_RADIUS.
6. Server Behavior 6. Server Behavior
Upon receipt of the RELAY-FORW (12) message with OPTION_RADIUS from a Upon receipt of the RELAY-FORW (12) message with OPTION_RADIUS from a
relay agent, the DHCPv6 server SHOULD extract and interpret the relay agent, the DHCPv6 server SHOULD extract and interpret the
RADIUS attributes in the OPTION_RADIUS, and use that information in RADIUS attributes in the OPTION_RADIUS, and use that information in
selecting configuration parameters for the requesting client. If the selecting configuration parameters for the requesting client. If the
DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server MUST DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server MUST
silently discard this option. silently discard this option.
7. Client Behavior 7. Client Behavior
OPTION_RADIUS option is only sent from the relay agents to the OPTION_RADIUS is only exchanged between the relay agents and the
servers. DHCPv6 clients are not aware of the usage of OPTION_RADIUS. servers. DHCPv6 clients are not aware of the usage of OPTION_RADIUS.
DHCPv6 Client MUST NOT send OPTION_RADIUS, and MUST ignore DHCPv6 client MUST NOT send OPTION_RADIUS, and MUST ignore
OPTION_RADIUS if received. OPTION_RADIUS if received.
8. Security Considerations 8. Security Considerations
Known security vulnerabilities of the DHCPv6 and RADIUS protocol may Known security vulnerabilities of the DHCPv6 and RADIUS protocol MAY
apply to its options. Security issues related with DHCPv6 are apply to its options. Security issues related with DHCPv6 are
described in section 23 of [RFC3315]. Security issues related with described in section 23 of [RFC3315]. Security issues related with
RADIUS are described in section 8 of [RFC2865], section 5 of RADIUS are described in section 8 of [RFC2865], section 5 of
[RFC3162]. [RFC3162].
9. IANA Considerations 9. IANA Considerations
This document requests to assign a new DHCPv6 option code for This document requests to assign a new DHCPv6 option code for
OPTION_RADIUS, and to create a new registry on the same assignments OPTION_RADIUS, and to create a new registry on the same assignment
page, which can be entitled as 'RADIUS Attributes Permitted in the page, which can be entitled as 'RADIUS Attributes Permitted in the
DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS
Attributes Types Attributes Types
(http://www.iana.org/assignments/radius-types/radius-types.xml) that (http://www.iana.org/assignments/radius-types/radius-types.xml) that
are permitted to be included in the DHCPv6 RADIUS option. The RADIUS are permitted to be included in the DHCPv6 RADIUS option. New RADIUS
Attribute may be added to this list after IETF Review [RFC5226]. The attributes MAY be added to this list after the IETF Expert Review
IETF Review Should include careful consideration of the security
implications of allowing the relay agent to include the RADIUS [RFC5226]. The IETF expert review SHOULD include careful
attribute being considered for addition to this registry. consideration of the security implications of allowing the relay
agent to include the RADIUS attribute being considered for addition
to this registry.
10. Acknowledgements 10. Acknowledgements
Thanks to Tomek Mrugalski, Bernie Volz and Gaurav Halwasia for their Thanks to Tomek Mrugalski, Bernie Volz, Gaurav Halwasia and Roberta
thorough review comments in the mailing list of DHC working group. Maglione for their thorough review comments in the mailing list of
DHC working group.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-radext-ipv6-access] [I-D.ietf-radext-ipv6-access]
Dec, W., Sarikaya, B., and G. Zorn, "RADIUS attributes for Dec, W., Sarikaya, B., and G. Zorn, "RADIUS attributes for
IPv6 Access Networks", draft-ietf-radext-ipv6-access-13 IPv6 Access Networks", draft-ietf-radext-ipv6-access-13
(work in progress), October 2012. (work in progress), October 2012.
skipping to change at page 9, line 18 skipping to change at page 9, line 26
[RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration [RFC6334] 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",
RFC 6334, August 2011. RFC 6334, August 2011.
Authors' Addresses Authors' Addresses
Leaf Y. Yeh Leaf Y. Yeh
Huawei Technologies Huawei Technologies
P. R. China P. R. China
Email: leaf.y.yeh@huawei.com Email: leaf.yeh.sdo@gmail.com
Mohamed Boucadair Mohamed Boucadair
France Telecom France Telecom
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Ted Lemon Ted Lemon
Nominum, Inc Nominum, Inc
USA USA
 End of changes. 28 change blocks. 
45 lines changed or deleted 52 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/