draft-ietf-dhc-dhcpv6-radius-opt-06.txt   draft-ietf-dhc-dhcpv6-radius-opt-07.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: July 8, 2013 France Telecom Expires: August 7, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
January 4, 2013 February 3, 2013
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-06 draft-ietf-dhc-dhcpv6-radius-opt-07
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 40 skipping to change at page 1, line 40
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 July 8, 2013. This Internet-Draft will expire on August 7, 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 20 skipping to change at page 2, line 20
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 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 8
6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 8 6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 8
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 8 7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8 8. Security Considerations . . . . . . . . . . . . . . . . . . . 9
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
skipping to change at page 6, line 50 skipping to change at page 6, line 50
DHCPv6 messages DHCPv6 messages DHCPv6 messages DHCPv6 messages
Figure 2: Network scenario and message sequence when employing DHCPv6 Figure 2: Network scenario and message sequence when employing DHCPv6
RADIUS option in PPPoE access RADIUS option in PPPoE access
If the authentication or the authorization through RADIUS fails, the If the authentication or the authorization through RADIUS fails, the
associated message sequences will stop. The NAS acting as the DHCPv6 associated message sequences will stop. The NAS acting as the DHCPv6
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 RADIUS attributes through RADIUS passes, the NAS MUST store the information indicated
received in the Access-Accept message from the RADIUS server during in the RADIUS attributes received in the Access-Accept message from
the whole session. After receiving RENEW (5) message from the DHCPv6 the RADIUS server during the whole session. How the NAS manages
client, the NAS SHOULD NOT initiate a new Access-Request/ these information during the RADIUS session is out of the scope of
Access-Accept message exchange with the RADIUS server; but after this document.
receiving REBIND (6) message from the DHCPv6 client, the NAS SHOULD
initiate a new Access-Request/Access-Accept message exchange with the After receiving RENEW (5) message from the DHCPv6 client, the NAS
RADIUS server. SHOULD NOT initiate a new Access-Request/Access-Accept message
exchange with the RADIUS server; but after receiving REBIND (6)
message from the DHCPv6 client, the NAS SHOULD initiate a new Access-
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 serve. in the Access-Accept message from the RADIUS serve.
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
skipping to change at page 9, line 40 skipping to change at page 9, line 48
Thanks to Tomek Mrugalski, Bernie Volz, Gaurav Halwasia and Roberta Thanks to Tomek Mrugalski, Bernie Volz, Gaurav Halwasia and Roberta
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. DHC working group.
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., Zorn, G., Miles, D., and B.
IPv6 Access Networks", draft-ietf-radext-ipv6-access-13 Lourdelet, "RADIUS attributes for IPv6 Access Networks",
(work in progress), October 2012. draft-ietf-radext-ipv6-access-15 (work in progress),
January 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. 7 change blocks. 
16 lines changed or deleted 20 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/