Internet Traffic Engineering (tewg)

This Working Group did not meet

NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 03/25/2002

Chair(s):
Ed Kern <ejk@tech.org>
Jim Boyle <jboyle@pdnets.com>
Sub-IP Area Director(s):
Scott Bradner <sob@harvard.edu>
Bert Wijnen <bwijnen@lucent.com>
Sub-IP Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Mailing Lists:
General Discussion: te-wg@ops.ietf.org
To Subscribe: te-wg-request@ops.ietf.org
In Body: subscribe
Archive: http://ops.ietf.org/lists/te-wg
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 measurement, modeling, characterization, and control of internet traffic, and the application of such knowledge and techniques to achieve specific service 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 a 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 working group to abstract and define those parameters, measurements, and controls that traffic engineering needs in order to engineer the network.

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

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

- 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
OCT 01  Submit TEM draft for AD review
OCT 01  Progress operational TE MIB to AD review
NOV 01  Any necessary protocol extensions for Diffserv TE sent to protocol relevant WGs for review.
DEC 01  Recharter
JAN 02  Progress Diffserv TE E-LSP and L-LSP Diffserv TE drafts together to AD/IESG for review
Internet-Drafts:
  • - draft-owens-te-network-survivability-03.txt
  • - draft-ietf-tewg-mib-02.txt
  • - draft-ietf-tewg-qos-routing-04.txt
  • - draft-ietf-tewg-diff-te-reqts-05.txt
  • - draft-srisuresh-ospf-te-02.txt
  • - draft-ietf-tewg-measure-02.txt
  • - draft-ietf-tewg-restore-hierarchy-00.txt
  • - draft-ietf-tewg-te-applicability-01.txt
  • - draft-ietf-tewg-diff-te-proto-01.txt
  • - draft-ietf-tewg-te-metric-igp-00.txt
  • Request For Comments:
    RFCStatusTitle
    RFC3272 I Overview and Principles of Internet Traffic Engineering

    Current Meeting Report

    None received.

    Slides

    None received.