CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 08:46:50 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=D4O8UCJ1nHubxA9R3Jx.Vdx5V9CA6eCCKucik36RIEo-1760172410-1.0.1.1-aNAqswI5PFr3x19XT10kwBddVe_oC0HCaTcEhcTd_JQ2o1U5SDjXS1PKeiWnbY.mqlB4jKMOMAWFQ8w9nk5lPryGm6YfJSl2iAHNPMH7q.8; path=/; expires=Sat, 11-Oct-25 09:16:50 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd16d7adf0d86d-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 5543 » RFC Editor
Search RFCs
RFC 5543
BGP Traffic Engineering Attribute, May 2009
- File formats:
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 7606
- Authors:
- H. Ould-Brahim
D. Fedyk
Y. Rekhter - Stream:
- IETF
- Source:
- softwire (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5543
Discuss this RFC: Send questions or comments to the mailing list softwires@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5543
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]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us