A new Request for Comments is now available in online RFC libraries.
RFC 4736
Title: Reoptimization of Multiprotocol Label Switching
(MPLS) Traffic Engineering (TE) Loosely Routed
Label Switched Path (LSP)
Author: JP. Vasseur, Ed.,
Y. Ikejiri, R. Zhang
Status: Informational
Date: November 2006
Mailbox: jpv@cisco.com,
y.ikejiri@ntt.com,
raymond_zhang@bt.infonet.com
Pages: 14
Characters: 28850
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ccamp-loose-path-reopt-02.txt
URL: http://www.rfc-editor.org/rfc/rfc4736.txt
This document defines a mechanism for the reoptimization of loosely
routed MPLS and GMPLS (Generalized Multiprotocol Label Switching)
Traffic Engineering (TE) Label Switched Paths (LSPs) signaled with
Resource Reservation Protocol Traffic Engineering (RSVP-TE). This
document proposes a mechanism that allows a TE LSP head-end Label
Switching Router (LSR) to trigger a new path re-evaluation on every hop
that has a next hop defined as a loose or abstract hop and a mid-point
LSR to signal to the head-end LSR that a better path exists (compared to
the current path) or that the TE LSP must be reoptimized (because of
maintenance required on the TE LSP path). The proposed mechanism
applies to the cases of intra- and inter-domain (Interior Gateway
Protocol area (IGP area) or Autonomous System) packet and non-packet
TE LSPs following a loosely routed path. This memo provides information
for the Internet community.
This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
