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

mohamed.boucadair@orange.com Mon, 17 May 2021 15:47 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 EC4033A3C43; Mon, 17 May 2021 08:47:26 -0700 (PDT)
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_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 vsntta0B2VLE; Mon, 17 May 2021 08:47:22 -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 B9A023A3C40; Mon, 17 May 2021 08:47:21 -0700 (PDT)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr22.francetelecom.fr (ESMTP service) with ESMTP id 4FkNmk5X1yz10gb; Mon, 17 May 2021 17:47:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1621266438; bh=VZeWmbNnahARMex3QFo0Va4C8GCgw6LRAUeTT9EKM9g=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=Pe+yV5KJWZj/iCLvTNOMgjMyNSq4r2MLDRb1bZbmlxEFj0MoXDPieYoL7V4uJ67K7 rKIkn7bevpuVlrpTvfPC6WOlA32ppe/q3mC4F7nawlTUIWBxLyB+rCpHlrcrjaCKxY QkMhem85YsTwxzWiqvgHN+YFn4kNa41vR5UBUhhzwl5kff3R/bNWb80hpD1D6wpvwO I94hxqqmuYMl7A6il57pU+4gV1JZY9mbsksGrKP2AF7ees/HfsFpt2wxcnQSmJKOfz QE5LKlgU+mKsWVWWmZXFH2hGbiHgZS6hiieLBOAIM0OYL0gPpzJHCYRtSK1xCMAzxR g6W6BkYyfDdVA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.79]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 4FkNmk4WNszFpWV; Mon, 17 May 2021 17:47:18 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "teas@ietf.org" <teas@ietf.org>
CC: 'TEAS WG Chairs' <teas-chairs@ietf.org>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
Thread-Index: AQHipGASW6xaEWNZaLDTKoBY1XfHxQIm5M9WAtxBG/eqpfae8IADB6jQ
Date: Mon, 17 May 2021 15:47:17 +0000
Message-ID: <16193_1621266438_60A29006_16193_263_1_787AE7BB302AE849A7480A190F8B933035389D57@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> <0c1301d749ad$58191e50$084b5af0$@olddog.co.uk>
In-Reply-To: <0c1301d749ad$58191e50$084b5af0$@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.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/Qo7Utr8wkhTof_IT4We4DR-UBkM>
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: Mon, 17 May 2021 15:47:27 -0000

Hi Adrian, 

Thank you for taking care of the comments. I appreciate in particular the new section about resource-based access control.  

As indicated in my review, I would restructure section because the logic for listing these techniques is not clear to me. Please find below a proposal for discussion.

I will send in a separate message a text proposal for the "Transport-based TE (was QUIC)" Section. 

(1)

OLD:
   5.  Review of TE Techniques . . . . . . . . . . . . . . . . . . .  28
     5.1.  Overview of IETF Projects Related to Traffic Engineering   28
       5.1.1.  Constraint-Based Routing  . . . . . . . . . . . . . .  29
       5.1.2.  Integrated Services . . . . . . . . . . . . . . . . .  31
       5.1.3.  RSVP  . . . . . . . . . . . . . . . . . . . . . . . .  31
       5.1.4.  Differentiated Services . . . . . . . . . . . . . . .  32
       5.1.5.  QUIC  . . . . . . . . . . . . . . . . . . . . . . . .  33
       5.1.6.  Multiprotocol Label Switching (MPLS)  . . . . . . . .  34
       5.1.7.  Generalized MPLS (GMPLS)  . . . . . . . . . . . . . .  34
       5.1.8.  IP Performance Metrics  . . . . . . . . . . . . . . .  35
       5.1.9.  Flow Measurement  . . . . . . . . . . . . . . . . . .  35
       5.1.10. Endpoint Congestion Management  . . . . . . . . . . .  36
       5.1.11. TE Extensions to the IGPs . . . . . . . . . . . . . .  36
       5.1.12. Link-State BGP  . . . . . . . . . . . . . . . . . . .  37
       5.1.13. Path Computation Element  . . . . . . . . . . . . . .  37
       5.1.14. Application-Layer Traffic Optimization  . . . . . . .  38
       5.1.15. Segment Routing with MPLS Encapsulation (SR-MPLS) . .  39
       5.1.16. Segment Routing Policy  . . . . . . . . . . . . . . .  40
       5.1.17. Network Virtualization and Abstraction  . . . . . . .  41
       5.1.18. Network Slicing . . . . . . . . . . . . . . . . . . .  41
       5.1.19. Deterministic Networking  . . . . . . . . . . . . . .  42
       5.1.20. Network TE State Definition and Presentation  . . . .  43
       5.1.21. System Management and Control Interfaces  . . . . . .  43

