draft-ietf-dhc-dhcpv6-radius-opt-01.txt   draft-ietf-dhc-dhcpv6-radius-opt-02.txt 
DHC Working Group L. Yeh, Ed. 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: January 31, 2013 France Telecom Expires: April 15, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
July 30, 2012 October 12, 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-01 draft-ietf-dhc-dhcpv6-radius-opt-02
Abstract Abstract
The DHCPv6 RADIUS option provides a communication mechanism between The DHCPv6 RADIUS option provides a mechanism to exchange
relay agent and the server. This mechanism can help the centralized authorization and identification information between relay agent and
DHCPv6 server to select the right configuration for the client based server. This mechanism is meant to the centralized DHCPv6 server to
on the authorization information received from a separate RADIUS select the right configuration for the requesting client based on the
server which is not located at the same place of DHCPv6 server in the authorization information received from the RADIUS server, which is
cases where the NAS acts as DHCPv6 relay agent and RADIUS client not co-located with the DHCPv6 server. NAS acts as DHCPv6 relay
simultaneously. 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 January 31, 2013. This Internet-Draft will expire on April 15, 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 2, line 22 skipping to change at page 2, line 22
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. OPTION_RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. OPTION_RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 6 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 6
6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . . 7
11.2. Informative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
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], and etc. The stateless [RFC3315], IPv6 prefix [RFC3633], etc. The stateless configuration
configuration parameters [RFC3736] include, for example, DNS parameters [RFC3736] include, for example, DNS [RFC3646], or a FQDN
[RFC3646]. The DHCPv6 server is typically deployed in the central of AFTR [RFC6334]. In this document, the DHCPv6 server is deployed
part of an ISP network. in the central part of an ISP network.
RADIUS [RFC2865], an essentially stateless protocol, is used widely RADIUS [RFC2865] is widely used as the centralized authentication,
as the centralized authentication, authorization and user management authorization and user management mechanism for the service provision
mechanism for the service provision in Broadband access network. in Broadband access network. [RFC3162], [RFC4818], [RFC6519] and
[RFC3162], [RFC4818] and [ietf-radext-ipv6-access-10] specify [I-D.ietf-radext-ipv6-access] specified attributes that support the
attributes that supports the provision of service for IPv6 access. service provision for IPv6-only and IPv6-transition access. RADIUS
RADIUS authorizes the NAS to assign an IPv6 address or prefix from server authorizes the NAS to assign an IPv6 address or prefix from
the indicated pool, or to assign an IPv6 address or prefix with an the indicated pool, or to assign an IPv6 address or prefix with an
explicitly indicated value in the attributes for the subscribers. explicitly indicated value, and other configuration parameters as per
the attributes for the subscribers.
These mechanisms work well in the deployment scenario where the NAS These mechanisms work well in the deployment scenarios where the NAS
acts as the distributed DHCPv6 server. In this case the NAS responds acts as the distributed DHCPv6 server. In that case the NAS directly
as the indication conveyed by the attributes in the Access-Accept responds the DHCPv6 messages as per the indication conveyed by the
message from the RADIUS server. These mechanisms also work in the attributes in the Access-Accept message from the RADIUS server.
scenario where the centralized DHCPv6 server is co-located with the These mechanisms might also work well in the scenario where the
RADIUS server, where they can share the same database of the users. centralized DHCPv6 server is co-located with the RADIUS server, where
But when the NAS acts as the relay agent and RADIUS client they can share the same database of the users. But when the NAS acts
simultaneously, and the centralized DHCPv6 server is not located in as the relay agent and RADIUS client simultaneously, and the
the same place as the RADIUS server, a new communication mechanism is centralized DHCPv6 server is not located in the same place as the
needed for the relay agent to transfer the authorization information RADIUS server, a new communication mechanism is needed for the relay
indicated by the RADIUS attributes to the DHCPv6 server. agent to 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 DHCPv6 option for the distributed Relay This document specifies a DHCPv6 option for the distributed 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 to the centralized DHCPv6 received in the Access-Accept message to the centralized DHCPv6
server. This document should be read in conjunction with the server. Definitions for terms and acronyms not specified in this
following specifications: [RFC2865], [RFC2869], [RFC3315] and document are defined in [RFC2865] and [RFC3315].
[RFC4818]. These specifications will help the reader to understand
how DHCPv6 and RADIUS work together to provide IPv6 service.
Definitions for terms and acronyms not specified in this document are
defined in [RFC2865], [RFC2869], [RFC3315] and [RFC4818].
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this
document, are to be interpreted as described in BCP 14, [RFC2119]. document, are to be interpreted as described in BCP 14, [RFC2119].
3. Network Scenarios 3. Network Scenarios
Figure 1 and Figure 2 shows the typical network scenarios where the Figure 1 and Figure 2 shows 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 relay agent and the RADIUS client domain. The NAS acts as the 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 IPoE access mode. Figure 2 shows the sequence of DHCPv6 messages for IPoE access mode. Figure 2 shows the sequence of DHCPv6
and RADIUS messages for PPPoE access mode. and RADIUS messages for PPPoE access mode.
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
|DHCPv6 | Access Mode: | NAS | |Radius | |DHCPv6 | Access Mode: | NAS | |Radius |
|Client | IPoE |(DHCPv6| |Server | |Client | IPoE | | |Server |
| | | Relay)| | |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| | | | | |
|---Solicit---------------->| | |---Solicit---------------->| |
|---Access-Request---------->| | |---Access-Request---------->|
|<--Access-Accept------------| | | |
| (e.g. Framed-Pool) | |<--Access-Accept------------|
| (e.g. Delegated-IPv6-Prefix) | |(e.g. Delegated-IPv6-Prefix)|
| | |
DHCPv6 messages RADIUS messages DHCPv6 messages RADIUS messages
+-------+
| +-------+ |DHCPv6 |
| |DHCPv6 | |Server |
| |Server | +-------+
| | | | | |
| +-------+ | |---Relay-Forward----------->|
|---Relay-Forward----------->| | | (OPTION_RADIUS) |
| (OPTION_RADIUS) | | |
| | |<--Relay-Reply -------------|
|<--Relay-Reply -------------| |<--Advertise---------------| |
|<--Advertise---------------| | (e.g. IA_PD) | |
(e.g. Prefix, Address) | | | |
|---Request---------------->| |---Request---------------->| |
(e.g. Prefix, Address) | | (e.g. IA_PD) |---Relay-Forward----------->|
|---Relay-Forward----------->| | | (OPTION_RADIUS) |
| (OPTION_RADIUS) | | |
| | |<--Relay-Reply -------------|
|<--Relay-Reply -------------| |<--Reply-------------------| |
|<--Reply-------------------| | (e.g. IA_PD) | |
(e.g. Prefix, Address) | | | |
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 Mode: | NAS | |Radius | |DHCPv6 | Access Mode: | NAS | |Radius |
|Client | PPPoE |(DHCPv6| |Server | |Client | PPPoE | | |Server |
| | | Relay)| | |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| | | | | |
|--PPP LCP Config-Request-->| | |--PPP LCP Config-Request-->| |
|---Access-Request---------->| | |---Access-Request---------->|
|<--Access-Accept------------| | | |
| (e.g. Framed-Pool) | |<--Access-Accept------------|
| (e.g. Delegated-IPv6-Prefix) |<----PPP LCP Config-ACK----|(e.g. Delegated-IPv6-Prefix)|
| | | |
|<----PPP LCP Config-ACK----|
PPP messages RADIUS messages PPP messages RADIUS messages
| +-------+ +-------+
| |DHCPv6 | |DHCPv6 |
| |Server | |Server |
| | | +-------+
| +-------+ | | |
|---Solicit---------------->| | |---Solicit---------------->| |
|---Relay-Forward----------->| | |---Relay-Forward----------->|
| (OPTION_RADIUS) | | (OPTION_RADIUS) |
| | | |
|<--Relay-Reply -------------| | |<--Relay-Reply -------------|
|<--Advertise---------------| |<--Advertise---------------| |
(e.g. Prefix, Address) | | (e.g. IA_PD) | |
|---Request---------------->| | | |
(e.g. Prefix, Address) | |---Request---------------->| |
|---Relay-Forward----------->| | (e.g. IA_PD) |---Relay-Forward----------->|
| (OPTION_RADIUS) | | (OPTION_RADIUS)
| | | |
|<--Relay-Reply -------------| | |<--Relay-Reply -------------|
|<--Reply-------------------| |<--Reply-------------------| |
(e.g. Prefix, Address) | | (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 DHCPv6 relay will not forward the message
from the client to the server. from the client to the server. After receiving RENEW (5) message
from the DHCPv6 client, NAS does not have to initiate a new Access-
Request/Access message exchange with the RADIUS server; but after
receiving REBIND (6) message from the DHCPv6 client, NAS has to
initiate a new Access-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 6, line 33 skipping to change at page 6, line 32
option-length Length of the option-data in Octets option-length Length of the option-data in Octets
option-data One or a list of RADIUS Attributes option-data One or a list of RADIUS Attributes
The option-data of OPTION_RADIUS is one or a list of RADIUS The option-data of OPTION_RADIUS is one or a list of RADIUS
attributes received in the Access-Accept message from the RADIUS attributes received in the Access-Accept message from the RADIUS
server. As the same method in [RFC4014], only the attributes listed server. As the same method in [RFC4014], only the attributes listed
in the table below may be included in the OPTION_RADIUS. in the table below may be included in the OPTION_RADIUS.
Type Code Attribute Reference Type Code Attribute Reference
26 Vendor-Specific [RFC2865] 26 Vendor-Specific [RFC2865]
88 Framed-Pool [RFC2869]
123 Delegated-IPv6-Prefix [RFC4818] 123 Delegated-IPv6-Prefix [RFC4818]
[TBD] Framed-IPv6-Address [ietf-radext-ipv6-access-10] 144 DS-Lite-Tunnel-Name [RFC6519]
[TBD] Stateful-IPv6-Address-Pool [ietf-radext-ipv6-access-10] [TBD] Framed-IPv6-Address [I-D.ietf-radext-ipv6-access]
[TBD] Delegated-IPv6-Prefix-Pool [ietf-radext-ipv6-access-10] [TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access]
[TBD] DNS-Server-IPv6-Address [ietf-radext-ipv6-access-10] [TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access]
[TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access]
Note: The above table might have more attributes in the future. Note: The above table might have more attributes to join in the
future.
5. Relay Agent Behavior 5. 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 Framed-Pool (88) (12) message. When the value in the attributes of Stateful-IPv6-
(or Stateful-IPv6-Address-Pool, Delegated-IPv6-Prefix-Pool), Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123)
Delegated-IPv6-Prefix (123) and Framed-IPv6-Address in the Access- or Framed-IPv6-Address in the Access-Accept message replied from
Accept message replied from RADIUS server are valid, the relay agent RADIUS server are valid, the relay agent that supports OPTION_RADIUS
that supports OPTION_RADIUS SHOULD include these RADIUS attributes in SHOULD include these RADIUS attributes into the container option,
the container option, OPTION_RADIUS. The relay agent MUST ignore OPTION_RADIUS. The relay agent MUST silently discard OPTION_RADIUS
OPTION_RADIUS if received. if received.
6. Server Behavior 6. Server Behavior
Upon receipt of the RELAY-FORW 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 SHOULD extract and interpret the
RADIUS attributes in the OPTION_RADIUS, and use that information in RADIUS attributes in the OPTION_RADIUS, and use that information in
selecting configuration parameters for the requesting client. If the selecting configuration parameters for the requesting client. If the
DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server DHCPv6 server does not support OPTION_RADIUS, the DHCPv6 server MUST
SHOULD ignore this option. The DHCPv6 server MUST NOT include silently discard this option. The DHCPv6 server MUST NOT include
OPTION_RADIUS in RELAY-REPL messages. OPTION_RADIUS in RELAY-REPL (13) messages.
7. Client Behavior 7. Client Behavior
OPTION_RADIUS option is only exchanged between the relay agents and OPTION_RADIUS option is only sent from the relay agents to the
the servers. DHCPv6 clients are not aware of the usage of servers. DHCPv6 clients are not aware of the usage of OPTION_RADIUS.
OPTION_RADIUS. DHCPv6 Client MUST NOT send OPTION_RADIUS, and MUST DHCPv6 Client MUST NOT send OPTION_RADIUS, and MUST ignore
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].
9. IANA Considerations 9. IANA Considerations
skipping to change at page 8, line 4 skipping to change at page 7, line 42
The authors of this document request to assign a new DHCPv6 option The authors of this document request to assign a new DHCPv6 option
code for OPTION_RADIUS. code for OPTION_RADIUS.
10. Acknowledgements 10. Acknowledgements
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]
Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B.
Lourdelet, "RADIUS attributes for IPv6 Access Networks",
draft-ietf-radext-ipv6-access-11 (work in progress),
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.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, 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 [RFC3736] Droms, R., "Stateless Dynamic Host Configuration Protocol
(DHCP) Service for IPv6", RFC 3736, April 2004. (DHCP) Service for IPv6", RFC 3736, April 2004.
[RFC4014] Droms, R. and J. Schnizlein, "Remote Authentication [RFC4014] Droms, R. and J. Schnizlein, "Remote Authentication
Dial-In User Service (RADIUS) Attributes Suboption for the Dial-In User Service (RADIUS) Attributes Suboption for the
Dynamic Host Configuration Protocol (DHCP) Relay Agent Dynamic Host Configuration Protocol (DHCP) Relay Agent
Information Option", RFC 4014, February 2005. 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-
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.
[ietf-radext-ipv6-access-10] [RFC6334] Hankins, D. and T. Mrugalski, "Dynamic Host Configuration
Lourdelet, B., Dec, W., Sarikaya, B., Zorn, G., and D. Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite",
Miles, "RADIUS attributes for IPv6 Access Networks", RFC 6334, August 2011.
July 2011.
Authors' Addresses Authors' Addresses
Leaf Y. Yeh (editor) Leaf Y. Yeh
Huawei Technologies Huawei Technologies
P. R. China P. R. China
Email: leaf.y.yeh@huawei.com Email: leaf.y.yeh@huawei.com
Mohamed Boucadair Mohamed Boucadair
France Telecom France Telecom
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
 End of changes. 33 change blocks. 
128 lines changed or deleted 134 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/