--- 1/draft-ietf-ccamp-ospf-gmpls-extensions-06.txt	2006-02-04 22:57:58.000000000 +0100
+++ 2/draft-ietf-ccamp-ospf-gmpls-extensions-07.txt	2006-02-04 22:57:58.000000000 +0100
@@ -1,24 +1,24 @@
 
 CCAMP Working Group                       K. Kompella (Juniper Networks)
 Internet Draft                            Y. Rekhter  (Juniper Networks)
-Expiration Date: October 2002             A. Banerjee (Calient Networks)
+Expiration Date: November 2002            A. Banerjee (Calient Networks)
                                           J. Drake    (Calient Networks)
                                           G. Bernstein (Ciena)
                                           D. Fedyk    (Nortel Networks)
                                           E. Mannie   (GTS Network)
                                           D. Saha     (Tellium)
                                           V. Sharma   (Metanoia, Inc.)
 
              OSPF Extensions in Support of Generalized MPLS
 
-             draft-ietf-ccamp-ospf-gmpls-extensions-06.txt
+             draft-ietf-ccamp-ospf-gmpls-extensions-07.txt
 
 1. Status of this Memo
 
    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
    other groups may also distribute working documents as Internet-
    Drafts.
@@ -280,28 +280,29 @@
    Descriptor" of [GMPLS-ROUTING]) the Interface Switching Capability
    Descriptor sub-TLV may occur more than once within the Link TLV.
 
 7. Implications on Graceful Restart
 
    The restarting node should follow the OSPF restart procedures [OSPF-
    RESTART], and the RSVP-TE restart procedures [GMPLS-RSVP].
 
    When a restarting node is going to originate its TE LSAs, the TE LSAs
    containing Link TLV should be originated with 0 unreserved bandwidth,
-   and if the Link has LSC or FSC as its Switching Capability then also
-   with 0 as Max LSP Bandwidth, until the node is able to determine the
-   amount of unreserved resources taking into account the resources
-   reserved by the already established LSPs that have been preserved
-   across the restart. Once the restarting node determines the amount of
-   unreserved resources, taking into account the resources reserved by
+   Traffic Engineering metric set to 0xffffffff, and if the Link has LSC
+   or FSC as its Switching Capability then also with 0 as Max LSP
+   Bandwidth, until the node is able to determine the amount of
+   unreserved resources taking into account the resources reserved by
    the already established LSPs that have been preserved across the
-   restart, the node should advertise these resources in its TE LSAs.
+   restart. Once the restarting node determines the amount of unreserved
+   resources, taking into account the resources reserved by the already
+   established LSPs that have been preserved across the restart, the
+   node should advertise these resources in its TE LSAs.
 
    In addition in the case of a planned restart prior to restarting, the
    restarting node SHOULD originate the TE LSAs containing Link TLV with
    0 as unreserved bandwidth, and if the Link has LSC or FSC as its
    Switching Capability then also with 0 as Max LSP Bandwidth.  This
    would discourage new LSP establishment through the restarting router.
 
    Neighbors of the restarting node should continue advertise the actual
    unreserved bandwidth on the TE links from the neighbors to that node.