NEW:
   5.  Review of TE-Related Techniques
                   ^^^^^^^^ 
     5.1.  Overview of IETF Projects Related to Traffic Engineering
       5.1.1.  TE Mechanisms
           5.1.1.1. Integrated Services . . . . . . . . . . . . . . . .
           5.1.1.2. Differentiated Services with TE Extensions . . . . 
                    (was Differentiated Services)
           5.1.1.3. Segment Routing Policy  . . . . . . . . . . . . . .
           5.1.1.4. Transport-based TE (was QUIC) . . . . . . . . . . .
           5.1.1.5. Deterministic Networking  . . . . . . . . . . . . .

       5.1.2.  Approaches Relying on TE Mechanisms
           5.1.2.1. Application-Layer Traffic Optimization  . . . . . .
           5.1.2.2. Network Virtualization and Abstraction  . . . . . .
           5.1.2.3. Network Slicing . . . . . . . . . . . . . . . . . .

       5.1.3.  Techniques Used by TE Mechanisms
           5.1.3.1.  Constraint-Based Routing  . . . . . . . . . . . . 
           5.1.3.2.  RSVP  . . . . . . . . . . . . . . . . . . . . . . 
           5.1.3.3.  Multiprotocol Label Switching (MPLS)  . . . . . . 
           5.1.3.4.  Generalized MPLS (GMPLS)  . . . . . . . . . . . . 
           5.1.3.5.  IP Performance Metrics  . . . . . . . . . . . . . 
           5.1.3.6.  Flow Measurement  . . . . . . . . . . . . . . . . .
           5.1.3.7.  Endpoint Congestion Management  . . . . . . . . . .
           5.1.3.8.  TE Extensions to the IGPs . . . . . . . . . . . . .
           5.1.3.9.  Link-State BGP  . . . . . . . . . . . . . . . . . .
           5.1.3.10. Path Computation Element  . . . . . . . . . . . . .
           5.1.3.11. Segment Routing with MPLS Encapsulation (SR-MPLS) .
           5.1.3.12. Network TE State Definition and Presentation  . . .
           5.1.3.13. System Management and Control Interfaces  . . . . .

(2)

OLD:
   This section briefly reviews different traffic engineering approaches
   proposed and implemented in telecommunications and computer networks
   using IETF protocols and architectures.  The discussion is not
   intended to be comprehensive.  It is primarily intended to illuminate
   existing approaches to traffic engineering in the Internet.  A
   historic overview of traffic engineering in telecommunications
   networks is provided in Appendix A, while Appendix B describes
   approaches in other standards bodies.

NEW:
   This section briefly reviews different TE-related approaches proposed
   and implemented in telecommunications and computer networks using
   IETF protocols and architectures.  These approaches are organized
   into three categories: TE mechanisms which adhere to the definition
   provided in Section 1.2, approaches that rely upon TE mechanisms, and
   techniques that are used by TE mechanisms.

   The discussion is not intended to be comprehensive.  It is primarily
   intended to illuminate existing approaches to traffic engineering in
   the Internet.  A historic overview of traffic engineering in
   telecommunications networks is provided in Appendix A, while
   Appendix B describes approaches in other standards bodies.

(3)

Add a table to indicate whether mechanisms that are tagged as "TE are "partial TE" or "full TE" as per the discussion in 1.2. This can be captured by indicating which properties are supported by each of them. A table (to be completed) is provided below, fwiw: 

                   +---------------+---------------+---------------+
                   | Policy        | Path Steering | Resource      |
                   |               |               | Management    |
       +-----------+---------------+---------------+---------------+
       | IntServ   | TBC           | TBC           | TBC           |
       | DS-TE     | TBC           | TBC           | TBC           |
       | SR Policy | TBC           | TBC           | TBC           |
       | DetNet    | TBC           | TBC           | TBC           |
       +-----------+---------------+---------------+---------------+

Cheers,
Med

> -----Message d'origine-----
> De : Adrian Farrel [mailto:adrian@olddog.co.uk]
> Envoyé : samedi 15 mai 2021 19:11
> À : BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>om>;
> teas@ietf.org
> Cc : 'TEAS WG Chairs' <teas-chairs@ietf.org>
> Objet : 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


_________________________________________________________________________________________________________________________

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.