draft-ietf-isis-gmpls-extensions-11.txt   draft-ietf-isis-gmpls-extensions-12.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Expiration Date: November 2002 A. Banerjee (Calient Networks) Expiration Date: November 2002 A. Banerjee (Calient Networks)
J. Drake (Calient Networks) J. Drake (Calient Networks)
G. Bernstein (Ciena) G. Bernstein (Ciena)
D. Fedyk (Nortel Networks) D. Fedyk (Nortel Networks)
E. Mannie (GTS Network) E. Mannie (GTS Network)
D. Saha (Tellium) D. Saha (Tellium)
V. Sharma (Metanoia, Inc.) V. Sharma (Metanoia, Inc.)
IS-IS Extensions in Support of Generalized MPLS IS-IS Extensions in Support of Generalized MPLS
draft-ietf-isis-gmpls-extensions-11.txt draft-ietf-isis-gmpls-extensions-12.txt
1. Status of this Memo 1. 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 8, line 12 skipping to change at page 8, line 12
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].
7. Implications on Graceful Restart 7. Implications on Graceful Restart
The restarting node should follow the ISIS restart procedures [ISIS- The restarting node should follow the ISIS restart procedures [ISIS-
RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP]. RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
When the restarting node is going to originate its TE LSAs, these When the restarting node is going to originate its TE LSAs, these
LSAs should be originated with 0 unreserved bandwidth, Traffic LSAs should be originated with 0 unreserved bandwidth, Traffic
Engineering Default metric set to MAX_PATH_METRIC, and if the Link Engineering Default metric set to 0xffffff, and if the Link has LSC
has LSC or FSC as its Switching Capability then also with 0 as Max or FSC as its Switching Capability then also with 0 as Max LSP
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 unreserved
resources, taking into account the resources reserved by the already resources, taking into account the resources reserved by the already
established LSPs that have been preserved across the restart, the established LSPs that have been preserved across the restart, the
node should advertise these resources in its TE LSAs. node should advertise these resources in its TE LSAs.
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 TE LSAs with 0 as unreserved restarting node SHOULD originate the TE LSAs with 0 as unreserved
bandwidth, and if the Link has LSC or FSC as its Switching Capability bandwidth, and if the Link has LSC or FSC as its Switching Capability
 End of changes. 

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