draft-ietf-dhc-dhcpv6-radius-opt-12.txt   draft-ietf-dhc-dhcpv6-radius-opt-13.txt 
DHC Working Group L. Yeh DHC Working Group L. Yeh
Internet-Draft Freelancer Technologies Internet-Draft Freelancer Technologies
Intended status: Standards Track M. Boucadair Intended status: Standards Track M. Boucadair
Expires: November 19, 2013 France Telecom Expires: January 6, 2014 France Telecom
May 18, 2013 July 5, 2013
RADIUS Option for DHCPv6 Relay Agent RADIUS Option for DHCPv6 Relay Agent
draft-ietf-dhc-dhcpv6-radius-opt-12 draft-ietf-dhc-dhcpv6-radius-opt-13
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 the DHCPv6 relay authorization and identification information between the DHCPv6 relay
agent and the DHCPv6 server. This mechanism is meant for the agent and the DHCPv6 server. This mechanism is meant for the
centralized DHCPv6 server to select the right configuration for the centralized DHCPv6 server to select the right configuration for the
requesting DHCPv6 client based on the authorization information requesting DHCPv6 client based on the authorization information
received from the RADIUS server, which is not co-located with the received from the RADIUS server, which is not co-located with the
DHCPv6 server. The Network Access Server (NAS) acts as DHCPv6 relay DHCPv6 server. The Network Access Server (NAS) acts as DHCPv6 relay
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 19, 2013. This Internet-Draft will expire on January 6, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 21 skipping to change at page 2, line 21
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 . . . . . . . . . . . . . . . . . . . . . 7 4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 7
4.1. RADIUS attributes permitted in DHCPv6 RADIUS option . . . 8 4.1. RADIUS attributes permitted in DHCPv6 RADIUS option . . . 8
5. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . 8 5. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . 8
6. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 8 6. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 8
7. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 8 7. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . . 10 11.1. Normative References . . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . . 10 11.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
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
skipping to change at page 7, line 12 skipping to change at page 7, line 12
the DHCPv6 server. If the authentication or the authorization the DHCPv6 server. If the authentication or the authorization
through RADIUS passes, the NAS MUST store the information indicated through RADIUS passes, the NAS MUST store the information indicated
in the RADIUS attributes received in the Access-Accept message from in the RADIUS attributes received in the Access-Accept message from
the RADIUS server during the whole session. How the NAS manages the RADIUS server during the whole session. How the NAS manages
these information during the RADIUS session is out of the scope of these information during the RADIUS session is out of the scope of
this document. this document.
After receiving RENEW (5) message from the DHCPv6 client, the NAS After receiving RENEW (5) message from the DHCPv6 client, the NAS
SHOULD NOT initiate a new Access-Request/Access-Accept message SHOULD NOT initiate a new Access-Request/Access-Accept 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 SHOULD initiate a new Access- message from the DHCPv6 client, the NAS MUST initiate a new Access-
Request/Access-Accept message exchange with the RADIUS server. Request/Access-Accept message exchange with the RADIUS server.
4. DHCPv6 RADIUS option 4. DHCPv6 RADIUS option
The OPTION_RADIUS is a DHCPv6 option used by the DHCPv6 relay agent The OPTION_RADIUS is a DHCPv6 option used by the DHCPv6 relay agent
to carry the authorization information of RADIUS attributes received to carry the authorization information of RADIUS attributes received
in the Access-Accept message from the RADIUS server. in the Access-Accept message from the RADIUS server.
The format of the OPTION_RADIUS option is defined as follows: The format of the OPTION_RADIUS option is defined as follows:
skipping to change at page 7, line 38 skipping to change at page 7, line 38
| 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. The format of RADIUS attributes is defined in section 5 of server. The format of RADIUS attributes is defined in section 5 of
[RFC2865]. The OPTION_RADIUS can only contain the RADIUS attributes [RFC2865] as well as sections 2.1 and 2.2 of [RFC6929]. If multiple
listed in the IANA Registry of 'RADIUS attributes permitted in DHCPv6 attributes with the same type (including the Long Extended type
RADIUS option'. defined in sections 2.2 of [RFC6929]) are present, the order of
attributes with the same type MUST be the same as that received from
the RADIUS server. The OPTION_RADIUS can only contain the RADIUS
attributes listed in the IANA Registry of 'RADIUS attributes
permitted in DHCPv6 RADIUS option'.
According to the network scenarios described in section 3, the According to the network scenarios described in section 3, the
OPTION_RADIUS SHOULD appear in the RELAY-FORW (12) message relaying OPTION_RADIUS should appear in the RELAY-FORW (12) message relaying
SOLICIT (1), REQUEST (3) and REBIND (6) from the DHCPv6 client, and SOLICIT (1), REQUEST (3) and REBIND (6) from the DHCPv6 client, and
MAY appear in the RELAY-FORW (12) relaying any other message from the may appear in the RELAY-FORW (12) relaying any other message from the
DHCPv6 client. DHCPv6 client.
4.1. RADIUS attributes permitted in DHCPv6 RADIUS option 4.1. RADIUS attributes permitted in DHCPv6 RADIUS option
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 DHCPv6 RADIUS option'. New RADIUS attributes attributes permitted in DHCPv6 RADIUS option'. New RADIUS attributes
can be added to this list after Expert Review [RFC5226]. can be added to this list after Expert Review [RFC5226].
Type Code Attribute Reference Type Code Attribute Reference
skipping to change at page 8, line 26 skipping to change at page 8, line 26
168 Framed-IPv6-Address [RFC6911] 168 Framed-IPv6-Address [RFC6911]
169 DNS-Server-IPv6-Address [RFC6911] 169 DNS-Server-IPv6-Address [RFC6911]
171 Delegated-IPv6-Prefix-Pool [RFC6911] 171 Delegated-IPv6-Prefix-Pool [RFC6911]
172 Stateful-IPv6-Address-Pool [RFC6911] 172 Stateful-IPv6-Address-Pool [RFC6911]
Note: The RADIUS attribute's 'Length' defined in section 5 of Note: The RADIUS attribute's 'Length' defined in section 5 of
[RFC2865] includes the length of 'Type' and 'Length' fields. [RFC2865] includes the length of 'Type' and 'Length' fields.
5. DHCPv6 Relay Agent Behavior 5. DHCPv6 Relay Agent Behavior
The DHCPv6 relay agent MAY include OPTION_RADIUS in the RELAY-FORW If the Relay Agent is configured to send OPTION_RADIUS, and the
(12) message. When the value in the attributes, for example, Access-Accept message from the RADIUS server contained RADIUS
Delegated-IPv6-Prefix-Pool (171), Stateful-IPv6-Address-Pool (172), attributes permitted for use in OPTION_RADIUS, the Relay Agent MUST
Delegated-IPv6-Prefix (123) or Framed-IPv6-Address (168) in the include OPTION_RADIUS in the RELAY-FORW (12) message. The DHCPv6
Access-Accept message replied from RADIUS server are valid, the relay relay agent includes the permitted RADIUS attributes into
agent that supports OPTION_RADIUS SHOULD include these RADIUS OPTION_RADIUS one by one; if multiple attributes with the same type
attributes into the OPTION_RADIUS one by one. are present, the order of attributes with the same type MUST be the
same as that received from the RADIUS server.
6. DHCPv6 Server Behavior 6. DHCPv6 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 that supports OPTION_RADIUS SHOULD relay agent, the DHCPv6 server that supports OPTION_RADIUS SHOULD
extract and interpret the RADIUS attributes in the OPTION_RADIUS, and extract and interpret the RADIUS attributes in the OPTION_RADIUS, and
use that information in selecting configuration parameters for the use that information in selecting configuration parameters for the
requesting client. If the DHCPv6 server does not support requesting client. If the DHCPv6 server does not support
OPTION_RADIUS, the DHCPv6 server MUST silently discard this option. OPTION_RADIUS, the DHCPv6 server MUST silently discard this option.
skipping to change at page 9, line 11 skipping to change at page 9, line 11
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], section 11 of [RFC6929].
The mechanism described in this document may introduce new attack The mechanism described in this document may introduce new attack
vector against the DHCPv6 server in case the DHCPv6 relay agent is vector against the DHCPv6 server in case the DHCPv6 relay agent is
compromised. By forging the RADIUS attributes contained in the compromised. By forging the RADIUS attributes contained in the
OPTION_RADIUS of the RELAY-FORW (12) messages, the attacker may OPTION_RADIUS of the RELAY-FORW (12) messages, the attacker may
influence the parameter assignment on the DHCPv6 server for the influence the parameter assignment on the DHCPv6 server for the
DHCPv6 clients. However, in the network scenarios described in the DHCPv6 clients. However, as those network scenarios described in the
section 3, NAS could always be regarded as a trusted network section 3, NAS always belongs to the same administrative domain of
component in the real deployment. the DHCPv6 server in the real deployment.
Network administrators should be aware that although RADIUS messages Network administrators should be aware that although RADIUS messages
are encrypted, DHCPv6 messages can not be encrypted. It is possible are encrypted, DHCPv6 messages are always not encrypted. It is
that some RADIUS vendor-specific attributes might contain the possible that some RADIUS vendor-specific attributes might contain
sensitive or confidential information. Network administrators are the sensitive or confidential information. Network administrators
strongly advised to prevent including such information into DHCPv6 are strongly advised to prevent including such information into
messages. DHCPv6 messages.
If the use of vendor-specific attributes with confidential content is
required, administrators are advised to use IPsec with encryption to
protect the confidentiality of the RADIUS attributes. Relay agents
and servers implementing this specification MUST support the use of
IPsec ESP with encryption in transport mode according to section
3.1.1 of [RFC4303] and section 21.1 of [RFC3315].
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 defined in section 4, and to create a new registry on OPTION_RADIUS defined in section 4, and to create a new registry on
the same assignment page, which is entitled as 'RADIUS attributes the same assignment page, which is entitled as 'RADIUS attributes
permitted in DHCPv6 RADIUS option' defined in section 4.1. The new permitted in DHCPv6 RADIUS option' defined in section 4.1. The new
registry will enumerate the RADIUS Attributes Types registry will enumerate the RADIUS 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 are permitted to be included in the DHCPv6 RADIUS option. The
skipping to change at page 10, line 20 skipping to change at page 10, line 27
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., 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.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, December 2005.
[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 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. 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.
[RFC6911] Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B. [RFC6911] Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B.
Lourdelet, "RADIUS Attributes for IPv6 Access Networks", Lourdelet, "RADIUS Attributes for IPv6 Access Networks",
RFC 6911, April 2013. RFC 6911, April 2013.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
Service (RADIUS) Protocol Extensions", RFC 6929,
April 2013.
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
 End of changes. 14 change blocks. 
27 lines changed or deleted 46 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/