draft-ietf-mpls-rsvp-upstream-00.txt   draft-ietf-mpls-rsvp-upstream-01.txt 
Network Working Group R. Aggarwal Network Working Group R. Aggarwal
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: September 2006 Expiration Date: September 2007
J. L. Le Roux J. L. Le Roux
France Telecom France Telecom
MPLS Upstream Label Assignment for RSVP-TE MPLS Upstream Label Assignment for RSVP-TE
draft-ietf-mpls-rsvp-upstream-00.txt draft-ietf-mpls-rsvp-upstream-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 2, line 13 skipping to change at page 2, line 13
multipoint (P2MP)LSPs. multipoint (P2MP)LSPs.
Table of Contents Table of Contents
1 Specification of requirements ......................... 2 1 Specification of requirements ......................... 2
2 Introduction .......................................... 2 2 Introduction .......................................... 2
3 RSVP-TE Upstream Label Assignment Capability .......... 3 3 RSVP-TE Upstream Label Assignment Capability .......... 3
4 Distributing Upstream-Assigned Labels in RSVP-TE ...... 4 4 Distributing Upstream-Assigned Labels in RSVP-TE ...... 4
4.1 Procedures ............................................ 4 4.1 Procedures ............................................ 4
5 RSVP-TE Tunnel Identifier Exchange .................... 5 5 RSVP-TE Tunnel Identifier Exchange .................... 5
6 RSVP-TE Point-to-Multipoint LSPs on a LAN ............. 5 6 RSVP-TE Point-to-Multipoint LSPs on a LAN ............. 6
7 Acknowledgements ...................................... 6 7 Acknowledgements ...................................... 7
8 References ............................................ 6 8 References ............................................ 7
8.1 Normative References .................................. 6 8.1 Normative References .................................. 7
8.2 Informative References ................................ 7 8.2 Informative References ................................ 8
9 Author Information .................................... 7 9 Author Information .................................... 8
10 Intellectual Property Statement ....................... 8 10 Intellectual Property Statement ....................... 8
11 Full Copyright Statement .............................. 8 11 Full Copyright Statement .............................. 9
1. Specification of requirements 1. Specification of requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
This document describes procedures for distributing upstream-assigned This document describes procedures for distributing upstream-assigned
skipping to change at page 2, line 42 skipping to change at page 2, line 42
Engineering (RSVP-TE). These procedures follow the architecture for Engineering (RSVP-TE). These procedures follow the architecture for
MPLS Upstream Label Assignment described in [MPLS-UPSTREAM]. MPLS Upstream Label Assignment described in [MPLS-UPSTREAM].
This document describes extensions to RSVP-TE that a LSR can use to This document describes extensions to RSVP-TE that a LSR can use to
advertise to its neighboring LSRs whether the LSR supports upstream advertise to its neighboring LSRs whether the LSR supports upstream
label assignment. label assignment.
This document also describes extensions to RSVP-TE to distribute This document also describes extensions to RSVP-TE to distribute
upstream-assigned labels. upstream-assigned labels.
The usage of MPLS upstream label assignment using RSVP-TE for avoid- The usage of MPLS upstream label assignment using RSVP-TE for
ing branch LSR [RSVP-P2MP] traffic replication on a LAN for RSVP-TE avoiding branch LSR [RSVP-P2MP] traffic replication on a LAN for
P2MP TE LSPs [RSVP-TE-P2MP] is also described. RSVP-TE P2MP TE LSPs [RSVP-TE-P2MP] is also described.
3. RSVP-TE Upstream Label Assignment Capability 3. RSVP-TE Upstream Label Assignment Capability
According to [MPLS-UPSTREAM], upstream-assigned label bindings MUST According to [MPLS-UPSTREAM], upstream-assigned label bindings MUST
NOT be used unless it is known that a downstream LSR supports them. NOT be used unless it is known that a downstream LSR supports them.
This implies that there MUST be a mechanism to enable a LSR to adver- This implies that there MUST be a mechanism to enable a LSR to
tise to its RSVP-TE neighbor LSR(s) its support of upstream-assigned advertise to its RSVP-TE neighbor LSR(s) its support of upstream-
labels. assigned labels.
[RSVP-RESTART] defines a CAPABILITY object to be carried within Hello [RSVP-RESTART] defines a CAPABILITY object to be carried within Hello
messages, and used to indicate the set of capabilities supported by a messages, and used to indicate the set of capabilities supported by a
node. Currently one flag is defined, the R flag indicating the sup- node. Currently one flag is defined, the R flag indicating the
port for RecoveryPath Srefresh. This document defines a new flag, the support for RecoveryPath Srefresh. This document defines a new flag,
U flag, to signal a LSR's support of upstream label assignment to its the U flag, to signal a LSR's support of upstream label assignment to
RSVP-TE neighbors. its RSVP-TE neighbors.
The format of a Capability object is: The format of a Capability object is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num(TBA)| C-Type (1) | | Length | Class-Num(TBA)| C-Type (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |U|R| | Reserved |U|R|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 4, line 32 skipping to change at page 4, line 32
The label can be encoded as in [RFC3209] when the C-Type is 1 or as a The label can be encoded as in [RFC3209] when the C-Type is 1 or as a
Generalized Label [RFC3473] when the C-Type is 2 or 3. Generalized Label [RFC3473] when the C-Type is 2 or 3.
4.1. Procedures 4.1. Procedures
A RSVP-TE LSR that assigns Upstream-Assigned Labels, distributes them A RSVP-TE LSR that assigns Upstream-Assigned Labels, distributes them
to the downstream LSRs by including them in RSVP-TE Path messages. to the downstream LSRs by including them in RSVP-TE Path messages.
A RSVP-TE LSR MUST NOT distribute the UPSTREAM_ASSIGNED_LABEL Object A RSVP-TE LSR MUST NOT distribute the UPSTREAM_ASSIGNED_LABEL Object
to a downstream LSR if the downstream LSR had not previously adver- to a downstream LSR if the downstream LSR had not previously
tised the CAPABILITY object with the U bit set in its RSVP-TE Hello advertised the CAPABILITY object with the U bit set in its RSVP-TE
messages. Hello messages.
If a downstream RSVP-TE LSR receives a Path message that carries an If a downstream RSVP-TE LSR receives a Path message that carries an
UPSTREAM_ASSIGNED_LABEL Object and the LSR does not support the UPSTREAM_ASSIGNED_LABEL Object and the LSR does not support the
object C-Num/C-Type it will return an "Unknown Object C-Num/C-Type" object C-Num/C-Type it will return an "Unknown Object C-Num/C-Type"
error. If the LSR does support the object, but is unable to process error. If the LSR does support the object, but is unable to process
the upstream-assigned label as described in [MPLS-UPSTREAM] it SHOULD the upstream-assigned label as described in [MPLS-UPSTREAM] it SHOULD
send a PathErr with the error code "Routing problem" and the error send a PathErr with the error code "Routing problem" and the error
value "MPLS Upstream Assigned Label Processing Failure". If the LSR value "MPLS Upstream Assigned Label Processing Failure". If the LSR
successfully processes the Path message and the upstream-assigned successfully processes the Path message and the upstream-assigned
label it MUST send a Resv message upstream as per [RFC3209] but it label it MUST send a Resv message upstream as per [RFC3209] but it
skipping to change at page 5, line 23 skipping to change at page 5, line 23
used by Ru for transmitting MPLS packets with upstream-assigned MPLS used by Ru for transmitting MPLS packets with upstream-assigned MPLS
labels. labels.
When RSVP-TE is used for upstream label assignment, the IF_ID When RSVP-TE is used for upstream label assignment, the IF_ID
RSVP_HOP object is used for signaling the Tunnel Identifier. If Ru RSVP_HOP object is used for signaling the Tunnel Identifier. If Ru
uses an IP or MPLS tunnel to transmit MPLS packets with upstream uses an IP or MPLS tunnel to transmit MPLS packets with upstream
assigned labels to Rd, Ru MUST include the IF_ID RSVP_HOP object assigned labels to Rd, Ru MUST include the IF_ID RSVP_HOP object
[RFC3473] in Path messages along with the UPSTREAM_ASSIGNED_LABEL [RFC3473] in Path messages along with the UPSTREAM_ASSIGNED_LABEL
Object. Object.
Two new TLVs are introduced in the IF_ID RSVP_HOP object [RFC3471] to Three new TLVs are introduced in the IF_ID RSVP_HOP object [RFC3471]
support RSVP-TE P2MP LSPs and IP Multicast Tunnels. The TLV value to support RSVP-TE P2MP LSPs, IP Multicast Tunnels and context
acts as the tunnel identifier. labels. The TLV value acts as the tunnel identifier.
1. RSVP-TE P2MP LSP TLV. Type = TBD. Value of the TLV is the RSVP-TE 1. RSVP-TE P2MP LSP TLV. Type = TBD. Value of the TLV is the RSVP-TE
P2MP Session Object and optionally the P2MP Sender Template Object P2MP Session Object and optionally the P2MP Sender Template Object
[RSVP-TE-P2MP]. The TLV value identifies the RSVP-TE P2MP LSP. This [RSVP-TE-P2MP]. The TLV value identifies the RSVP-TE P2MP LSP. This
mechanism extends RSVP-TE P2P Hierarchy [LSP-HIER] to RSVP-TE P2MP mechanism extends RSVP-TE P2P Hierarchy [LSP-HIER] to RSVP-TE P2MP
Hierarchy. It allows Ru to tunnel an "inner" P2MP LSP, the label for Hierarchy. It allows Ru to tunnel an "inner" P2MP LSP, the label for
which is upstream assigned, over an "outer" P2MP LSP that has leaves which is upstream assigned, over an "outer" P2MP LSP that has leaves
<Rd1...Rdn>. The P2MP LSP IF_ID TLV allows Ru to signal to <Rd1...Rdn>. The P2MP LSP IF_ID TLV allows Ru to signal to
<Rd1...Rdn> the binding of the inner P2MP LSP to the outer P2MP LSP. <Rd1...Rdn> the binding of the inner P2MP LSP to the outer P2MP LSP.
The control plane signaling between Ru and <Rd1...Rdn> for the inner The control plane signaling between Ru and <Rd1...Rdn> for the inner
P2MP LSP uses directed RSVP-TE signaling messages as in [LSP-HIER]. P2MP LSP uses directed RSVP-TE signaling messages as in [LSP-HIER].
2. IP Multicast Tunnel TLV. Type = TBD. In this case the TLV value is 2. IP Multicast Tunnel TLV. Type = TBD. In this case the TLV value is
a <Source Address, Multicast Group Address> tuple. a <Source Address, Multicast Group Address> tuple. Source Address is
the IP address of the root of the tunnel i.e. Ru, and Multicast Group
Address is the Multicast Group Address used by the tunnel.
3. MPLS Context Label TLV. Type = TBD. In this case the TLV value is
a <Source Address, MPLS Context Label> tuple. The Source Address
belongs to Ru and the MPLS Context Label is an upstream assigned
label, assigned by Ru. This allows Ru to tunnel an "inner" RSVP-TE
P2MP LSP, the label of which is upstream assigned, over an "outer"
MPLS LSP, where the outer LSP has the following property:
+ The label pushed by Ru for the outer MPLS LSP is an upstream
assigned context label, assigned by Ru. When <Rd1...Rdn> perform
a MPLS label lookup on this label a combination of this label and
the incoming interface MUST be sufficient for <Rd1...Rdn> to
uniquely determine Ru's context specific label space to lookup
the next label on the stack in. <Rd1...Rdn> MUST receive the data
sent by Ru with the context specific label assigned by Ru being
the top label on the label stack.
Currently the usage of the context label TLV is limited only to RSVP-
TE P2MP LSPs on a LAN as specified in the next section. The context
label TLV MUST NOT be used for any other purposes.
6. RSVP-TE Point-to-Multipoint LSPs on a LAN 6. RSVP-TE Point-to-Multipoint LSPs on a LAN
This section describes one application of upstream label assignment This section describes one application of upstream label assignment
using RSVP-TE. Further applications are to be described in separate using RSVP-TE. Further applications are to be described in separate
documents. documents.
[RSVP-TE-P2MP] describes how to setup RSVP-TE P2MP LSPs. On a LAN the [RSVP-TE-P2MP] describes how to setup RSVP-TE P2MP LSPs. On a LAN the
solution described in [RSVP-TE-P2MP] relies on "ingress replication". solution described in [RSVP-TE-P2MP] relies on "ingress replication".
A LSR on a LAN, that is a branch LSR for a P2MP LSP, (say Ru) sends a A LSR on a LAN (say Il), that is a branch LSR for a P2MP LSP, (say
separate copy of a packet that it receives on the P2MP LSP to each of Ru) sends a separate copy of a packet that it receives on the P2MP
the downstream LSRs on the LAN (say <Rd1...Rdn> that are adjacent to LSP to each of the downstream LSRs on the LAN (say <Rd1...Rdn> that
it in the P2MP LSP. are adjacent to it in the P2MP LSP.
In order to increase efficiency of bandwidth utilization, it is In order to increase efficiency of bandwidth utilization, it is
desirable for Ru to send a single copy of the packet for the P2MP LSP desirable for Ru to send a single copy of the packet for the P2MP LSP
on the LAN, when there are multiple downstream routers on the LAN on the LAN, when there are multiple downstream routers on the LAN
that are adjacent in that P2MP LSP. This requires that each of that are adjacent in that P2MP LSP. This requires that each of
<Rd1...Rdn> must be able to associate the label L, used by Ru to <Rd1...Rdn> must be able to associate the label L, used by Ru to
transmit packets for the P2MP LSP on the LAN, with that P2MP LSP. It transmit packets for the P2MP LSP on the LAN, with that P2MP LSP. It
is possible to achieve this using RSVP-TE upstream-assigned labels is possible to achieve this using RSVP-TE upstream-assigned labels
with the following procedures. Assume that Ru and <Rd1...Rdn> support with the following procedures. Assume that Ru and <Rd1...Rdn> support
upstream label assignment. upstream label assignment.
Ru sends a Path message for the P2MP LSP to each of <Rd1...Rdn> that Ru sends a Path message for the P2MP LSP to each of <Rd1...Rdn> that
is adjacent on the P2MP LSP, with the same UPSTREAM_ASSIGNED_LABEL is adjacent on the P2MP LSP, with the same UPSTREAM_ASSIGNED_LABEL
object. This object carries an upstream assigned label, L. object. This object carries an upstream assigned label, L. This
message also carries a MPLS Context Label TLV, as described in the
previous section, with the value of the MPLS label set to a value
assigned by Ru on inteface I1 as specified in [MPLS-UPSTREAM].
<Rd1...Rdn> "reserve" the upstream assigned label in the separate <Rd1...Rdn> "reserve" the upstream assigned label in the separate
Upstream Neighbor Label Space that they maintain for Ru [MPLS- Upstream Neighbor Label Space that they maintain for Ru [MPLS-
UPSTREAM]. Ru can then transmit a single packet for the P2MP LSP to UPSTREAM].
<Rd1..Rdn> with a top label L using procedures defined in [MPLS-
UPSTREAM] and [MPLS-MCAST-ENCAPS].
If a subset of <Rd1...Rdn> does not support upstream label assignment Ru can then transmit a single packet for the P2MP LSP to <Rd1..Rdn>
these procedures can still be used between Ru and the remaining sub- with a top label L using procedures defined in [MPLS-UPSTREAM] and
set of <Rd1...Rdn>. Ingress replication and downstream label assign- [MPLS-MCAST-ENCAPS]. The MPLS packet transmitted by Ru contains as
ment will continue to be used for LSRs that do not support upstream the top label the context label assigned by Ru on the LAN interface,
label assignment. I1. The bottom label is the upstream label assigned by Ru to the
RSVP-TE P2MP LSP. The top label is looked up in the context of the
LAN interface, I1, [MPLS-UPSTREAM] by a downstream LSR on the LAN.
This lookup enables the downstream LSR to determine the context
specific label space to lookup the inner label in.
If a subset of <Rd1...Rdn> do not support upstream label assignment
these procedures can still be used between Ru and the remaining
subset of <Rd1...Rdn>. Ingress replication and downstream label
assignment will continue to be used for LSRs that do not support
upstream label assignment.
7. Acknowledgements 7. Acknowledgements
Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and Thanks to Yakov Rekhter for his contribution. Thanks to Ina Minei and
Thomas Morin for their comments. Thomas Morin for their comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon, [RFC3031] "MPLS Architecture", E. Rosen, A. Viswanathan, R. Callon,
RFC 3031. RFC 3031.
[MPLS-UPSTREAM] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream [MPLS-UPSTREAM] R. Aggarwal, Y. Rekhter, E. Rosen, "MPLS Upstream
Label Assignment and Context Specific Label Space", draft-ietf-mpls- Label Assignment and Context Specific Label Space", draft-ietf-mpls-
upstream-label-00.txt upstream-label-02.txt
[MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter, [MPLS-MCAST-ENCAPS] T. Eckert, E. Rosen, R. Aggarwal, Y. Rekhter,
draft-ietf-mpls-codepoint-00.txt draft-ietf-mpls-codepoint-02.txt
[RFC3209] Awduche et. al." "RSVP-TE: Extensions to RSVP for LSP Tun- [RFC3209] Awduche et. al." "RSVP-TE: Extensions to RSVP for LSP
nels", RFC 3209, December 2001. Tunnels", RFC 3209, December 2001.
[RFC2119] "Key words for use in RFCs to Indicate Requirement Lev- [RFC2119] "Key words for use in RFCs to Indicate Requirement
[RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label [RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling - Resource ReserVation Protocol-Traffic Switching (GMPLS) Signaling - Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L. Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", RFC 3471 January Switching (GMPLS) Signaling Functional Description", RFC 3471 January
2003. 2003.
[RSVP-RESTART] A. Satyanarayana et. al., "Extensions to GMPLS RSVP [RSVP-RESTART] A. Satyanarayana et. al., "Extensions to GMPLS RSVP
Graceful Restart", draft-ietf-ccamp-rsvp-restart-ext-02.txt Graceful Restart", draft-ietf-ccamp-rsvp-restart-ext-02.txt
8.2. Informative References 8.2. Informative References
[MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs" [MVPN] E. Rosen, R. Aggarwal [Editors], "Multicast in BGP/MPLS VPNs",
draft-ietf-l3vpn-2547bis-mcast-02.txt
[RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors], [RSVP-TE-P2MP] R. Aggarwal, D. Papadimitriou, S. Yasukawa [Editors],
"Extensions to RSVP-TE for Point to Multipoint TE LSPs" "Extensions to RSVP-TE for Point to Multipoint TE LSPs", draft-ietf-
mpls-rsvp-te-p2mp-07.txt
9. Author Information 9. Author Information
Rahul Aggarwal Rahul Aggarwal
Juniper Networks Juniper Networks
1194 North Mathilda Ave. 1194 North Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: rahul@juniper.net Email: rahul@juniper.net
Jean-Louis Le Roux Jean-Louis Le Roux
France Telecom France Telecom
2, avenue Pierre-Marzin 2, avenue Pierre-Marzin
22307 Lannion Cedex 22307 Lannion Cedex
France France
E-mail: jeanlouis.leroux@francetelecom.com E-mail: jeanlouis.leroux@orange-ftgroup.com
10. Intellectual Property Statement 10. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assur- Copies of IPR disclosures made to the IETF Secretariat and any
ances of licenses to be made available, or the result of an attempt assurances of licenses to be made available, or the result of an
made to obtain a general license or permission for the use of such attempt made to obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification can such proprietary rights by implementers or users of this
be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
11. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The IETF Trust (2007). This document is subject to the
to the rights, licenses and restrictions contained in BCP 78, and rights, licenses and restrictions contained in BCP 78, and except as
except as set forth therein, the authors retain all their rights. set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFOR- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
MATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 24 change blocks. 
55 lines changed or deleted 91 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/