Internet Traffic Engineering (tewg)

Last Modified: 2004-08-16


Ed Kern <>
Jim Boyle <>

Sub-IP Area Director(s):

Bert Wijnen <>
Alex Zinin <>

Sub-IP Area Advisor:

Bert Wijnen <>

Mailing Lists:

General Discussion:
To Subscribe:
In Body: subscribe

Description of Working Group:

Internet Traffic Engineering is defined as that aspect of Internet
network engineering concerned with the performance optimization of
traffic handling in operational networks, with the main focus of the
optimization being minimizing over-utilization of capacity when other
capacity is available in the network. Traffic Engineering entails that
aspect of network engineering which is concerned with the design,
provisioning, and tuning of operational internet networks.  It applies
business goals, technology and scientific principles to the
modeling, characterization, and control of internet traffic, and the
application of such knowledge and techniques to achieve specific
and performance objectives, including the reliable and expeditious
movement of traffic through the network, the efficient utilization of
network resources, and the planning of network capacity.

The Internet Traffic Engineering Working Group defines, develops,
specifies, and recommends principles, techniques, and mechanisms for
traffic engineering in the internet.  The working group also serves as
general forum for discussing improvements to IETF protocols to advance
the traffic engineering function.

The primary focus of the tewg is the measurement and control aspects of
intra-domain internet traffic engineering.  This includes provisioning,
measurement and control of intra-domain routing, and measurement and
control aspects of intra-domain network resource allocation. Techniques
already in use or in advanced development for traffic engineering
include ATM and Frame Relay overlay models, MPLS based approaches,
constraint-based routing, and traffic engineering methodologies in
Diffserv environments.  The tewg describes and characterizes these and
other techniques, documents how they fit together, and identifies
scenarios in which they are useful.

The working group may also consider the problems of traffic engineering
across autonomous systems boundaries.

The tewg interacts with the common control and measurement plane
group to abstract and define those parameters, measurements, and
controls that traffic engineering needs in order to engineer the

The tewg also interacts with other groups whose scopes intersect, e.g.
mpls, is-is, ospf, diffserv, ippm, rap, rtfm, policy, rmonmib, disman,

The work items to be undertaken by TE WG encompass the following

- BCP documents on ISP uses, requirements, desires (TEBCPs)

- Operational TE MIB (TEMIB)

- Document additional measurements needed for TE (TEM)

- TE interoperability & implementation informational notes (TEIMP)

- Traffic Engineering Applicability Statement (TEAPP)

For the time being, it also is covering the area of verification that
diffserv is achievable in traffic engineered SP networks.  This will
entail verification and review of the Diffserv requirements in the the
WG Framework document and initial specification of how these
requirements can be met through use and potentially expansion of
existing protocols.

Goals and Milestones:

Done    Solicit TEBCP drafts concerning requirements, approaches, lessons learned from use (or non use) of TE techniques in operational provider environments.
Done    Review and comment on operational TEMIB
Done    TEBCPs submitted for WG comment
Done    Comments to TEBCP authors for clarifications
Done    First draft of TEAPP
Done    First draft of TEM
Done    TE Framework Draft to AD/IESG for review.
Done    Drafts available for E-LSP and L-LSP Diffserv TE
Done    Another update of operational TEMIB draft
Done    All comments back on TE Diffserv requirements
Done    Submit revised TEBCPs and REAPP to AD/IESG for review
Done    Any necessary protocol extensions for Diffserv TE sent to protocol relevant WGs for review
Done    Progress Diffserv TE E-LSP and L-LSP Diffserv TE drafts together to AD/IESG for review
Done    Progress operational TE MIB to AD review
Done    Submit MPLS Inter-AS TE requirements to IESG

No Current Internet-Drafts

Request For Comments:

Overview and Principles of Internet Traffic Engineering (RFC 3272) (190384 bytes)
Applicability Statement for Traffic Engineering with MPLS (RFC 3346) (33754 bytes)
Network Hierarchy and Multilayer Survivability (RFC 3386) (65345 bytes)
Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering (RFC 3564) (50808 bytes)
Use of Interior Gateway Protocol Metric as a second MPLS Traffic Engineering Metric (RFC 3785) (0 bytes)
A Traffic Engineering MIB (RFC 3970) (0 bytes)
Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering (RFC 4124) (79265 bytes)
Russian Dolls Bandwidth Constraints Model for Diff-Serv-aware MPLS Traffic Engineering (RFC 4127) (23694 bytes)
Max Allocation with Reservation Bandwidth Constraint Model for MPLS/DiffServ TE & Performance Comparisons (RFC 4126) (51232 bytes)
MPLS Inter-Autonomous System (AS)Traffic Engineering (TE) Requirements (RFC 4216) (64640 bytes)
Maximum Allocation Bandwidth Constraints Model for Diff-Serv-aware MPLS Traffic Engineering (RFC 4125) (22585 bytes)
Requirements for Inter-area MPLS Traffic Engineering (RFC 4105) (50111 bytes)