Skip to main content

Routing extensions for discovery of Traffic Engineering Node Capabilities

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors JP Vasseur , Jean-Louis Le Roux
Last updated 2011-01-10 (Latest revision 2005-10-04)
Replaced by draft-ietf-ccamp-te-node-cap
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-ccamp-te-node-cap
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


It is highly desired in several cases, to take into account Traffic Engineering (TE) node capabilities during TE LSP path selection, such as for instance the capability to act as a branch LSR of a P2MP LSP. This requires advertising these capabilities within the IGP. For that purpose, this document specifies OSPF and IS-IS traffic engineering extensions for the advertisement of control plane and data plane traffic engineering node capabilities.


JP Vasseur
Jean-Louis Le Roux

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