draft-ietf-mpls-te-feed-02.txt   draft-ietf-mpls-te-feed-03.txt 
MPLS Working Group Peter Ashwood-Smith MPLS Working Group Peter Ashwood-Smith
Internet Draft Bilel Jamoussi Internet Draft Bilel Jamoussi
Expiration Date: December 2001 Don Fedyk Expiration Date: May 2002 Don Fedyk
Darek Skalecki Darek Skalecki
Nortel Networks Nortel Networks
July 2001 November 2001
Improving Topology Data Base Accuracy with LSP Feedback Improving Topology Data Base Accuracy with LSP Feedback
draft-ietf-mpls-te-feed-02.txt draft-ietf-mpls-te-feed-03.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 8, line 15 skipping to change at page 8, line 15
the reverse flowing mapping. the reverse flowing mapping.
When an LDP session goes down either because of a link failure, When an LDP session goes down either because of a link failure,
TCP/IP timeout, keep alive timeout, adjacency timeout etc. Other LDP TCP/IP timeout, keep alive timeout, adjacency timeout etc. Other LDP
sessions in the module must generate either notification, withdraw sessions in the module must generate either notification, withdraw
or release messages for LSPs that traversed the LDP in question. In or release messages for LSPs that traversed the LDP in question. In
the case that the LSP was created by CR-LDP and that a withdraw or the case that the LSP was created by CR-LDP and that a withdraw or
notification is about to be generated, LDP will insert a feedback notification is about to be generated, LDP will insert a feedback
TLV for the interface which just went down that contains 0's for all TLV for the interface which just went down that contains 0's for all
the bandwidth values and attach to it the proper interface the bandwidth values and attach to it the proper interface
addresses. addresses. Where LDP FT procedures [LDP-FT] are in use, LSPs that
are protected by FT procedures should not be torn down until after
session reestablishment has failed. During LDP re-establishment
time new connections may be queued and delayed for the re-
establishment time. If signaling delay is undesirable feedback may
be used to report zero bandwidth. In this case, if LDP is
successfully re-established a Link LSA should be triggered if
sufficient amount bandwidth is available.
When the LDP session that originated a CR-LDP label request receives When the LDP session that originated a CR-LDP label request receives
a mapping that contains feedback TLV's it is recommended that these a mapping that contains feedback TLV's it is recommended that these
bandwidth values supersede the corresponding values in the node's bandwidth values supersede the corresponding values in the node's
topology database for source route computations. Doing so permits topology database for source route computations. Doing so permits
this node to immediately synchronize its topology with respect to this node to immediately synchronize its topology with respect to
the real bandwidth reservations along the path that was just the real bandwidth reservations along the path that was just
established. established.
When the LDP session that originated a CR-LDP label request receives When the LDP session that originated a CR-LDP label request receives
skipping to change at page 9, line 49 skipping to change at page 9, line 58
12. References 12. References
[CR-LDP] Jamoussi, B. et al., _Constraint-Based LSP Setup using [CR-LDP] Jamoussi, B. et al., _Constraint-Based LSP Setup using
LDP_, Internet Draft, draft-ietf-mpls-cr-ldp-05.txt, February 2001. LDP_, Internet Draft, draft-ietf-mpls-cr-ldp-05.txt, February 2001.
[LDP] Andersson, L. et al., _LDP Specification_, RFC 3032, January [LDP] Andersson, L. et al., _LDP Specification_, RFC 3032, January
2001. 2001.
[IS-IS] Li, T., Smit, H., _Extensions to IS-IS for traffic [IS-IS] Li, T., Smit, H., _Extensions to IS-IS for traffic
engineering_, Internet Draft, draft-ietf-isis-traffic-03.txt, June engineering_, Internet Draft, draft-ietf-isis-traffic-04.txt, August
2001. 2001.
[OSPF] Katz, Dave and Yeung, Derek, "Traffic Engineering Extensions
to OSPF," draft-katz-yeung-ospf-traffic-04.txt, February 2001.
[QUERY] Ashwood-Smith, P., Paraschiv, A., _MPLS LDP Query Message [QUERY] Ashwood-Smith, P., Paraschiv, A., _MPLS LDP Query Message
Description_, Internet Draft, draft-anto-ldp-query-02.txt, May 2001 Description_, Internet Draft, draft-anto-ldp-query-03.txt, August
2001.
[LDP-FT] Farrel, A et al., _Fault Tolerance for LDP and CR-LDP_,
13. Author's Addresses 13. Author's Addresses
Peter Ashwood-Smith Bilel Jamoussi Peter Ashwood-Smith Bilel Jamoussi
Nortel Networks Corp. Nortel Networks Corp. Nortel Networks Corp. Nortel Networks Corp.
P.O. Box 3511 Station C, 600 Technology Park Drive P.O. Box 3511 Station C, 600 Technology Park Drive
Ottawa, ON K1Y 4H7 Billerica, MA 01821 Ottawa, ON K1Y 4H7 Billerica, MA 01821
Canada USA Canada USA
Phone: +1 613-763-4534 phone: +1 978-288-4506 Phone: +1 613-763-4534 phone: +1 978-288-4506
petera@nortelnetworks.com jamoussi@nortelnetworks.com petera@nortelnetworks.com jamoussi@nortelnetworks.com
 End of changes. 

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