[Teas] RFC 9522 on Overview and Principles of Internet Traffic Engineering

rfc-editor@rfc-editor.org Sun, 28 January 2024 22:36 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885E9C14F69F; Sun, 28 Jan 2024 14:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6fErh8ZHdSR; Sun, 28 Jan 2024 14:36:29 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46D00C14F68E; Sun, 28 Jan 2024 14:36:29 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F1688193A2CD; Sun, 28 Jan 2024 14:36:28 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240128223628.F1688193A2CD@rfcpa.amsl.com>
Date: Sun, 28 Jan 2024 14:36:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/HCH6F3DPwQ9KUrMEZW7LSf9u2iM>
Subject: [Teas] RFC 9522 on Overview and Principles of Internet Traffic Engineering
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Sun, 28 Jan 2024 22:36:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9522

        Title:      Overview and Principles of Internet 
                    Traffic Engineering 
        Author:     A. Farrel, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       January 2024
        Mailbox:    adrian@olddog.co.uk
        Pages:      73
        Obsoletes:  RFC 3272

        I-D Tag:    draft-ietf-teas-rfc3272bis-27.txt

        URL:        https://www.rfc-editor.org/info/rfc9522

        DOI:        10.17487/RFC9522

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.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC