RFC 3272: Overview and Principles of Internet Traffic Engineering
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9522.
Current version: RFC 9522 — Overview and Principles of Internet Traffic Engineering
In plain English — editorial summary, not part of the RFC
This memo describes the principles of Traffic Engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks, and to provide a common basis for the development of traffic engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational IP networks are discussed throughout this document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3272
- Published
- May 2002
- Authors
- D. Awduche; A. Chiu; A. Elwalid; I. Widjaja; X. Xiao
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sub
- Pages
- 71
- 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 3753Mobility Related TerminologyCurrent
June 2004
- RFC 3346Applicability Statement for Traffic Engineering with MPLSCurrent
August 2002
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 3260New Terminology and Clarifications for DiffservCurrent
April 2002
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
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?