draft-ietf-dhc-dhcpv6-radius-opt-09.txt   draft-ietf-dhc-dhcpv6-radius-opt-10.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: August 29, 2013 France Telecom Expires: October 5, 2013 France Telecom
February 25, 2013 April 3, 2013
RADIUS Option for DHCPv6 Relay Agent on the Broadband Access Servers RADIUS Option for DHCPv6 Relay Agent
draft-ietf-dhc-dhcpv6-radius-opt-09 draft-ietf-dhc-dhcpv6-radius-opt-10
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 August 29, 2013. This Internet-Draft will expire on October 5, 2013.
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 15 skipping to change at page 2, line 15
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 . . . . . . . . . . . . . . . . . . . . . 7 4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 7
5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 8 4.1. RADIUS attributes permitted in DHCPv6 RADIUS option . . . 7
6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 8 5. DHCPv6 Relay Agent Behavior . . . . . . . . . . . . . . . . . 8
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 8 6. DHCPv6 Server Behavior . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. DHCPv6 Client Behavior . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . 9 11.1. Normative References . . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . 10 11.2. Informative References . . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
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] and IPv6 prefix [RFC3633]. 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 the scenarios described in this document, the of AFTR [RFC6334]. In the scenarios described in this document, the
DHCPv6 server is deployed in the central part of an ISP network. DHCPv6 server is deployed 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 Network Access Server (NAS) to assign an IPv6 server authorizes the Network Access Server (NAS) to assign an IPv6
skipping to change at page 3, line 46 skipping to change at page 3, line 46
RADIUS attributes to the DHCPv6 server. RADIUS attributes to the DHCPv6 server.
2. Terminology and Language 2. Terminology and Language
This document specifies a new DHCPv6 option for the DHCPv6 Relay This document specifies a new DHCPv6 option for the DHCPv6 Relay
Agent to transfer the authorization information of RADIUS attributes Agent to transfer the authorization information of RADIUS attributes
received in the Access-Accept message from the RADIUS server to the received in the Access-Accept message from the RADIUS server to the
centralized DHCPv6 server. Definitions for terms and acronyms not centralized DHCPv6 server. Definitions for terms and acronyms not
specified in this document are defined in [RFC2865] and [RFC3315]. specified in this document are defined in [RFC2865] and [RFC3315].
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document, are to be interpreted as described in BCP 14, [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Network Scenarios 3. Network Scenarios
Figure 1 and Figure 2 show the typical network scenarios where the Figure 1 and Figure 2 show the typical network scenarios where the
communication mechanism introduced in this document is necessary. In communication mechanism introduced in this document is necessary. In
these scenarios, the centralized DHCPv6 server is not co-located with these scenarios, the centralized DHCPv6 server is not co-located with
the RADIUS server, but both of them are in the same administrative the RADIUS server, but both of them are in the same administrative
domain. The NAS acts as the DHCPv6 relay agent and the RADIUS client domain. The NAS acts as the DHCPv6 relay agent and the RADIUS client
simultaneously. Figure 1 shows the sequence of DHCPv6 and RADIUS simultaneously. Figure 1 shows the sequence of DHCPv6 and RADIUS
messages for IP over Ethernet (IPoE) access model, when the access messages for IP over Ethernet (IPoE) access model, when the access
loop adopts the direct Ethernet encapsulation. Figure 2 shows the loop adopts the direct Ethernet encapsulation. Figure 2 shows the
sequence of DHCPv6 and RADIUS messages for PPP over Ethernet (PPPoE) sequence of DHCPv6 and RADIUS messages for PPP over Ethernet (PPPoE)
access model. access model.
The mechanism introduced in this document is a generic mechanism, and
might also be employed in other network scenarios where the DHCPv6
relay agent and the RADIUS client locate in the same device.
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
|DHCPv6 | Access Model: | NAS | |Radius | |DHCPv6 | Access Model: | NAS | |RADIUS |
|Client | IPoE | | |Server | |Client | IPoE | | |Server |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
RADIUS Client/DHCPv6 Relay Agent
| | | | | |
|---Solicit---------------->| | |---Solicit---------------->| |
| |---Access-Request---------->| | |---Access-Request---------->|
| | | | | |
| |<--Access-Accept------------| | |<--Access-Accept------------|
| |(e.g. Delegated-IPv6-Prefix)| | |(e.g. Delegated-IPv6-Prefix)|
| | | | | |
DHCPv6 messages RADIUS messages DHCPv6 messages RADIUS messages
skipping to change at page 6, line 6 skipping to change at page 6, line 6
|<--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
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
|DHCPv6 | Access Model: | NAS | |Radius | |DHCPv6 | Access Model: | NAS | |RADIUS |
|Client | PPPoE | | |Server | |Client | PPPoE | | |Server |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
RADIUS Client/DHCPv6 Relay Agent
| | | | | |
|--PPP LCP Config-Request-->| | |--PPP LCP Config-Request-->| |
| |---Access-Request---------->| | |---Access-Request---------->|
| | | | | |
| |<--Access-Accept------------| | |<--Access-Accept------------|
|<----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
skipping to change at page 7, line 36 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. 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 DHCPv6 RADIUS option' SHOULD be included in
in the OPTION_RADIUS. the OPTION_RADIUS.
According to the network scenarios described in section 3, the
OPTION_RADIUS SHOULD appear in the RELAY-FORW (12) message relaying
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
DHCPv6 client.
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 the DHCPv6 RADIUS option'. New RADIUS attributes permitted in DHCPv6 RADIUS option'. New RADIUS attributes
attributes MAY be added to this list after the IETF Expert Review MAY be added to this list after the IETF Expert Review [RFC5226].
[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] 168 Framed-IPv6-Address [I-D.ietf-radext-ipv6-access]
[TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access] 169 DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access]
[TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access] 171 Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access]
[TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access] 172 Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access]
Note: The definition of the RADIUS attribute's 'Length' field in
section 5 of [RFC2865] includes the length of 'Type' and 'Length'
fields.
According to the network scenarios described in section 3, the Note: The RADIUS attribute's 'Length' defined in section 5 of
OPTION_RADIUS SHOULD appear in the RELAY-FORW (12) message relaying [RFC2865] includes the length of 'Type' and 'Length' fields.
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
DHCPv6 client.
5. Relay Agent Behavior 5. DHCPv6 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, for example,
Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123) Delegated-IPv6-Prefix-Pool (171), Stateful-IPv6-Address-Pool (172),
or Framed-IPv6-Address in the Access-Accept message replied from Delegated-IPv6-Prefix (123) or Framed-IPv6-Address (168) in the
RADIUS server are valid, the relay agent that supports OPTION_RADIUS Access-Accept message replied from RADIUS server are valid, the relay
SHOULD include these RADIUS attributes into the container option, agent that supports OPTION_RADIUS SHOULD include these RADIUS
OPTION_RADIUS. attributes into the OPTION_RADIUS one by one.
6. 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 SHOULD extract and interpret the relay agent, the DHCPv6 server that supports OPTION_RADIUS SHOULD
RADIUS attributes in the OPTION_RADIUS, and use that information in extract and interpret the RADIUS attributes in the OPTION_RADIUS, and
selecting configuration parameters for the requesting client. If the use that information in selecting configuration parameters for the
DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server MUST requesting client. If the DHCPv6 server does not support
silently discard this option. OPTION_RADIUS, the DHCPv6 server MUST silently discard this option.
7. Client Behavior 7. DHCPv6 Client Behavior
OPTION_RADIUS is only exchanged between the relay agents and 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
skipping to change at page 9, line 25 skipping to change at page 9, line 21
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, in the network scenarios described in the
section 3, NAS could always be regarded as a trusted network section 3, NAS could always be regarded as a trusted network
component in the real deployment. component in the real deployment.
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 assignment OPTION_RADIUS defined in section 4, and to create a new registry on
page, which can be entitled as 'RADIUS Attributes Permitted in the the same assignment page, which is entitled as 'RADIUS attributes
DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS permitted in DHCPv6 RADIUS option' defined in section 4.1. The new
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. New RADIUS are permitted to be included in the DHCPv6 RADIUS option. New RADIUS
attributes MAY be added to this list after the IETF Expert Review attributes MAY be added to this list after the IETF Expert Review
[RFC5226]. The IETF expert review SHOULD include careful [RFC5226]. The IETF expert review SHOULD include careful
consideration of the security implications of allowing the relay consideration of the security implications of allowing the relay
agent to include the RADIUS attribute being considered for addition agent to include the RADIUS attribute being considered for addition
to this registry. to this registry.
10. Acknowledgements 10. Acknowledgements
skipping to change at page 10, line 4 skipping to change at page 9, line 46
Maglione for their thorough review comments in the mailing list of Maglione for their thorough review comments in the mailing list of
DHC working group, to Ted Lemon for his continuous encouragement and DHC working group, to Ted Lemon for his continuous encouragement and
technical guidance. technical guidance.
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., Zorn, G., Miles, D., and B. Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B.
Lourdelet, "RADIUS attributes for IPv6 Access Networks", Lourdelet, "RADIUS attributes for IPv6 Access Networks",
draft-ietf-radext-ipv6-access-15 (work in progress), draft-ietf-radext-ipv6-access-16 (work in progress),
January 2013. February 2013.
[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., Bound, J., Volz, B., Lemon, T., Perkins, C.,
and M. Carney, "Dynamic Host Configuration Protocol for and M. Carney, "Dynamic Host Configuration Protocol for
 End of changes. 24 change blocks. 
56 lines changed or deleted 64 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/