[Teas] Update to draft-ietf-teas-rfc3272bis-01.txt

Adrian Farrel <adrian@olddog.co.uk> Mon, 13 July 2020 21:11 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 09D3E3A0A2E for <teas@ietfa.amsl.com>; Mon, 13 Jul 2020 14:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ULu2Cg4_WDOW for <teas@ietfa.amsl.com>; Mon, 13 Jul 2020 14:11:22 -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 F23463A0A7B for <teas@ietf.org>; Mon, 13 Jul 2020 14:11:21 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06DLBJ2O014712 for <teas@ietf.org>; Mon, 13 Jul 2020 22:11:19 +0100
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 8DB0922032 for <teas@ietf.org>; Mon, 13 Jul 2020 22:11:17 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS id 790232203C for <teas@ietf.org>; Mon, 13 Jul 2020 22:11:17 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id 06DLBGVH007357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <teas@ietf.org>; Mon, 13 Jul 2020 22:11:16 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <teas@ietf.org>
Date: Mon, 13 Jul 2020 22:11:16 +0100
Organization: Old Dog Consulting
Message-ID: <072901d6595a$25df2cc0$719d8640$@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: AdZZWiMbNBgI5zqFQ7GmSuyNnZPheg==
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--17.051-10.0-31-10
X-imss-scan-details: No--17.051-10.0-31-10
X-TMASE-Result: 10--17.051400-10.000000
X-TMASE-MatchedRID: CDtsO4Gok4dor4mPA3EMtnFPUrVDm6jtu8ZgmQ167rWZfDRE1uqSgj77 Lhrh7xxod371w8KZaYiVkKHib3gfR2Bt4CaODzdDBcaL/tyWL2M5iooXtStiHukcZ2oaQMVmjL4 B9OUMY3Wp5SzUirVGLr+ZRx3n+HfgdKV6sajdfEZcrmR4Jr5uaOkphWnlDPb3FoX0IByf8R4XsK ivASOwuNksSf0frDbxgUcAJaxTivVedqf/1CqXC9MfKJ+BrWfHzN2Fo3fuIAysaBVGMabQl18gk dmvvg/2Lt6Th6XF55wGIKNkvPq+b2MFwILfD7YgnMQdNQ64xfdReWnUUdhI9Z3ls77dbPaIhGzG 3wY/cLeLvjAcuEwRp3Y7esss4Pcst5xC/66F0BHPkG//aAoWCaUYIgxuvuD+g8vHe9ji82LmVyn Qf9JaEO6AnvE45YLak9+sD8O+RkFQb11/ZSgnz/03NoquOQp7ICoL/Rp4fQcdLHANO4bp4Ckx5I VTYi8Vf4oylLsldE5xiTqHtRnBaL9jX++auvv+4h8r8l3l4eb+NefZIdSZXNE4PeXguBzlOUNwl zKe/hzyujcK/844/dJJNS9kbqgP443ELYJ+aVso7b5tLxYZrZLQR37yyvyamyiLZetSf8nJ4y0w P1A6AJy/CPd12p6Jh9eWnlL1x8DdB/CxWTRRu/558CedkGIvIXptJJqT2TE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/ZhIFkw-qH8uWZPKCYdPdMcg9LlE>
Subject: [Teas] Update to draft-ietf-teas-rfc3272bis-01.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Jul 2020 21:11:25 -0000

Hi WG,

This update is just to flush my edit buffer.

Dhruv raised the question as to whether a TE solution MUST include all three
elements described in Section 1.2, viz:
   1.  Policy
   2.  Path steering
   3.  Resource management

I have added this paragraph

   The key elements required in any TE solution are as follows.  Some TE
   solutions rely on these elements to a lesser or greater extent.
   Debate remains about whether a solution can truly be called Traffic
   Engineering that does not include all of these elements.  For the
   sake of this document we assert that all TE solutions must include
   some aspects of all of these elements.  Other solutions can be
   classed as "partial TE" and also fall in scope of this document.

The term "partial TE" feels a bit clunky, and we might use terms more
specific to what they describe. For example, we might look at BIER tree
engineering and Segment Routing policy as mentioned by Dhruv.


-----Original Message-----
From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 13 July 2020 21:49
To: i-d-announce@ietf.org
Cc: teas@ietf.org
Subject: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-01.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-01.txt
	Pages           : 77
	Date            : 2020-07-13

   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 discussed throughout this document.

   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 are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

Teas mailing list