Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt Tue, 18 May 2021 13:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ACE233A12D0; Tue, 18 May 2021 06:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.095
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SxLekuZAImLz; Tue, 18 May 2021 06:50:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DFA9D3A12CD; Tue, 18 May 2021 06:50:37 -0700 (PDT)
Received: from (unknown [xx.xx.xx.8]) by (ESMTP service) with ESMTP id 4Fky7c0RqQz2xdL; Tue, 18 May 2021 15:50:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1621345836; bh=JkaecHEsTbmj4tHbI2S8CUfl9v5/JMzmDs0zFuUzbpw=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=N4ycDtrSnexu12oZ7zNh9/+S8BsFz+9YveZy/cdiJDokoSZFlZPtMSU0hoSdK5NzL 4m34+XKlKiHqkPBhDD5XT2GW/efLkN2JYhTknVbixG6tM32uBR1gsyCtXBbeip0cxT MMwTlMzD7gj6qj+CtrrT2JN6os6wpia65dLAxMGiqVXqMIkQgu2OJ//nCFXOVK8Fci Vazw/vRp68fieTWsWfmp9NIlRjisHI2d3svCFs2jKPtlvI/E89P5mjk+Vhi8TK/sYr jQOZemsx23HGJZ7XPlyAtTMFyD7h2dBnsUcpGZDWwDtK+DRZP732ddUH21ZGRnm7VG vZ99CNxqJ/fgA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.23]) by (ESMTP service) with ESMTP id 4Fky7b6b9Mz3wbY; Tue, 18 May 2021 15:50:35 +0200 (CEST)
To: "" <>, "" <>
CC: 'TEAS WG Chairs' <>
Thread-Topic: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
Thread-Index: AQHipGASW6xaEWNZaLDTKoBY1XfHxQIm5M9WAtxBG/eqpfae8IADB6jQgAF0b8A=
Date: Tue, 18 May 2021 13:50:35 +0000
Message-ID: <27978_1621345835_60A3C62B_27978_23_1_787AE7BB302AE849A7480A190F8B93303538A533@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <> <06a201d72be3$8e1e9b20$aa5bd160$> <2544_1620053359_60900D6F_2544_75_1_787AE7BB302AE849A7480A190F8B933035375DEC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <0c1301d749ad$58191e50$084b5af0$> <16193_1621266438_60A29006_16193_263_1_787AE7BB302AE849A7480A190F8B933035389D57@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <16193_1621266438_60A29006_16193_263_1_787AE7BB302AE849A7480A190F8B933035389D57@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Teas] I-D Action: draft-ietf-teas-rfc3272bis-11.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 18 May 2021 13:50:43 -0000

Hi Adrian, all,

> I will send in a separate message a text proposal for the "Transport-
> based TE (was QUIC)" Section.
> NEW:
>    5.  Review of TE-Related Techniques
>                    ^^^^^^^^
>      5.1.  Overview of IETF Projects Related to Traffic Engineering
>        5.1.1.  TE Mechanisms
>   Transport-based TE (was QUIC) . . . . . . . . . 

As promised, please find below a proposal fwiw:

X.  Transport-based TE (was QUIC)

   In addition to IP-based TE mechanisms, transport-based TE approaches
   can be considered in specific deployment contexts (e.g., data
   centers, multi-homing).  For example, the 3GPP defines the
   Access Traffic Steering, Switching, and Splitting (ATSSS) service
   that is applicable between multiple access networks.  The ATSSS
   functions are described below:

   Access Traffic Steering:  is the selection of an access network for a
      new flow and the transfer of the traffic of that flow over the
      selected access network.

   Access Traffic Switching:  is the migration of all packets of an
      ongoing flow from one access network to another access network.
      Only one access network is in use at a time.

   Access Traffic Splitting:  is about forwarding the packets of a flow
      across multiple access networks simultaneously.

   Hosts and specific network devices are provided by means of the
   control plane with a set or policies that specify which flows are
   eligible to the ATSSS service.  The traffic that matches an ATSSS
   policy can be distributed among the available access networks
   following one of these modes:

   Active-Standby:   The traffic is forwarded via a specific access
      (called 'active access') and switched to another access (called
      'standby access') when the active access is unavailable.

   Priority-based:   Network accesses are assigned priority levels that
      indicate which network access to be used first.  The traffic
      associated with the matching flow will be steered on the network
      access with a high priority till congestion is detected, then the
      overflow will be forwarded over a low priority access.

   Load-Balancing:   The traffic is distributed among the available
      access networks following a distribution ratio (e.g., 75% via a
      first network access, 25% via a second network access).

   Smallest Delay:   The traffic is forwarded via the access that
      presents the smallest round-trip-time (RTT).

   For resource management purposes, hosts and involved network devices
   support means such as congestion control, RTT measurement, and packet

   For TCP traffic, Multipath TCP [RFC8684] and the 0-RTT
   Convert Protocol [RFC8803] are used to provide the ATSSS service.

   Note that for QUIC [I-D.ietf-quic-transport], it is possible to
   support the switching and steering functions, but splitting is not
   yet supported.  Indeed, QUIC supports a connection migration
   procedure which allows peers to change their transport coordinates
   (IP addresses, port numbers) without breaking the underlying QUIC

   The reader may refer to Section 2.5 of [I-D.irtf-panrg-questions] for
   some research investigation areas.



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.