draft-ietf-mpls-rsvp-lsp-fastreroute-06.txt   draft-ietf-mpls-rsvp-lsp-fastreroute-07.txt 
Internet Draft Ping Pan, Ed (Ciena Corp) Internet Draft Ping Pan, Ed (Ciena Corp)
Expires: November 2004 George Swallow, Ed (Cisco Systems) Expires: February 2005 George Swallow, Ed (Cisco Systems)
Alia Atlas, Ed (Avici Systems) Alia Atlas, Ed (Avici Systems)
Fast Reroute Extensions to RSVP-TE for LSP Tunnels Fast Reroute Extensions to RSVP-TE for LSP Tunnels
draft-ietf-mpls-rsvp-lsp-fastreroute-06.txt draft-ietf-mpls-rsvp-lsp-fastreroute-07.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 12, line 20 skipping to change at page 12, line 20
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| Setup Prio | Hold Prio | Hop-limit | Reserved | | Setup Prio | Hold Prio | Hop-limit | Reserved |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| Bandwidth | | Bandwidth |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| Include-any | | Include-any |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
| Exclude-any | | Exclude-any |
+-------------+-------------+-------------+-------------+ +-------------+-------------+-------------+-------------+
Unknown C-types should be treated as specified in [RSVP] Section
3.10.
5.2. DETOUR Object 5.2. DETOUR Object
The DETOUR object is used in one-to-one backup to identify detour The DETOUR object is used in one-to-one backup to identify detour
LSPs. It has the following format: LSPs. It has the following format:
Class-Num = 63 Class-Num = 63
5.2.1 DETOUR object for IPv4 address 5.2.1 DETOUR object for IPv4 address
C-Type = 7 C-Type = 7
skipping to change at page 14, line 18 skipping to change at page 14, line 20
a DETOUR object. If detour merging is desired, after each merging a DETOUR object. If detour merging is desired, after each merging
operation, the Detour Merge Point should combine all the merged operation, the Detour Merge Point should combine all the merged
detours in the subsequent Path messages. detours in the subsequent Path messages.
The high-order bit of the C-Class is zero; LSRs that do not support The high-order bit of the C-Class is zero; LSRs that do not support
the DETOUR objects MUST reject any Path message containing a DETOUR the DETOUR objects MUST reject any Path message containing a DETOUR
object and send a PathErr to notify the PLR. This PathErr SHOULD object and send a PathErr to notify the PLR. This PathErr SHOULD
be generated as specified in [RSVP] for unknown objects with a be generated as specified in [RSVP] for unknown objects with a
class-num of the form "0bbbbbbb". class-num of the form "0bbbbbbb".
Unknown C-types should be treated as specified in [RSVP] Section
3.10.
5.3. SESSION_ATTRIBUTE Flags 5.3. SESSION_ATTRIBUTE Flags
To explicitly request bandwidth and node protection, two new flags To explicitly request bandwidth and node protection, two new flags
are defined in the SESSION_ATTRIBUTE object. are defined in the SESSION_ATTRIBUTE object.
For both C-Type 1 and 7, the SESSION_ATTRIBUTE object currently has For both C-Type 1 and 7, the SESSION_ATTRIBUTE object currently has
the following flags defined: the following flags defined:
Local protection desired: 0x01 Local protection desired: 0x01
skipping to change at page 34, line 36 skipping to change at page 34, line 40
IANA will assign C-Type 1 for the standard FAST_REROUTE object IANA will assign C-Type 1 for the standard FAST_REROUTE object
format defined in section 5.1 and list C-Type 7 as reserved as it format defined in section 5.1 and list C-Type 7 as reserved as it
is still used by pre-standard implementations. Future C-Types is still used by pre-standard implementations. Future C-Types
will be assigned using the following guidelines: will be assigned using the following guidelines:
C-Types 0 through 127 are assigned by Standards Action. C-Types 0 through 127 are assigned by Standards Action.
C-Types 128 through 191 are assigned by Expert Review. C-Types 128 through 191 are assigned by Expert Review.
C-Types 192 through 255 are reserved for Vendor Private Use. C-Types 192 through 255 are reserved for Vendor Private Use.
For C-Types in the range 192 through 255, the first four octets of
the FAST_REROUTE object after the C-Type MUST be the Vendor's SMI
Network Management Private Enterprise Code (see [ENT]) in network
byte order.
IANA will assign C-Types 7 and 8 to the IPv4 and IPv6 DETOUR object IANA will assign C-Types 7 and 8 to the IPv4 and IPv6 DETOUR object
formats as defined in section 5.2. Future C-Types will be formats as defined in section 5.2. Future C-Types will be
assigned using the following guidelines: assigned using the following guidelines:
C-Types 0 through 127 are assigned by Standards Action. C-Types 0 through 127 are assigned by Standards Action.
C-Types 128 through 191 are assigned by Expert Review. C-Types 128 through 191 are assigned by Expert Review.
C-Types 192 through 255 are reserved for Vendor Private Use. C-Types 192 through 255 are reserved for Vendor Private Use.
For C-Types in the range 192 through 255, the first four octets of
the DETOUR object after the C-Type MUST be the Vendor's SMI Network
Management Private Enterprise Code (see [ENT]) in network byte order.
12. Intellectual Property Considerations 12. Intellectual Property Considerations
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
skipping to change at page 36, line 25 skipping to change at page 36, line 38
[RSVP-TE] D. Awduche, et al, "RSVP-TE: Extensions to RSVP for LSP [RSVP-TE] D. Awduche, et al, "RSVP-TE: Extensions to RSVP for LSP
tunnels", RFC3029, December 2001. tunnels", RFC3029, December 2001.
[RFC-WORDS] Bradner, S., "Key words for use in RFCs to Indicate [RFC-WORDS] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC-IANA] T. Narten and H. Alvestrand, "Guidelines for Writing an [RFC-IANA] T. Narten and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 2434. IANA Considerations Section in RFCs", RFC 2434.
[ENT] IANA PRIVATE ENTERPRISE NUMBERS,
http://www.iana.org/assignments/enterprise-numbers
16. Editor Information 16. Editor Information
George Swallow George Swallow
Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road 300 Beaver Brook Road
Boxborough, MA 01719 Boxborough, MA 01719
USA USA
email: swallow@cisco.com email: swallow@cisco.com
phone: +1 978 244 8143 phone: +1 978 244 8143
Ping Pan Ping Pan
CIENA Corp. 640 Clyde Court
5965 Silver Creek Valley Road Mountain View, CA 94043
San Jose, CA 95138
USA USA
e-mail: ppan@ciena.net e-mail: ppan@hammerheadsystems.com
phone: +1 408 965 2707
Alia Atlas Alia Atlas
Avici Systems Avici Systems
101 Billerica Avenue 101 Billerica Avenue
N. Billerica, MA 01862 N. Billerica, MA 01862
USA USA
email: aatlas@avici.com email: aatlas@avici.com
phone: +1 978 964 2070 phone: +1 978 964 2070
 End of changes. 

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