[rfc-dist] RFC 4972 on Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Jul 31 18:08:33 PDT 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4972

        Title:      Routing Extensions for Discovery of 
                    Multiprotocol (MPLS) Label Switch Router (LSR) 
                    Traffic Engineering (TE) Mesh Membership 
        Author:     JP. Vasseur, Ed.,
                    JL. Leroux, Ed.,
                    S. Yasukawa, S. Previdi,
                    P. Psenak, P. Mabbey
        Status:     Standards Track
        Date:       July 2007
        Mailbox:    jpv at cisco.com, 
                    jeanlouis.leroux at orange-ftgroup.com, 
                    s.yasukawa at hco.ntt.co.jp, sprevidi at cisco.com, 
                    ppsenak at cisco.com, Paul_Mabey at cable.comcast.com
        Pages:      15
        Characters: 32044
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-automesh-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4972.txt

The setup of a full mesh of Multi-Protocol Label Switching (MPLS)
Traffic Engineering (TE) Label Switched Paths (LSP) among a set of
Label Switch Routers (LSR) is a common deployment scenario of MPLS
Traffic Engineering either for bandwidth optimization, bandwidth
guarantees or fast rerouting with MPLS Fast Reroute.  Such deployment
may require the configuration of a potentially large number of TE
LSPs (on the order of the square of the number of LSRs).  This document
specifies Interior Gateway Protocol (IGP) routing extensions for
Intermediate System-to-Intermediate System (IS-IS) and Open Shortest
Path First (OSPF) so as to provide an automatic discovery of the set
of LSRs members of a mesh in order to automate the creation of such
mesh of TE LSPs.  [STANDARDS TRACK]

This document is a product of the Common Control and Measurement Plane
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.Please refer to the current edition of the Internet
 Official Protocol Standards (STD 1) for the standardization state and
 status of this protocol.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list