[Teas] Document Action: 'Overview and Principles of Internet Traffic Engineering' to Informational RFC (draft-ietf-teas-rfc3272bis-27.txt)
The IESG <iesg-secretary@ietf.org> Fri, 18 August 2023 22:57 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: teas@ietf.org
Delivered-To: teas@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF4CAC14CE2E; Fri, 18 Aug 2023 15:57:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 11.8.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-teas-rfc3272bis@ietf.org, jgs@juniper.net, rfc-editor@rfc-editor.org, teas-chairs@ietf.org, teas@ietf.org, vishnupavan@gmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Message-ID: <169239944897.56335.16088761389304004095@ietfa.amsl.com>
Date: Fri, 18 Aug 2023 15:57:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Xp9jt_AoNZBtTQNN_3uy1vn_oEw>
Subject: [Teas] Document Action: 'Overview and Principles of Internet Traffic Engineering' to Informational RFC (draft-ietf-teas-rfc3272bis-27.txt)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2023 22:57:29 -0000
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: https://datatracker.ietf.org/doc/draft-ietf-teas-rfc3272bis/ 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. Personnel The Document Shepherd for this document is Vishnu Pavan Beeram. The Responsible Area Director is John Scudder. RFC Editor Note Two minor nits I noticed when reviewing the approved version -- Note that QUIC [RFC9000] natively support the switching and steering functions. 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”.