[rfc-dist] RFC 5073 on IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Dec 12 15:05:01 PST 2007


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

        
        RFC 5073

        Title:      IGP Routing Protocol Extensions for 
                    Discovery of Traffic Engineering Node Capabilities 
        Author:     J.P. Vasseur, Ed.,
                    J.L. Le Roux, Ed.
        Status:     Standards Track
        Date:       December 2007
        Mailbox:    jpv at cisco.com, 
                    jeanlouis.leroux at orange-ftgroup.com
        Pages:      13
        Characters: 27004
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-te-node-cap-05.txt

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

It is highly desired, in several cases, to take into account Traffic
Engineering (TE) node capabilities during Multi Protocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineered Label
Switched Path (TE-LSP) selection, such as, for instance, the
capability to act as a branch Label Switching Router (LSR) of a
Point-To-MultiPoint (P2MP) LSP.  This requires advertising these
capabilities within the Interior Gateway Protocol (IGP).  For that
purpose, this document specifies Open Shortest Path First (OSPF) and
Intermediate System-Intermediate System (IS-IS) traffic engineering
extensions for the advertisement of control plane and data plane
traffic engineering node capabilities.  [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