draft-ietf-dhc-dhcpv6-radius-opt-13.txt   draft-ietf-dhc-dhcpv6-radius-opt-14.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: January 6, 2014 France Telecom Expires: January 30, 2014 France Telecom
July 5, 2013 July 29, 2013
RADIUS Option for DHCPv6 Relay Agent RADIUS Option for DHCPv6 Relay Agent
draft-ietf-dhc-dhcpv6-radius-opt-13 draft-ietf-dhc-dhcpv6-radius-opt-14
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 DHCPv6 relay
agent and the DHCPv6 server. This mechanism is meant for the agent and DHCPv6 server. This architecture assumes that the Network
centralized DHCPv6 server to select the right configuration for the Access Server(NAS) acts as both DHCPv6 relay agent and RADIUS client.
requesting DHCPv6 client based on the authorization information When receiving messages from the DHCPv6 clients, the NAS consults the
received from the RADIUS server, which is not co-located with the RADIUS server and adds the RADIUS response when forwarding the DHCPv6
DHCPv6 server. The Network Access Server (NAS) acts as DHCPv6 relay client's messages to the DHCPv6 server. The DHCPv6 server then uses
agent and RADIUS client simultaneously in this document. that additional information to generate appropriate response to the
DHCPv6 client's requests.
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 January 6, 2014. This Internet-Draft will expire on January 30, 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 24 skipping to change at page 2, line 25
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 . . . . . . . . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . 11
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
[RFC3315] and IPv6 prefix [RFC3633]. 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 service provision in
in Broadband access network. [RFC3162], [RFC4818], [RFC6519] and Broadband access network. [RFC3162], [RFC4818], [RFC6519] and
[RFC6911] specified attributes that support the service provision for [RFC6911] specified the attributes that support the service provision
IPv6-only and IPv6-transition access. RADIUS server authorizes the for IPv6-only and IPv6-transition access. The RADIUS server
Network Access Server (NAS) to assign an IPv6 address or prefix from authorizes the Network Access Server (NAS) to assign an IPv6 address
the indicated pool, or to assign an IPv6 address or prefix with an or prefix from the indicated pool, or to assign an IPv6 address or
explicitly indicated value, and other configuration parameters as per prefix with an explicitly indicated value, and other configuration
the attributes for the subscribers. parameters as per the attributes for the subscribers.
These mechanisms work well in the deployment scenarios where the NAS When the NAS acts as distributed DHCPv6 server and RADIUS client
acts as the distributed DHCPv6 server. In that case the NAS directly simultaneously, it communicates with RADIUS server after receiving
responds the DHCPv6 messages as per the indication conveyed by the request from DHCPv6 client. Upon receiving the Access-Accept message
attributes in the Access-Accept message from the RADIUS server. from the RADIUS server, the NAS then responds to the DHCPv6 client's
These mechanisms might also work well in the scenario where the requests per the associated authorization information indicated by
centralized DHCPv6 server is co-located with the RADIUS server, where the RADIUS attributes in the Access-Accept message. When NAS acts as
they can share the same database of the users. But when the NAS acts DHCPv6 relay agent and RADIUS client simultaneously, and the
as the relay agent and RADIUS client simultaneously, and the centralized DHCPv6 server is co-located with the RADIUS server, they
centralized DHCPv6 server is not located in the same place as the may share the same database of the users; but when the centralized
RADIUS server, a new communication mechanism is needed for the relay DHCPv6 server is not located in the same place as the RADIUS server,
agent to transfer the authorization information indicated by the a new communication mechanism is needed for the DHCPv6 relay agent to
RADIUS attributes to the DHCPv6 server. transfer the authorization information indicated by the 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 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 7, line 11 skipping to change at page 7, line 11
relay agent will not forward the message received from the client to relay agent will not forward the message received from the client to
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. After receiving REBIND (6) message
message from the DHCPv6 client, the NAS MUST initiate a new Access- from the DHCPv6 client, the NAS MUST initiate a new Access-Request/
Request/Access-Accept message exchange with the RADIUS server. Access-Accept message exchange with the RADIUS server, unless RADIUS
capability is disabled on the NAS.
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:
0 1 2 3 0 1 2 3
 End of changes. 8 change blocks. 
35 lines changed or deleted 38 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/