RFC 3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5305.
Current version: RFC 5305 — IS-IS Extensions for Traffic Engineering
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 (LSP) Data Units. This information describes additional details regarding the state of the network that are useful for traffic engineering computations. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3784
- Published
- June 2004
- Authors
- H. Smit; T. Li
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
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.
- RFC 5130A Policy Control Mechanism in IS-IS Using Administrative TagsCurrent
February 2008
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 4003GMPLS Signaling Procedure for Egress ControlCurrent
February 2005
- RFC 4090Fast Reroute Extensions to RSVP-TE for LSP TunnelsUpdated
May 2005
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4208Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay ModelCurrent
October 2005
- RFC 3270Multi-Protocol Label Switching (MPLS) Support of Differentiated ServicesUpdated
May 2002
- RFC 3214LSP Modification Using CR-LDPCurrent
January 2002
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?