draft-ietf-dhc-dhcpv6-radius-opt-05.txt   draft-ietf-dhc-dhcpv6-radius-opt-06.txt 
DHC Working Group L. Yeh DHC Working Group L. Yeh
Internet-Draft Huawei Technologies Internet-Draft Freelancer Technologies
Intended status: Standards Track M. Boucadair Intended status: Standards Track M. Boucadair
Expires: June 2, 2013 France Telecom Expires: July 8, 2013 France Telecom
T. Lemon T. Lemon
Nominum, Inc Nominum, Inc
November 29, 2012 January 4, 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-05 draft-ietf-dhc-dhcpv6-radius-opt-06
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 the DHCPv6 relay
server. This mechanism is meant for the centralized DHCPv6 server to agent and the DHCPv6 server. This mechanism is meant for the
select the right configuration for the requesting client based on the centralized DHCPv6 server to select the right configuration for the
authorization information received from the RADIUS server, which is requesting DHCPv6 client based on the authorization information
not co-located with the DHCPv6 server. The Network Access Server received from the RADIUS server, which is not co-located with the
(NAS) acts as DHCPv6 relay agent and RADIUS client simultaneously in DHCPv6 server. The Network Access Server (NAS) acts as DHCPv6 relay
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 June 2, 2013. This Internet-Draft will expire on July 8, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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 . . . . . . . . . . . . . . . . . . . . . 6 4. DHCPv6 RADIUS option . . . . . . . . . . . . . . . . . . . . . 7
5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 7 5. Relay Agent Behavior . . . . . . . . . . . . . . . . . . . . . 8
6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Server Behavior . . . . . . . . . . . . . . . . . . . . . . . 8
7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
11.1. Normative References . . . . . . . . . . . . . . . . . . . 8 11.1. Normative References . . . . . . . . . . . . . . . . . . 9
11.2. Informative References . . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9 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], IPv6 prefix [RFC3633], etc. 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 this document, the DHCPv6 server is deployed of AFTR [RFC6334]. In the scenarios described in this document, the
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
address or prefix from the indicated pool, or to assign an IPv6 address or prefix from the indicated pool, or to assign an IPv6
address or prefix with an explicitly indicated value, and other address or prefix with an explicitly indicated value, and other
configuration parameters as per the attributes for the subscribers. configuration parameters as per the attributes for the subscribers.
skipping to change at page 3, line 40 skipping to change at page 3, line 40
centralized DHCPv6 server is co-located with the RADIUS server, where centralized DHCPv6 server is co-located with the RADIUS server, where
they can share the same database of the users. But when the NAS acts they can share the same database of the users. But when the NAS acts
as the relay agent and RADIUS client simultaneously, and the as the relay agent and RADIUS client simultaneously, and the
centralized DHCPv6 server is not located in the same place as the centralized DHCPv6 server is not located in the same place as the
RADIUS server, a new communication mechanism is needed for the relay RADIUS server, a new communication mechanism is needed for the relay
agent to transfer the authorization information indicated by the agent to transfer the authorization information indicated by the
RADIUS attributes to the DHCPv6 server. 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 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 to the centralized DHCPv6 received in the Access-Accept message from the RADIUS server to the
server. Definitions for terms and acronyms not specified in this centralized DHCPv6 server. Definitions for terms and acronyms not
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 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 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 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 IPoE access mode. Figure 2 shows the sequence of DHCPv6 messages for IP over Ethernet (IPoE) access model, when the access
and RADIUS messages for PPPoE access mode. loop adopts the direct Ethernet encapsulation. Figure 2 shows the
sequence of DHCPv6 and RADIUS messages for PPP over Ethernet (PPPoE)
access model.
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
|DHCPv6 | Access Mode: | NAS | |Radius | |DHCPv6 | Access Model: | NAS | |Radius |
|Client | IPoE | | |Server | |Client | IPoE | | |Server |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| | | | | |
|---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
+-------+ +-------+
|DHCPv6 | |DHCPv6 |
|Server | |Server |
+-------+ +-------+
| | | | | |
| |---Relay-forward----------->| | |---Relay-forward----------->|
| | (OPTION_RADIUS) | | | (OPTION_RADIUS) |
| | | | | |
| |<--Relay-reply -------------| | |<--Relay-reply -------------|
|<--Advertise---------------| | |<--Advertise---------------| |
skipping to change at page 5, 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 Mode: | NAS | |Radius | |DHCPv6 | Access Model: | NAS | |Radius |
|Client | PPPoE | | |Server | |Client | PPPoE | | |Server |
+-------+ +-------+ +-------+ +-------+ +-------+ +-------+
| | | | | |
|--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
+-------+ +-------+
|DHCPv6 | |DHCPv6 |
|Server | |Server |
+-------+ +-------+
| | | | | |
|---Solicit---------------->| | |---Solicit---------------->| |
| |---Relay-forward----------->| | |---Relay-forward----------->|
| | (OPTION_RADIUS) | | | (OPTION_RADIUS) |
skipping to change at page 5, line 39 skipping to change at page 6, line 40
| (e.g. IA_PD) | | | (e.g. IA_PD) | |
| | | | | |
|---Request---------------->| | |---Request---------------->| |
| (e.g. IA_PD) |---Relay-forward----------->| | (e.g. IA_PD) |---Relay-forward----------->|
| | (OPTION_RADIUS) | | (OPTION_RADIUS)
| | | | | |
| |<--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 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 server. After receiving RENEW (5) message from the DHCPv6 the DHCPv6 server. If the authentication or the authorization
client, the NAS does not have to initiate a new Access-Request/ through RADIUS passes, the NAS MUST store the RADIUS attributes
received in the Access-Accept message from the RADIUS server during
the whole session. After receiving RENEW (5) message from the DHCPv6
client, the NAS SHOULD NOT initiate a new Access-Request/
Access-Accept message exchange with the RADIUS server; but after Access-Accept message exchange with the RADIUS server; but after
receiving REBIND (6) message from the DHCPv6 client, the NAS has to receiving REBIND (6) message from the DHCPv6 client, the NAS SHOULD
initiate a new Access-Request/Access-Accept message exchange with the initiate a new Access-Request/Access-Accept message exchange with the
RADIUS server. RADIUS server.
4. DHCPv6 RADIUS option 4. DHCPv6 RADIUS option
The OPTION_RADIUS is a stateless DHCPv6 option, and is used by the The OPTION_RADIUS is a DHCPv6 option used by the DHCPv6 relay agent
relay agent to carry the authorization information of RADIUS to carry the authorization information of RADIUS attributes received
attributes received in the Access-Accept message. 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
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_RADIUS | option-len | | OPTION_RADIUS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 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 the DHCPv6 RADIUS option' SHOULD be included
in the OPTION_RADIUS. in the OPTION_RADIUS.
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 the DHCPv6 RADIUS option'. New RADIUS
skipping to change at page 6, line 45 skipping to change at page 8, line 4
[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] [TBD] Framed-IPv6-Address [I-D.ietf-radext-ipv6-access]
[TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access] [TBD] Stateful-IPv6-Address-Pool [I-D.ietf-radext-ipv6-access]
[TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access] [TBD] Delegated-IPv6-Prefix-Pool [I-D.ietf-radext-ipv6-access]
[TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access] [TBD] DNS-Server-IPv6-Address [I-D.ietf-radext-ipv6-access]
Note: The definition of the RADIUS attribute's 'Length' field in Note: The definition of the RADIUS attribute's 'Length' field in
section 5 of [RFC2865] includes the length of 'Type' and 'Length' section 5 of [RFC2865] includes the length of 'Type' and 'Length'
fields. fields.
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.
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 Stateful-IPv6- (12) message. When the value in the attributes of Stateful-IPv6-
Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123) Address-Pool, Delegated-IPv6-Prefix-Pool, Delegated-IPv6-Prefix (123)
or Framed-IPv6-Address in the Access-Accept message replied from or Framed-IPv6-Address in the Access-Accept message replied from
RADIUS server are valid, the relay agent that supports OPTION_RADIUS RADIUS server are valid, the relay agent that supports OPTION_RADIUS
SHOULD include these RADIUS attributes into the container option, SHOULD include these RADIUS attributes into the container option,
OPTION_RADIUS. OPTION_RADIUS.
skipping to change at page 7, line 39 skipping to change at page 9, line 5
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].
The mechanism described in this document may introduce new attack
vector against the DHCPv6 server in case the DHCPv6 relay agent is
compromised. By forging the RADIUS attributes contained in the
OPTION_RADIUS of the RELAY-FORW (12) messages, the attacker may
influence the parameter assignment on the DHCPv6 server for the
DHCPv6 clients. However, in the network scenarios described in the
section 3, NAS could always be regarded as a trusted network
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, and to create a new registry on the same assignment
page, which can be entitled as 'RADIUS Attributes Permitted in the page, which can be entitled as 'RADIUS Attributes Permitted in the
DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS DHCPv6 RADIUS option'. The new registry will enumerate the RADIUS
Attributes Types 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
skipping to change at page 9, line 23 skipping to change at page 10, line 42
[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.
[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 Freelancer Technologies
P. R. China P. R. China
Email: leaf.yeh.sdo@gmail.com Email: leaf.yeh.sdo@gmail.com
Mohamed Boucadair Mohamed Boucadair
France Telecom France Telecom
France France
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
Ted Lemon Ted Lemon
Nominum, Inc Nominum, Inc
USA USA
 End of changes. 29 change blocks. 
49 lines changed or deleted 71 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/