This Working Group did not meet
NOTE: This charter is a snapshot of the 60th IETF Meeting in San Diego, CA USA. It may now be out-of-date.
Last Modified: 2003-12-18
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.
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 | |
Jan 04 | Progress operational TE MIB to AD review | |
Jan 04 | Submit MPLS Inter-AS TE requirements to IESG |
RFC | Status | Title |
---|---|---|
RFC3272 | I | Overview and Principles of Internet Traffic Engineering |
RFC3346 | I | Applicability Statement for Traffic Engineering with MPLS |
RFC3386 | I | Network Hierarchy and Multilayer Survivability |
RFC3564 | I | Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering |
RFC3785 | BCP | Use of Interior Gateway Protocol Metric as a second MPLS Traffic Engineering Metric |