datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
draft-ietf-ccamp-te-node-cap-05

RFC
Document Stream: IETF
Last updated: 2007-04-04
Replaces: draft-vasseur-ccamp-te-node-cap
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 5073
IANA Action State: RFC-Ed-Ack 
Responsible AD: Ross Callon
Send notices to: ccamp-chairs@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ccamp-te-node-cap.

Abstract:
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]

Authors:
JP Vasseur <jpv@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)