[Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-20.txt

Adrian Farrel <adrian@olddog.co.uk> Mon, 11 July 2022 08:14 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 937CEC14CF06; Mon, 11 Jul 2022 01:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id J2EHlxn2kHFB; Mon, 11 Jul 2022 01:14:15 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 832C9C14F73B; Mon, 11 Jul 2022 01:14:14 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com []) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 26B8ECbN018740; Mon, 11 Jul 2022 09:14:12 +0100
Received: from vs4.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id E043346083; Mon, 11 Jul 2022 09:14:11 +0100 (BST)
Received: from vs4.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id D4B4546082; Mon, 11 Jul 2022 09:14:11 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown []) by vs4.iomartmail.com (Postfix) with ESMTPS; Mon, 11 Jul 2022 09:14:11 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 26B8E9Ut025933 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 11 Jul 2022 09:14:11 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'TEAS WG' <teas@ietf.org>
Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org>
References: <165752705005.4984.16696626073342124482@ietfa.amsl.com>
In-Reply-To: <165752705005.4984.16696626073342124482@ietfa.amsl.com>
Date: Mon, 11 Jul 2022 09:14:10 +0100
Organization: Old Dog Consulting
Message-ID: <01e201d894fe$3406bb10$9c143130$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQEbSkB7YATx8q/bC0VvyfNLP9ULZK7zZ4bA
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--19.065-10.0-31-10
X-imss-scan-details: No--19.065-10.0-31-10
X-TMASE-Result: 10--19.064600-10.000000
X-TMASE-MatchedRID: wLipip0ZYSC0upcqUpSkATjNGpWCIvfTMVx/3ZYby7974JkRCQAITmqC 9lWWJTGcsNesK1qmuQCB1pn4Wt7RgZ76e9GOpfQKn6y0mNkW0aR1TaBc8Zmm5zGQt2RbsLmq5mR eq9wtVQ2dUZ2b+Iq+B3VyBEksQF0cr8SWmHOl/UstMfCdg6KRDRxCcOlDoVfT1saJu9VAQy0uDh oR+qZH11tAJx/CsgVkIc8bjtTNvcg1BRoXCmaSMLU+IyHhkXf1T5ysQDj6eFmAI7Mvq/sL5+EmR OSC5Th4a7j80yrsQslJ9iwir5XT1R3KilrpmSwS6qr9Nf6IzxN9LQinZ4QefL6qvLNjDYTwzz3j ehzenezN6NCcJaSBTwtuKBGekqUpIG4YlbCDECtruV6hT84yE/IxdJB3PGL0
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/BlisGpy5ui_GkmdpiffAFsur20k>
Subject: [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-20.txt
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: Mon, 11 Jul 2022 08:14:17 -0000


I made the update as discussed to remove the Appendix material. Did this in
a bit of a hurry to get it done before the cut-off later today.

Chairs, I believe that this completes work on the issues raised during
working group last call.


-----Original Message-----
From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
Sent: 11 July 2022 09:11
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: I-D Action: draft-ietf-teas-rfc3272bis-20.txt

A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Traffic Engineering Architecture and
Signaling WG of the IETF.

        Title           : Overview and Principles of Internet Traffic
        Author          : Adrian Farrel
  Filename        : draft-ietf-teas-rfc3272bis-20.txt
  Pages           : 88
  Date            : 2022-07-11

   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.

The IETF datatracker status page for this draft is:

There is also an htmlized version available at:

A diff from the previous version is available at:

Internet-Drafts are also available by rsync at

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt