metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5305: IS-IS Extensions for Traffic Engineering

Still current, but amended. Parts of this document are changed or extended by RFC 5307, RFC 8918. Read both.

In plain English — editorial summary, not part of the RFC

This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support Traffic Engineering (TE). This document extends the IS-IS protocol by specifying new information that an Intermediate System (router) can place in Link State Protocol Data Units (LSP). This information describes additional details regarding the state of the network that are useful for traffic engineering computations. [STANDARDS-TRACK]

Document record

Document ID
RFC5305
Published
October 2008
Authors
T. Li; H. Smit
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
17
Also known as
—
Obsoletes:
RFC 3784
Updated by:
RFC 5307, RFC 8918

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5305-is-is-extensions-for-traffic-engineering