draft-ietf-dhc-dhcpv6-radius-opt-00.txt   draft-ietf-dhc-dhcpv6-radius-opt-01.txt 
DHC Working Group L. Yeh, Ed. DHC Working Group L. Yeh, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track M. Boucadair Intended status: Standards Track M. Boucadair
Expires: November 8, 2012 France Telecom Expires: January 31, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
May 7, 2012 July 30, 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-00 draft-ietf-dhc-dhcpv6-radius-opt-01
Abstract Abstract
The DHCPv6 RADIUS option provides a communication mechanism between The DHCPv6 RADIUS option provides a communication mechanism between
relay agent and the server. This mechanism can help the centralized relay agent and the server. This mechanism can help the centralized
DHCPv6 server to select the right configuration for the client based DHCPv6 server to select the right configuration for the client based
on the authorization information received from a separate RADIUS on the authorization information received from a separate RADIUS
server which is not located at the same place of DHCPv6 server in the server which is not located at the same place of DHCPv6 server in the
cases where the NAS acts as DHCPv6 relay agent and RADIUS client cases where the NAS acts as DHCPv6 relay agent and RADIUS client
simultaneously. simultaneously.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 November 8, 2012. This Internet-Draft will expire on January 31, 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 22 skipping to change at page 2, line 22
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. OPTION_RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. OPTION_RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 6 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . . . . . 7 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
11.1. Normative References . . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . . 8
11.2. Informative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
DHCPv6 provides a mechanism that allows the server to assign or DHCPv6 provides a mechanism that allows the server to assign or
delegate both stateful and stateless configuration parameters to the delegate both stateful and stateless configuration parameters to the
clients. The stateful configuration parameters include IPv6 address clients. The stateful configuration parameters include IPv6 address
[RFC3315], IPv6 prefix [RFC3633], and etc. The stateless [RFC3315], IPv6 prefix [RFC3633], and etc. The stateless
configuration parameters [RFC3736] include, for example, DNS configuration parameters [RFC3736] include, for example, DNS
[RFC3646]. The DHCPv6 server is typically deployed in the central [RFC3646]. The DHCPv6 server is typically deployed in the central
part of an ISP network. part of an ISP network.
RADIUS [RFC2865], an essentially stateless protocol, is used widely RADIUS [RFC2865], an essentially stateless protocol, is used widely
as the centralized authentication, authorization and user management as the centralized authentication, authorization and user management
mechanism for the service provision in Broadband access network. mechanism for the service provision in Broadband access network.
[RFC3162], [RFC4818] and [ietf-radext-ipv6-access-06] specify [RFC3162], [RFC4818] and [ietf-radext-ipv6-access-10] specify
attributes that supports the provision of service for IPv6 access. attributes that supports the provision of service for IPv6 access.
RADIUS authorizes that the NAS assigns an IPv6 address or prefix from RADIUS authorizes the NAS to assign an IPv6 address or prefix from
the indicated pool, or assigns an IPv6 address or prefix with an the indicated pool, or to assign an IPv6 address or prefix with an
explicitly indicated value in the attributes for the subscribers. explicitly indicated value in the attributes for the subscribers.
These mechanisms work well in the deployment scenario where the NAS These mechanisms work well in the deployment scenario where the NAS
acts as the distributed DHCPv6 server. In this case the NAS responds acts as the distributed DHCPv6 server. In this case the NAS responds
as the indication conveyed by the attributes in the Access-Accept as the indication conveyed by the attributes in the Access-Accept
message from the RADIUS server. These mechanisms also work in the message from the RADIUS server. These mechanisms also work in the
scenario where the centralized DHCPv6 server is co-located with the scenario where the centralized DHCPv6 server is co-located with the
RADIUS server, where they can share the same database of the users. RADIUS server, where they can share the same database of the users.
But when the NAS acts as the relay agent and RADIUS client But when the NAS acts as the relay agent and RADIUS client
simultaneously, and the centralized DHCPv6 server is not located in simultaneously, and the centralized DHCPv6 server is not located in
skipping to change at page 6, line 19 skipping to change at page 6, line 19
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-length | | OPTION_RADIUS | option-length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RADIUS Attributes... | option-data (List of RADIUS Attributes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code TBD option-code TBD
option-length Length of the option-data in Octets option-length Length of the option-data in Octets
option-data One or a list of RADIUS Attributes option-data One or a list of RADIUS Attributes
The option-data of OPTION_RADIUS is one or a list of RADIUS The option-data of OPTION_RADIUS is one or a list of RADIUS
attributes received in the Access-Accept message from the RADIUS attributes received in the Access-Accept message from the RADIUS
server. As the same method in [RFC4014], only the attributes listed server. As the same method in [RFC4014], only the attributes listed
in the table below may be included in the OPTION_RADIUS. in the table below may be included in the OPTION_RADIUS.
Type Code Attribute Reference Type Code Attribute Reference
26 Vendor-Specific [RFC2865] 26 Vendor-Specific [RFC2865]
88 Framed-Pool [RFC2869] 88 Framed-Pool [RFC2869]
123 Delegated-IPv6-Prefix [RFC4818] 123 Delegated-IPv6-Prefix [RFC4818]
[TBD] Framed-IPv6-Address [ietf-radext-ipv6-access-06] [TBD] Framed-IPv6-Address [ietf-radext-ipv6-access-10]
[TBD] Stateful-IPv6-Address-Pool [ietf-radext-ipv6-access-10]
[TBD] Delegated-IPv6-Prefix-Pool [ietf-radext-ipv6-access-10]
[TBD] DNS-Server-IPv6-Address [ietf-radext-ipv6-access-10]
Note: The above table might have more attributes in the future. Note: The above table might have more attributes in the future.
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
message. When the value in the attributes of Framed-Pool (88), (or (12) message. When the value in the attributes of Framed-Pool (88)
Stateful-IPv6-Address-Pool, Delegated-IPv6-Prefix-Pool,) Delegated- (or Stateful-IPv6-Address-Pool, Delegated-IPv6-Prefix-Pool),
IPv6-Prefix (123) and Framed-IPv6-Address in the Access-Accept Delegated-IPv6-Prefix (123) and Framed-IPv6-Address in the Access-
message replied from RADIUS server are valid, the relay agent that Accept message replied from RADIUS server are valid, the relay agent
supports OPTION_RADIUS SHOULD include these RADIUS attributes in the that supports OPTION_RADIUS SHOULD include these RADIUS attributes in
container option, OPTION_RADIUS. The relay agent MUST ignore the container option, OPTION_RADIUS. The relay agent MUST ignore
OPTION_RADIUS if received. OPTION_RADIUS if received.
6. Server Behavior 6. Server Behavior
Upon receipt of the RELAY-FORW message with OPTION_RADIUS from a Upon receipt of the RELAY-FORW 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 DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server
SHOULD ignore this option. The DHCPv6 server MUST NOT include SHOULD ignore this option. The DHCPv6 server MUST NOT include
skipping to change at page 8, line 40 skipping to change at page 8, line 44
RFC 3162, August 2001. RFC 3162, August 2001.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. December 2003.
[RFC3646] Droms, R., "DNS Configuration options for Dynamic Host [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
December 2003. December 2003.
[ietf-radext-ipv6-access-06] [ietf-radext-ipv6-access-10]
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",
July 2011. July 2011.
Authors' Addresses Authors' Addresses
Leaf Y. Yeh (editor) Leaf Y. Yeh (editor)
Huawei Technologies Huawei Technologies
P. R. China P. R. China
 End of changes. 11 change blocks. 
22 lines changed or deleted 25 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/