RFC 5543 · PROPOSED STANDARD · 2009
WED · 29 JUL 2026
BGP Traffic Engineering Attribute
Overview
RFC 5543, “BGP Traffic Engineering Attribute”, is a Proposed Standard document published in May 2009 by H. Ould-Brahim, D. Fedyk, Y. Rekhter. It has since been updated by RFC 7606. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 5543 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2009
- RFC 5542 Definitions of Textual Conventions for Pseudowire Management
- RFC 5541 Encoding of Objective Functions in the Path Computation Element Communication Protocol
- RFC 5545 Internet Calendaring and Scheduling Core Object Specification
- RFC 5540 40 Years of RFCs
- RFC 5546 iCalendar Transport-Independent Interoperability Protocol
- RFC 5539 NETCONF over Transport Layer Security
- RFC 5547 A Session Description Protocol Offer/Answer Mechanism to Enable File Transfer
- RFC 5548 Routing Requirements for Urban Low-Power and Lossy Networks