draft-ietf-dhc-dhcpv6-radius-opt-02.txt   draft-ietf-dhc-dhcpv6-radius-opt-03.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 15, 2013 France Telecom Expires: April 25, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
October 12, 2012 October 22, 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-02 draft-ietf-dhc-dhcpv6-radius-opt-03
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 to 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. 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 15, 2013. This Internet-Draft will expire on April 25, 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 5, line 45 skipping to change at page 5, line 45
| |<--Relay-Reply -------------| | |<--Relay-Reply -------------|
|<--Reply-------------------| | |<--Reply-------------------| |
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
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 authorization through RADIUS fails, the associated message If the authorization through RADIUS fails, the associated message
sequences will stop. The DHCPv6 relay will not forward the message sequences will stop. The NAS acting as the DHCPv6 relay agent will
from the client to the server. After receiving RENEW (5) message not forward the message received from the client to the server.
from the DHCPv6 client, NAS does not have to initiate a new Access- After receiving RENEW (5) message from the DHCPv6 client, the NAS
Request/Access message exchange with the RADIUS server; but after does not have to initiate a new Access-Request/Access message
receiving REBIND (6) message from the DHCPv6 client, NAS has to exchange with the RADIUS server; but after receiving REBIND (6)
initiate a new Access-Request/Access message exchange with the RADIUS message from the DHCPv6 client, the NAS has to initiate a new Access-
server. Request/Access message exchange with the RADIUS server.
4. OPTION_RADIUS 4. OPTION_RADIUS
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
skipping to change at page 7, line 46 skipping to change at page 7, line 46
Expert comments from Bernie Volz and Tomek Mrugalski for the Expert comments from Bernie Volz and Tomek Mrugalski for the
discussion on the technology selection in the mailing list are discussion on the technology selection in the mailing list are
appreciated. 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., Zorn, G., Miles, D., and B. Dec, W., Sarikaya, B., and G. Zorn, "RADIUS attributes for
Lourdelet, "RADIUS attributes for IPv6 Access Networks", IPv6 Access Networks", draft-ietf-radext-ipv6-access-13
draft-ietf-radext-ipv6-access-11 (work in progress), (work in progress), October 2012.
August 2012.
[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
IPv6 (DHCPv6)", RFC 3315, July 2003. IPv6 (DHCPv6)", RFC 3315, July 2003.
[RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol
(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.
[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.
[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
(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. 9 change blocks. 
24 lines changed or deleted 23 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/