Skip to main content

Overview and Principles of Internet Traffic Engineering

Approval announcement
Draft of message to be sent after approval:


From: The IESG <>
To: IETF-Announce <>
Cc: The IESG <>,,,,,,
Subject: Document Action: 'Overview and Principles of Internet Traffic Engineering' to Informational RFC (draft-ietf-teas-rfc3272bis-27.txt)

The IESG has approved the following document:
- 'Overview and Principles of Internet Traffic Engineering'
  (draft-ietf-teas-rfc3272bis-27.txt) as Informational RFC

This document is the product of the Traffic Engineering Architecture and
Signaling Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:

Ballot Text

Technical Summary

   This document 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 the networks that support IP networking, 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 networks are also discussed.

   This work was first published as RFC 3272 in May 2002.  This document
   obsoletes RFC 3272 by making a complete update to bring the text in
   line with best current practices for Internet traffic engineering and
   to include references to the latest relevant work in the IETF.

Working Group Summary

   Document shepherd reports "There was broad agreement in the WG 
   to progress this document", with no controversy or rough points 
   to the consensus.

Document Quality

   It's an informational overview; as such "existing implementations"
   aren't relevant. Reviewers agree the document is well-structured
   and well-written.


   The Document Shepherd for this document is Vishnu Pavan Beeram. The
   Responsible Area Director is John Scudder.

RFC Editor Note

RFC Editor Note

Two minor nits I noticed when reviewing the approved version --

  Note that QUIC [RFC9000] natively support the switching and steering

Should be “supports”, and

                  [RFC5472] describes the
  applicability of IPFIX and makes a comparison with RTFM, pointing out
  that, architecturally, while RTM talks about devices, IPFIX deals
  with processed to clarify that multiple of those processes may be co-
  located on the same machine.

Should be “deals with processes”.