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

mohamed.boucadair@orange.com Tue, 18 May 2021 15:00 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 976353A160D for <teas@ietfa.amsl.com>; Tue, 18 May 2021 08:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=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 RE_WaNoiBsDS for <teas@ietfa.amsl.com>; Tue, 18 May 2021 08:00:36 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 6732D3A1608 for <teas@ietf.org>; Tue, 18 May 2021 08:00:36 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 4FkzhL3Zbfz21VL; Tue, 18 May 2021 17:00:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1621350034; bh=lJCXOcA87AaTrny6N+N9I+rFuFzaTGIvGaWAxozSrUI=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=M1xyKy7oVWufqu/6j0hEIIgDGqor7da3iC82Z90LWw2JOlEZDhJt6z8ZfOtDD5Ol8 yW1QHzoWwC+UnLoxXNIpHTVB0f+rJyTE426is9yuigYq7VBlkLJQRHY0NCznSkMgqy npQuDwmAUvUt+XnPeipaXoVvIoxd/BBZ5ldj+YK56zWZqBDg+YtlpYF2+960aC2lm7 HzywBpvEp21Xec5JCRtVR2+VaTtWWvyq4Wc83UFTkP2pGPZ9WeedShyS0tiHqPYNyQ ryM6q4XdyX6xeDlIPcNLF5UubmTfKT6R3dHCT9gOIX85wcMUIDi5zPNR9htQipZO6J lzvmQr7XFgwXA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.67]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 4FkzhL2f87z8sZ3; Tue, 18 May 2021 17:00:34 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
CC: "teas@ietf.org" <teas@ietf.org>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
Thread-Index: AQHipGASW6xaEWNZaLDTKoBY1XfHxQIm5M9WAtxBG/eqpfae8IAAAkeAgASKaMA=
Date: Tue, 18 May 2021 15:00:33 +0000
Message-ID: <14245_1621350034_60A3D692_14245_28_4_787AE7BB302AE849A7480A190F8B93303538A62A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <161781991426.15865.4191431758501856588@ietfa.amsl.com> <06a201d72be3$8e1e9b20$aa5bd160$@olddog.co.uk> <2544_1620053359_60900D6F_2544_75_1_787AE7BB302AE849A7480A190F8B933035375DEC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <0c1401d749b1$4ea76030$ebf62090$@olddog.co.uk>
In-Reply-To: <0c1401d749b1$4ea76030$ebf62090$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
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/id3LJRuYZc6UYuYht0hcbeI1hsQ>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.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: Tue, 18 May 2021 15:00:42 -0000

Hi Adrian, 

Thank you for the replies. Here is some few follow-up points:

* s/within the control plane or by controllers/within the control or management plane

* "I'm not clear about the term "resource-based access control". Do you mean "policing"? If so, yes. Policing is mentioned just two sentences later"

I actually meant resource-based admission control. This is now covered by the new section you added. Thanks. 

* " The word "economically" is, I think, giving you a different meaning to what is intended. I think the word is not intended to just mean "financially economical", but also to mean "not wasteful or profligate." This is similar to "efficient", but not the same. In this context, "economically" would certainly apply to power use, money, and any other resource.
I spent a little time trying to think of an equivalent word (because if it is causing you unrest, it will do the same for other readers), but I was unable to think of one.": 

The concern I had is that the observed behavior is conditioned by the metrics/attributes/information that can be disseminated and acted upon. Optimizing the forwarding with a set of metrics as inputs does not guarantee that the overall forwarding is economically-optimized. That's why I provided the example of power-consumption. Such optimization is not currently supported at the level of a network (despite that some optimization can be made at the node/card level).

Cheers,
Med

> -----Message d'origine-----
> De : Adrian Farrel [mailto:adrian@olddog.co.uk]
> Envoyé : samedi 15 mai 2021 19:40
> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
> Objet : RE: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
> 
> Here's the file.
> 
> Many thanks for looking at this.
> 
> Adrian
> 
> -----Original Message-----
> From: Adrian Farrel <adrian@olddog.co.uk>
> Sent: 15 May 2021 18:11
> To: 'mohamed.boucadair@orange.com' <mohamed.boucadair@orange.com>om>;
> 'teas@ietf.org' <teas@ietf.org>
> Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org>
> Subject: RE: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
> 
> Hi Med,
> 
> Thanks for all of your comments.
> 
> Nearly everything is accepted and included.
> 
> Not sure the best way to respond to your Word file, so I embedded my
> responses and I'll send it to you under separate cover (no need to
> spam the mailing list).
> 
> There'll be a -12 along soon to capture your improvements.
> 
> Best,
> Adrian
> 
> -----Original Message-----
> From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> Sent: 03 May 2021 15:49
> To: adrian@olddog.co.uk; teas@ietf.org
> Cc: 'TEAS WG Chairs' <teas-chairs@ietf.org>
> Subject: RE: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
> 
> Hi Adrian, all,
> 
> FWIW, you may find some comments at:
> * pdf:
> https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-
> ietf-teas
> -rfc3272bis-11-rev%20Med.pdf
> * doc:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-
> ietf-teas-
> rfc3272bis-11-rev%20Med.docx
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Teas [mailto:teas-bounces@ietf.org] De la part de Adrian
> Farrel
> > Envoyé : mercredi 7 avril 2021 21:24 À : teas@ietf.org Cc : 'TEAS
> WG
> > Chairs' <teas-chairs@ietf.org> Objet : Re: [Teas] I-D Action:
> > draft-ietf-teas-rfc3272bis-11.txt
> >
> > With this version I have filled in the remaining TBDs:
> > - small section on intent-based network
> > - small section on multi-layer TE (thanks, Lou, for the suggestion)
> > - change log from 3272
> >
> > As far as I'm concerned this document is complete modulo review
> > comments.
> >
> > It *really* needs review, but I can't force you!
> > Maybe you can look at the sections of special interest to you?
> > Maybe the original Design Team could take another look?
> >
> > Otherwise: time for WG last call?
> >
> > Thanks,
> > Adrian
> >
> > -----Original Message-----
> > From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
> > internet-drafts@ietf.org
> > Sent: 07 April 2021 19:25
> > To: i-d-announce@ietf.org
> > Cc: teas@ietf.org
> > Subject: I-D Action: draft-ietf-teas-rfc3272bis-11.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-11.txt
> > 	Pages           : 91
> > 	Date            : 2021-04-07
> >
> > 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 are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-teas-rfc3272bis-11
> > https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-11
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rfc3272bis-11
> >
> >
> > 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:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> > _______________________________________________
> > 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.

_________________________________________________________________________________________________________________________

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.