draft-ietf-dhc-dhcpv6-radius-opt-03.txt   draft-ietf-dhc-dhcpv6-radius-opt-04.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: April 25, 2013 France Telecom Expires: May 9, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
October 22, 2012 November 5, 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-03 draft-ietf-dhc-dhcpv6-radius-opt-04
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 to 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 NAS acts as DHCPv6 relay
agent and RADIUS client simultaneously in this document. 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 April 25, 2013. This Internet-Draft will expire on May 9, 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 15 skipping to change at page 2, line 15
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
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. OPTION_RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 8
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 . . . . . . . . . . . . . . . . . . . . . . . . 9
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], 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.
skipping to change at page 6, line 5 skipping to change at page 6, line 5
If the authorization through RADIUS fails, the associated message If the authorization through RADIUS fails, the associated message
sequences will stop. The NAS acting as the DHCPv6 relay agent will sequences will stop. The NAS acting as the DHCPv6 relay agent will
not forward the message received from the client to the server. not forward the message received from the client to the server.
After receiving RENEW (5) message from the DHCPv6 client, the NAS After receiving RENEW (5) message from the DHCPv6 client, the NAS
does not have to initiate a new Access-Request/Access message does not have to initiate a new Access-Request/Access message
exchange with the RADIUS server; but after receiving REBIND (6) exchange with the RADIUS server; but after receiving REBIND (6)
message from the DHCPv6 client, the NAS has to initiate a new Access- message from the DHCPv6 client, the NAS has to initiate a new Access-
Request/Access message exchange with the RADIUS server. Request/Access message exchange with the RADIUS server.
4. OPTION_RADIUS 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-length | | OPTION_RADIUS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| option-data (List of RADIUS Attributes) | option-data (List of RADIUS Attributes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code TBD option-code TBD
option-length Length of the option-data in Octets option-len Length of the option-data in Octets
option-data One or a list of RADIUS Attributes option-data List of one or more RADIUS Attributes
The option-data of OPTION_RADIUS is one or a list of 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. As the same method in [RFC4014], only the attributes listed server. Only the attributes listed in the IANA Registry of 'RADIUS
in the table below may be included in the OPTION_RADIUS. Attributes Permitted in the DHCPv6 RADIUS option' Should be included
in the OPTION_RADIUS.
The RADIUS attributes listed in the below table are recommended as
the first batch of attributes in the IANA Registry of 'RADIUS
Attributes Permitted in the DHCPv6 RADIUS option'.
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 above table might have more attributes to join in the Note: The definition of the RADIUS attribute's 'Length' field in
future. section 5 of [RFC2865] is different from that of DHCPv6 option's
'option-len' field defined here.
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. The relay agent MUST silently discard OPTION_RADIUS OPTION_RADIUS.
if received.
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. The DHCPv6 server MUST NOT include silently discard this option.
OPTION_RADIUS in RELAY-REPL (13) messages.
7. Client Behavior 7. Client Behavior
OPTION_RADIUS option is only sent from the relay agents to the OPTION_RADIUS option is only sent from the relay agents to 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
The authors of this document request to assign a new DHCPv6 option This document requests to assign a new DHCPv6 option code for
code for OPTION_RADIUS. OPTION_RADIUS, and to create a new registry on the same assignments
page, which can be entitled as 'RADIUS Attributes Permitted in the
DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS
Attributes Types
(http://www.iana.org/assignments/radius-types/radius-types.xml) that
are permitted to be included in the DHCPv6 RADIUS option. The RADIUS
Attribute may be added to this list after IETF Review [RFC5226]. The
IETF Review Should include careful 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
Expert comments from Bernie Volz and Tomek Mrugalski for the Thanks to Tomek Mrugalski, Bernie Volz and Gaurav Halwasia for their
discussion on the technology selection in the mailing list are thorough review comments in the mailing list of DHC working group.
appreciated.
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 8, line 20 skipping to change at page 8, line 33
"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., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix
Attribute", RFC 4818, April 2007. Attribute", RFC 4818, April 2007.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual- [RFC6519] Maglione, R. and A. Durand, "RADIUS Extensions for Dual-
Stack Lite", RFC 6519, February 2012. Stack Lite", RFC 6519, February 2012.
11.2. Informative References 11.2. Informative References
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
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.
[RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol
(DHCP) Service for IPv6", RFC 3736, April 2004. (DHCP) Service for IPv6", RFC 3736, April 2004.
[RFC4014] Droms, R. and J. Schnizlein, "Remote Authentication
Dial-In User Service (RADIUS) Attributes Suboption for the
Dynamic Host Configuration Protocol (DHCP) Relay Agent
Information Option", RFC 4014, February 2005.
[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
 End of changes. 20 change blocks. 
33 lines changed or deleted 44 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/