RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8570
- Published
- March 2019
- Authors
- L. Ginsberg; S. Previdi; S. Giacalone; D. Ward; J. Drake; Q. Wu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
- Obsoletes:
- RFC 7810
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8500IS-IS Routing with Reverse MetricCurrent
February 2019
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 9666Area Proxy for IS-ISCurrent
October 2024
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 8541Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loopsCurrent
March 2019
- RFC 8518Selection of Loop-Free Alternates for Multi-Homed PrefixesCurrent
March 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?