Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-14.txt

mohamed.boucadair@orange.com Thu, 24 February 2022 06:36 UTC

Return-Path: <mohamed.boucadair@orange.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 9CABD3A1497 for <teas@ietfa.amsl.com>; Wed, 23 Feb 2022 22:36:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gscfAJZ55P9d for <teas@ietfa.amsl.com>; Wed, 23 Feb 2022 22:36:15 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3C63A1496 for <teas@ietf.org>; Wed, 23 Feb 2022 22:36:14 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar21.francetelecom.fr (ESMTP service) with ESMTPS id 4K438F1GLKz7tst; Thu, 24 Feb 2022 07:36:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1645684573; bh=wdSUdVXwxcopdLzbQEw2/Q9DmLu2bKkKhWQvU3S2Otc=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=QWnN3mmkna6qC+ONpGxkZYaibDTRDxsMIg6meBbuI8u3ZgH3xI0t6A5zzPQ7COoCI 93+H2CYBG/0OMbugtlOSQajkFJDdx8JufWGj0o88ncqb0CcLYVtZMbRnon7dzcVk9T iph5T0MdFsRfVpRGz8/WsgkT9Wx1moiGCVgvA7vMwhy4Q1msqCLus/3WehP7HMmZOx mBRwS57z2cCLAkM4YcSjT2n1BzNusJfkSm2nf6U9WM7RXjVHlSZfa8aS7fYOqxk40x DVWQjXLAfAEWGRvQnCu8phz4dLazNg4WM6E3TKHBZC7Jhj5x7RjAl/Jp+K/10y35ps uJohTqXfo/tVQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar06.francetelecom.fr (ESMTP service) with ESMTPS id 4K438F0TyFz3wbH; Thu, 24 Feb 2022 07:36:13 +0100 (CET)
From: mohamed.boucadair@orange.com
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-14.txt
Thread-Index: AQHYKPP1lIWJKopGeEmK6GXUG2GSLqyhhigAgAC3C7A=
Content-Class:
Date: Thu, 24 Feb 2022 06:36:12 +0000
Message-ID: <17088_1645684573_6217275D_17088_290_1_787AE7BB302AE849A7480A190F8B933035498E88@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164564808383.28603.7186062312487278298@ietfa.amsl.com> <015701d828f4$6b7c9e50$4275daf0$@olddog.co.uk>
In-Reply-To: <015701d828f4$6b7c9e50$4275daf0$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-02-24T06:27:16Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=4b7dee68-fe5f-4b39-9df2-1dd814e149aa; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/TUDQRkZLb83G7sJKi-g4cE7GlkI>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-14.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: Thu, 24 Feb 2022 06:36:21 -0000

Hi Adrian, all, 

Many thanks for the effort put into this document.

I like the revised version but I will like it even more if it addresses this pending comment :-)

https://mailarchive.ietf.org/arch/msg/teas/TcPmT0mbB0JUJoR9gnTSXUj3SIs/.   

Cheers,
Med

> -----Message d'origine-----
> De : Teas <teas-bounces@ietf.org> De la part de Adrian Farrel
> Envoyé : mercredi 23 février 2022 21:32
> À : teas@ietf.org
> Objet : Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-14.txt
> 
> I know you've not been able to sleep for the last four months, waiting
> (as you have been) with barely contained enthusiasm for the next
> revision of this draft.
> 
> Thanks for this revision go to Med and Gyan. They both submitted
> substantial comments. I addressed most of Med's comments in -13, but
> this revision completes on the points Med raised and handles yan's
> review modulo the email I just sent.
> 
> Best,
> Adrian
> 
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
> Sent: 23 February 2022 20:28
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-14.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Traffic Engineering Architecture and
> Signaling WG of the IETF.
> 
>         Title           : Overview and Principles of Internet Traffic
> Engineering
>         Author          : Adrian Farrel
> 	Filename        : draft-ietf-teas-rfc3272bis-14.txt
> 	Pages           : 93
> 	Date            : 2022-02-23
> 
> Abstract:
>    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:
> https://datatracker.ietf.org/doc/draft-ietf-teas-rfc3272bis/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-14
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rfc3272bis-14
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-
> drafts
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.