RFC 4736 on Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)
rfc-editor@rfc-editor.org Sat, 11 November 2006 02:08 UTC
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiiIL-0000Ze-1H for ccamp-archive@ietf.org; Fri, 10 Nov 2006 21:08:33 -0500
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiiIJ-0006Dz-Nm for ccamp-archive@ietf.org; Fri, 10 Nov 2006 21:08:33 -0500
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from <owner-ccamp@ops.ietf.org>) id 1Gii8x-000Pa6-FE for ccamp-data@psg.com; Sat, 11 Nov 2006 01:58:51 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-16.7 required=5.0 tests=AWL,BAYES_00,NO_REAL_NAME, USER_IN_DEF_WHITELIST autolearn=no version=3.1.6
Received: from [128.9.160.116] (helo=nit.isi.edu) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from <apache@nit.isi.edu>) id 1Gii8w-000PYu-Hm for ccamp@ops.ietf.org; Sat, 11 Nov 2006 01:58:51 +0000
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kAB1wlus019694; Fri, 10 Nov 2006 17:58:47 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kAB1wlsP019693; Fri, 10 Nov 2006 17:58:47 -0800
Date: Fri, 10 Nov 2006 17:58:47 -0800
Message-Id: <200611110158.kAB1wlsP019693@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 4736 on Reoptimization of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Loosely Routed Label Switched Path (LSP)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ccamp@ops.ietf.org
Sender: owner-ccamp@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.2 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
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 ...