draft-ietf-isis-gmpls-extensions-16.txt   draft-ietf-isis-gmpls-extensions-17.txt 
Network Working Group K. Kompella (Editor) Network Working Group K. Kompella, Editor
Internet Draft Y. Rekhter (Editor) Internet Draft Y. Rekhter, Editor
Category: Informational Juniper Networks Category: Informational Juniper Networks
Expires: June 2003 December 2002 Updates: <isis te> October 2003
Expires: April 2004
IS-IS Extensions in Support of Generalized MPLS IS-IS Extensions in Support of Generalized MPLS
draft-ietf-isis-gmpls-extensions-16.txt draft-ietf-isis-gmpls-extensions-17.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 36
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document specifies encoding of extensions to the IS-IS routing This document specifies encoding of extensions to the IS-IS routing
protocol in support of Generalized Multi-Protocol Label Switching. protocol in support of Generalized Multi-Protocol Label Switching.
Summary for Sub-IP Area Specification of Requirements
(To be removed before publication)
0.1. Summary
This document specifies encoding of extensions to the IS-IS routing
protocol in support of Generalized Multi-Protocol Label Switching
(GMPLS). The description of the extensions is specified in [GMPLS-
ROUTING].
0.2. Where does it fit in the Picture of the Sub-IP Work
This work fits squarely in either CCAMP or IS-IS boxes.
0.3. Why is it Targeted at this WG
This draft is targeted at either the CCAMP or IS-IS WGs, because this The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
draft specifies the extensions to the IS-IS routing protocols in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
support of GMPLS, because GMPLS is within the scope of CCAMP WG, and document are to be interpreted as described in RFC 2119 [RFC2119].
because IS-IS is within the scope of the IS-IS WG.
0.4. Justification Changes since last revision
The WG should consider this document as it specifies the extensions (RFC Editor: remove this section before publication.)
to the IS-IS routing protocols in support of GMPLS.
1. Specification of Requirements Formatting changes.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", Updated references.
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 1. Introduction
This document specifies extensions to the IS-IS routing protocol in This document specifies extensions to the IS-IS routing protocol in
support of carrying link state information for Generalized Multi- support of carrying link state information for Generalized
Protocol Label Switching (GMPLS). The set of required enhancements to Multi-Protocol Label Switching (GMPLS). The set of required
IS-IS are outlined in [GMPLS-ROUTING]. Support for unnumbered enhancements to IS-IS are outlined in [GMPLS-ROUTING]. Support for
interfaces assumes support for the "Point-to-Point Three-Way unnumbered interfaces assumes support for the "Point-to-Point
Adjacency" IS-IS Option type [ISIS-3way]. Three-Way Adjacency" IS-IS Option type [ISIS-3way].
3. IS-IS Routing Enhancements 2. IS-IS Routing Enhancements
In this section we define the enhancements to the TE properties of In this section we define the enhancements to the TE properties of
GMPLS TE links that can be announced in IS-IS Link State Protocol GMPLS TE links that can be announced in IS-IS Link State Protocol
Data Units. Data Units.
In this document, we enhance the sub-TLVs for the extended IS In this document, we enhance the sub-TLVs for the extended IS
reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically, reachability TLV (see [ISIS-TE]) in support of GMPLS. Specifically,
we add the following sub-TLVs: we add the following sub-TLVs:
Sub-TLV Type Length Name Sub-TLV Type Length Name
4 8 Link Local/Remote Identifiers 4 8 Link Local/Remote Identifiers
20 2 Link Protection Type 20 2 Link Protection Type
21 variable Interface Switching Capability Descriptor 21 variable Interface Switching Capability
Descriptor
We further add one new TLV to the TE TLVs: We further add one new TLV to the TE TLVs:
TLV Type Length Name TLV Type Length Name
138 variable Shared Risk Link Group 138 variable Shared Risk Link Group
3.1. Link Local/Remote Identifiers 2.1. Link Local/Remote Identifiers
A Link Local Interface Identifiers is a sub-TLV of the extended IS A Link Local Interface Identifiers is a sub-TLV of the extended IS
reachability TLV. The type of this sub-TLV is 4, and length is eight reachability TLV. The type of this sub-TLV is 4, and length is eight
octets. The value field of this sub-TLV contains four octets of Link octets. The value field of this sub-TLV contains four octets of Link
Local Identifier followed by four octets of Link Remote Idenfier (see Local Identifier followed by four octets of Link Remote Idenfier (see
Section "Support for unnumbered links" of [GMPLS-ROUTING]). If the Section "Support for unnumbered links" of [GMPLS-ROUTING]). If the
Link Remote Identifier is unknown, it is set to 0. Link Remote Identifier is unknown, it is set to 0.
The following illustrates encoding of the Value field of the Link The following illustrates encoding of the Value field of the Link
Local/Remote Identifiers sub-TLV. Local/Remote Identifiers sub-TLV.
skipping to change at page 4, line 19 skipping to change at page 4, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Remote Identifier | | Link Remote Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Link Local/Remote Identifiers sub-TLV MUST NOT occur more than The Link Local/Remote Identifiers sub-TLV MUST NOT occur more than
once within the extended IS reachability TLV. If the Link once within the extended IS reachability TLV. If the Link
Local/Remote Idenfitiers sub-TLV occurs more than once within the Local/Remote Idenfitiers sub-TLV occurs more than once within the
extended IS reachability TLV, the receiver SHOULD ignore all these extended IS reachability TLV, the receiver SHOULD ignore all these
sub-TLVs. sub-TLVs.
3.2. Link Protection Type 2.2. Link Protection Type
The Link Protection Type is is a sub-TLV (of type 20) of the The Link Protection Type is is a sub-TLV (of type 20) of the
extended IS reachability TLV, with length two octets. extended IS reachability TLV, with length two octets.
The following illustrates encoding of the Value field of the Link The following illustrates encoding of the Value field of the Link
Protection Type sub-TLV. Protection Type sub-TLV.
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 5, line 4 skipping to change at page 4, line 38
0x08 Dedicated 1:1 0x08 Dedicated 1:1
0x10 Dedicated 1+1 0x10 Dedicated 1+1
0x20 Enhanced 0x20 Enhanced
0x40 Reserved 0x40 Reserved
0x80 Reserved 0x80 Reserved
The second octet SHOULD be set to zero by the sender, and SHOULD be The second octet SHOULD be set to zero by the sender, and SHOULD be
ignored by the receiver. ignored by the receiver.
The Link Protection Type sub-TLV MUST NOT occur more than once within The Link Protection Type sub-TLV MUST NOT occur more than once within
the extended IS reachability TLV. If the Link Protection Type sub-TLV the extended IS reachability TLV. If the Link Protection Type
occurs more than once within the extended IS reachability TLV, the sub-TLV occurs more than once within the extended IS reachability
receiver SHOULD ignore all these sub-TLVs. TLV, the receiver SHOULD ignore all these sub-TLVs.
3.3. Interface Switching Capability Descriptor 2.3. Interface Switching Capability Descriptor
The Interface Switching Capability Descriptor is a sub-TLV (of type The Interface Switching Capability Descriptor is a sub-TLV (of type
21) of the extended IS reachability TLV. The length is the length of 21) of the extended IS reachability TLV. The length is the length of
value field in octets. The following illustrates encoding of the value field in octets. The following illustrates encoding of the
Value field of the Interface Switching Capability Descriptor sub-TLV. Value field of the Interface Switching Capability Descriptor sub-TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Cap | Encoding | Reserved | | Switching Cap | Encoding | Reserved |
skipping to change at page 7, line 20 skipping to change at page 7, line 5
When the Switching Capability field is LSC, there is no Switching When the Switching Capability field is LSC, there is no Switching
Capability specific information field present. Capability specific information field present.
To support interfaces that have more than one Interface Switching To support interfaces that have more than one Interface Switching
Capability Descriptor (see Section "Interface Switching Capability Capability Descriptor (see Section "Interface Switching Capability
Descriptor" of [GMPLS-ROUTING]) the Interface Switching Capability Descriptor" of [GMPLS-ROUTING]) the Interface Switching Capability
Descriptor sub-TLV MAY occur more than once within the extended IS Descriptor sub-TLV MAY occur more than once within the extended IS
reachability TLV. reachability TLV.
3.4. Shared Risk Link Group TLV 2.4. Shared Risk Link Group TLV
The SRLG TLV (of type 138 TBD) contains a data structure consisting The SRLG TLV (of type 138 TBD) contains a data structure consisting
of: of:
6 octets of System ID 6 octets of System ID
1 octet of Pseudonode Number 1 octet of Pseudonode Number
1 octet Flag 1 octet Flag
4 octets of IPv4 interface address or 4 octets of a Link Local 4 octets of IPv4 interface address or 4 octets of a Link Local
Identifier Identifier
4 octets of IPv4 neighbor address or 4 octets of a Link Remote 4 octets of IPv4 neighbor address or 4 octets of a Link Remote
Identifier Identifier
(variable) list of SRLG values, where each element in the list has 4 (variable) list of SRLG values, where each element in the list
octets. has 4 octets.
The following illustrates encoding of the Value field of the SRLG The following illustrates encoding of the Value field of the SRLG
TLV. TLV.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System ID | | System ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System ID (cont.) | Pseudonode num| Flags | | System ID (cont.) | Pseudonode num| Flags |
skipping to change at page 8, line 39 skipping to change at page 8, line 8
other bits are reserved and should be set to 0. other bits are reserved and should be set to 0.
The length of this TLV is 16 + 4 * (number of SRLG values). The length of this TLV is 16 + 4 * (number of SRLG values).
This TLV carries the Shared Risk Link Group information (see Section This TLV carries the Shared Risk Link Group information (see Section
"Shared Risk Link Group Information" of [GMPLS-ROUTING]). "Shared Risk Link Group Information" of [GMPLS-ROUTING]).
The SRLG TLV MAY occur more than once within the IS-IS Link State The SRLG TLV MAY occur more than once within the IS-IS Link State
Protocol Data Units. Protocol Data Units.
3.5. Link Identifier for Unnumbered Interfaces 2.5. Link Identifier for Unnumbered Interfaces
Link Identifiers are exchanged in the Extended Local Circuit ID field Link Identifiers are exchanged in the Extended Local Circuit ID field
of the "Point-to-Point Three-Way Adjacency" IS-IS Option type of the "Point-to-Point Three-Way Adjacency" IS-IS Option type
[ISIS-3way]. [ISIS-3way].
4. Implications on Graceful Restart 3. Implications on Graceful Restart
The restarting node SHOULD follow the ISIS restart procedures [ISIS- The restarting node SHOULD follow the ISIS restart procedures
RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP]. [ISIS-RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
When the restarting node is going to originate its IS-IS Link State When the restarting node is going to originate its IS-IS Link State
Protocol data units for TE links, these Link State Protocol data Protocol data units for TE links, these Link State Protocol data
units SHOULD be originated with 0 unreserved bandwidth, Traffic units SHOULD be originated with 0 unreserved bandwidth, Traffic
Engineering Default metric set to 0xffffff, and if the link has LSC Engineering Default metric set to 0xffffff, and if the link has LSC
or FSC as its Switching Capability then also with 0 as Max LSP or FSC as its Switching Capability then also with 0 as Max LSP
Bandwidth, until the node is able to determine the amount of Bandwidth, until the node is able to determine the amount of
unreserved resources taking into account the resources reserved by unreserved resources taking into account the resources reserved by
the already established LSPs that have been preserved across the the already established LSPs that have been preserved across the
restart. Once the restarting node determines the amount of unreserved restart. Once the restarting node determines the amount of
resources, taking into account the resources reserved by the already unreserved resources, taking into account the resources reserved by
established LSPs that have been preserved across the restart, the the already established LSPs that have been preserved across the
node SHOULD advertise these resources in its Link State Protocol data restart, the node SHOULD advertise these resources in its Link State
units. Protocol data units.
In addition in the case of a planned restart prior to restarting, the In addition in the case of a planned restart prior to restarting, the
restarting node SHOULD originate the IS-IS Link State Protocol data restarting node SHOULD originate the IS-IS Link State Protocol data
units for TE links with 0 as unreserved bandwidth, and if the link units for TE links with 0 as unreserved bandwidth, and if the link
has LSC or FSC as its Switching Capability then also with 0 as Max has LSC or FSC as its Switching Capability then also with 0 as Max
LSP Bandwidth. This would discourage new LSP establishment through LSP Bandwidth. This would discourage new LSP establishment through
the restarting router. the restarting router.
Neighbors of the restarting node SHOULD continue advertise the actual Neighbors of the restarting node SHOULD continue advertise the actual
unreserved bandwidth on the TE links from the neighbors to that node. unreserved bandwidth on the TE links from the neighbors to that node.
5. Normative References 4. Normative References
[GMPLS-ROUTING] Kompella, K., and Rekhter, Y. (Editors), "Routing [GMPLS-ROUTING] Kompella, K., and Rekhter, Y. (Editors), "Routing
Extensions in Support of Generalized MPLS", (work in progress) Extensions in Support of Generalized Multi-Protocol Label
Switching", (work in progress) [draft-ietf-ccamp-gmpls-
routing-08.txt]
[GMPLS-RSVP] Berger, L. (Editors), "Generalized MPLS Signaling - [GMPLS-RSVP] Berger, L., (Editor), "Generalized Multi-Protocol Label
RSVP-TE Extensions", (work in progress) Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003
[GMPLS-SIG] Berger, L. (Editor), "Generalized MPLS - Signaling [GMPLS-SIG] Berger, L. (Editor), "Generalized Multi-Protocol Label
Functional Description", (work in progress) Switching (GMPLS) Signaling Functional Description", RFC 3471,
January 2003
[ISIS-3way] Katz, D., and Saluja, R., "Three-Way Handshake for IS-IS [ISIS-3way] Katz, D., and Saluja, R., "Three-Way Handshake for
Point-to-Point Adjacencies", (work in progress) Intermediate System to Intermediate System (IS-IS) Point-to-Point
Adjacencies", RFC 3373, September 2002
[ISIS-RESTART] Shand, M., "Restart signaling for ISIS", (work in [ISIS-RESTART] Shand, M. and L. Ginsburg, "Restart signaling for
progress) ISIS", (work in progress) [draft-ietf-isis-restart-04.txt]
[ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic [ISIS-TE] Smit, H., Li, T., "IS-IS Extensions for Traffic
Engineering", (work in progress) Engineering", (work in progress) [draft-ietf-isis-traffic-05.txt]
[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.
6. Security Considerations 5. Security Considerations
The extensions proposed in this document do not raise any new This document raises no security concerns beyond those addressed in
security concerns. [ISIS-TE].
7. Acknowledgements 6. Acknowledgements
The authors would like to thank Jim Gibson, Suresh Katukam, Jonathan The authors would like to thank Jim Gibson, Suresh Katukam, Jonathan
Lang and Quaizar Vohra for their comments on the draft. Lang and Quaizar Vohra for their comments on the draft.
8. Contributors 7. Contributors
Ayan Banerjee Ayan Banerjee
Calient Networks Calient Networks
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Phone: +1.408.972.3645 Phone: +1 408 972 3645
Email: abanerjee@calient.net EMail: abanerjee@calient.net
John Drake John Drake
Calient Networks Calient Networks
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Phone: (408) 972-3720 Phone: +1 408 972 3720
Email: jdrake@calient.net EMail: jdrake@calient.net
Greg Bernstein Greg Bernstein
Ciena Corporation Grotto Networking
10480 Ridgeview Court EMail: gregb@grotto-networking.com
Cupertino, CA 94014
Phone: (408) 366-4713
Email: greg@ciena.com
Don Fedyk Don Fedyk
Nortel Networks Corp. Nortel Networks Corp.
600 Technology Park Drive 600 Technology Park Drive
Billerica, MA 01821 Billerica, MA 01821
Phone: +1-978-288-4506 Phone: +1 978 288 4506
Email: dwfedyk@nortelnetworks.com EMail: dwfedyk@nortelnetworks.com
Eric Mannie Eric Mannie
Independent Consultant Independent Consultant
E-mail: eric_mannie@hotmail.com E-mail: eric_mannie@hotmail.com
Debanjan Saha Debanjan Saha
Tellium Optical Systems Tellium Optical Systems
2 Crescent Place 2 Crescent Place
P.O. Box 901 P.O. Box 901
Ocean Port, NJ 07757 Ocean Port, NJ 07757
Phone: (732) 923-4264 Phone: +1 732 923 4264
Email: dsaha@tellium.com EMail: dsaha@tellium.com
Vishal Sharma Vishal Sharma
Metanoia, Inc. EMail: v.sharma@ieee.org
335 Elan Village Lane, Unit 203
San Jose, CA 95134-2539
Phone: +1 408-943-1794
Email: v.sharma@ieee.org
9. Authors' Information 8. Authors' Information
Kireeti Kompella Kireeti Kompella
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave 1194 N. Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: kireeti@juniper.net EMail: kireeti@juniper.net
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave 1194 N. Mathilda Ave
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Email: yakov@juniper.net EMail: yakov@juniper.net
10. Intellectual Property Rights Notices 9. Intellectual Property Rights Notices
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 or other rights that might be claimed to intellectual property 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; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
skipping to change at page 12, line 29 skipping to change at page 12, line 7
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
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 which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/