Internet Traffic Engineering (tewg) Concluded WG

Note: The data for concluded WGs is occasionally incorrect.

WG Name Internet Traffic Engineering
Acronym tewg
Area Sub-IP Area (sub)
State Concluded
Charter charter-ietf-tewg-01 Approved
Dependencies Document dependency graph (SVG)
Personnel Chairs Ed Kern
Jim Boyle
Area Director Bert Wijnen
Mailing list Address
To subscribe

Charter for 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.


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