OSPF Traffic Engineering (TE) Express Path

Document Type Expired Internet-Draft (individual)
Authors Spencer Giacalone  , David Ward  , John Drake  , Alia Atlas  , Stefano Previdi 
Last updated 2012-03-26 (latest revision 2011-09-21)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In certain networks, such as, but not limited to, financial information networks (e.g. stock market data providers), network performance criteria (e.g. latency) are becoming as critical to data path selection as other metrics. This document describes extensions to OSPF TE [RFC3630] such that network performance information can be distributed and collected in a scalable fashion. The information distributed using OSPF TE Express Path can then be used to make path selection decisions based on network performance. Note that this document only covers the mechanisms with which network performance information is distributed. The mechanisms for measuring network performance or acting on that information, once distributed, are outside the scope of this document.


Spencer Giacalone (Spencer.giacalone@thomsonreuters.com)
David Ward (dward@cisco.com)
John Drake (jdrake@juniper.net)
Alia Atlas (akatlas@juniper.net)
Stefano Previdi (sprevidi@cisco.com)

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