RFC 5543: BGP Traffic Engineering Attribute
In plain English — editorial summary, not part of the RFC
This document defines a new BGP attribute, the Traffic Engineering attribute, that enables BGP to carry Traffic Engineering information. The scope and applicability of this attribute currently excludes its use for non-VPN reachability information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5543
- Published
- May 2009
- Authors
- H. Ould-Brahim; D. Fedyk; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
- Updated by:
- RFC 7606
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5549Advertising IPv4 Network Layer Reachability Information with an IPv6 Next HopObsoleted
May 2009
- RFC 5535Hash-Based Addresses (HBA)Current
June 2009
- RFC 5534Failure Detection and Locator Pair Exploration Protocol for IPv6 MultihomingCurrent
June 2009
- RFC 5533Shim6: Level 3 Multihoming Shim Protocol for IPv6Current
June 2009
- RFC 5555Mobile IPv6 Support for Dual Stack Hosts and RoutersUpdated
June 2009
- RFC 5522Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile NetworksCurrent
October 2009
- RFC 5565Softwire Mesh FrameworkCurrent
June 2009
- RFC 5566BGP IPsec Tunnel Encapsulation AttributeObsoleted
June 2009
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?