Skip to main content

IS-IS Traffic Engineering (TE) Metric Extensions
RFC 8570

Revision differences

Document history

Date By Action
2019-08-19
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2019-08-19
Gunter Van de Velde Assignment of request for Last Call review by OPSDIR to Jürgen Schönwälder was marked no-response
2019-03-15
(System)
Received changes through RFC Editor sync (created alias RFC 8570, changed abstract to 'In certain networks, such as, but not limited to, financial information …
Received changes through RFC Editor sync (created alias RFC 8570, changed abstract to '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 IS-IS Traffic Engineering Extensions (RFC 5305). These extensions provide a way to distribute and collect network-performance information in a scalable fashion. The information distributed using IS-IS TE Metric Extensions 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.

This document obsoletes RFC 7810.', changed pages to 21, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-03-15, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-lsr-isis-rfc7810bis and RFC 7810)
2019-03-15
(System) RFC published