Re: [Pce] new draft on segment routing approach to TSN

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 25 February 2021 17:41 UTC

Return-Path: <pthubert@cisco.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 625883A1D72; Thu, 25 Feb 2021 09:41:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.596
X-Spam-Level:
X-Spam-Status: No, score=-9.596 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, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=kCIO199/; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kBZtwA9a
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 EovuqUdtr0Os; Thu, 25 Feb 2021 09:41:09 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F7793A1F82; Thu, 25 Feb 2021 09:40:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23648; q=dns/txt; s=iport; t=1614274838; x=1615484438; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=BsrU0jx3EpJoEGmLQfMIfBdCsE5WxwA7LHHpj9OxPAo=; b=kCIO199/hzQ4odi+rdhmyoMuzkRR15VqTKa3YvkGECSvMUHyIgJ9LHZ/ JRf2H6wt9mMftFObEjab9UJk2KJmAt8Eb8IqeCbJ1MlfMnMZ0yNbZ1tPt 7GWt9KkVkCRwLm/SAzZp8UWdaSEKUTuMX1sdQsK0DrfcrrRsEuHOHIHBi Y=;
X-IPAS-Result: =?us-ascii?q?A0DUAgDx3zdgkJ1dJa1iHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?U+BIzApKH1aNjGICQOFOYhhA5kgglMDVAsBAQENAQEqCAIEAQGETQKBeAIlO?= =?us-ascii?q?BMCAwEBAQMCAwEBAQEFAQEBAgEGBBQBAQEBAQGGOA2GRAEBAQEDLRMBATgPA?= =?us-ascii?q?gEIEQEDAQEhBwcyFAMGCAEBBAESCIJoAYF+VwMvAQ6lVwKKJXSBNIMEAQEGg?= =?us-ascii?q?TMBAwKDVRiCEgMGgTiCdoQGglSDcyYcgUFCgVSCVz6CXQEBA4FFGisJgxSCK?= =?us-ascii?q?4F+RgInRUMOAldtGjQgQos+j16BS5xSCoJ8iT+MO4ZFkliQdZROizySB4RXA?= =?us-ascii?q?gICAgQFAg4BAQaBayE5gSBwFYMkUBcCDVaIG4UuGYEKAQgCgkGFFIUJATtzA?= =?us-ascii?q?jYCBgEJAQEDCXyKOV4BAQ?=
IronPort-PHdr: =?us-ascii?q?9a23=3Ab4s6MR+Z1Cf3wv9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+7ZRKN5ehkk1LIG47c7qEMh+nXtvXmXmoNqdaEvWsZeZNBHx?= =?us-ascii?q?kClY0NngMmDcLEbC+zLPPjYyEgWsgXUlhj8iK7LEFKFce4bFrX8TW+6DcIEU?= =?us-ascii?q?D5Mgx4bu3+Bo/ViZGx0Oa/s53eaglFnnyze7R3eR63tg7W8MIRhNhv?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.81,206,1610409600"; d="scan'208,217";a="670288920"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 25 Feb 2021 17:40:36 +0000
Received: from mail.cisco.com (xbe-rcd-005.cisco.com [173.37.102.20]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 11PHea2k010113 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=OK); Thu, 25 Feb 2021 17:40:36 GMT
Received: from xfe-rcd-004.cisco.com (173.37.227.252) by xbe-rcd-005.cisco.com (173.37.102.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.792.3; Thu, 25 Feb 2021 11:40:36 -0600
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xfe-rcd-004.cisco.com (173.37.227.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.792.3; Thu, 25 Feb 2021 11:40:35 -0600
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 25 Feb 2021 12:40:35 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZraxIfhNcYJ6zzdUOF4PN0Uvs0P98a2mYuo+1Bt8CSOLCohr/XCLnqW61ws5Vnxgjxl0yqANXJUeOu+I1WtMohTbRQp9dZgG6kQPOGUV8yaVacxm8aBwxyASPC77ZxWTEOji2qvtfuINXDGwS0q6LepNFOgEhIx30lwqQ9f2Ke7yC/okX3mBvfXY2p5qXvr0JviFIiUXYM3hGdiRWmAwJQ+Mhsfrij0IUy7/xHVXJxkqAdLFwejmNcZ4RzD4R4BEQOUb5qV1STwNWXdjS7ZJq/yW7AHfUfe1evgh6D2fyBdw8ubC5DbkSLS++Qsy6yP2Lu4PzhUmfPOhEhHraWVQ2A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7XJoWt09Z9GiPGNML/q36ArATyzoLCW2jUH9O5qYFPQ=; b=UnIlTsnTgrM1MYbKFCyg1zqJXAcDJZX3Y3K4+5nm58WSZkbr7oGNuoreweQu2AOkJ8dk7w/sOzTSmXpJy7477QeI/MALvw8IJfB6EBRVQhNmSlQ4J+NYKPQcsrWnrjiY50hbzGUEhPTYJUzvyOxw2uDtrg1/wyjWZ+YxhvGpPIdiUz49VUjHhjeq5TAFx153TVuM+llhsCLHZcjgFlyRIwa7bAoOwM4RMxHIb/yqlwzV12yUx5+YiwunvohMkaURfF4jfD0iY0AVNAySmo1f2SSaaMnt9glJMMwPh/Ym30QCv0JnvzJZTbq+Ax/lk8bXIJpn8E4NHrYhgGost2AP0Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7XJoWt09Z9GiPGNML/q36ArATyzoLCW2jUH9O5qYFPQ=; b=kBZtwA9alH6yJRo+DSFRhdo0rZDC0N9cOzfnBncJ9LoOBPFWY0RN8/d01Lf02laeU7zvrL2gkPeKk6mEUbUA9Vaqevg5gmBwtgTYDkQu5S2K+oRB06a2BCvgC1b21/oiTuulDenHjaBcEjeYbeCSp3wEBf9Tg9nghyXg2xyUonQ=
Received: from CO1PR11MB4881.namprd11.prod.outlook.com (2603:10b6:303:91::20) by MWHPR11MB1888.namprd11.prod.outlook.com (2603:10b6:300:10e::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3890.20; Thu, 25 Feb 2021 17:40:34 +0000
Received: from CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::14a1:29eb:e708:d7e6]) by CO1PR11MB4881.namprd11.prod.outlook.com ([fe80::14a1:29eb:e708:d7e6%7]) with mapi id 15.20.3868.034; Thu, 25 Feb 2021 17:40:34 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Tianran Zhou <zhoutianran@huawei.com>, Yaakov Stein <yaakov_s@rad.com>, "detnet@ietf.org" <detnet@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: new draft on segment routing approach to TSN
Thread-Index: AdcJ5AjgmuXpLt94R1Stsoh/vUDwUABaAaLAAAtVwoA=
Date: Thu, 25 Feb 2021 17:40:29 +0000
Deferred-Delivery: Thu, 25 Feb 2021 17:40:24 +0000
Message-ID: <CO1PR11MB488181838180DBE6F5DB3B5BD89E9@CO1PR11MB4881.namprd11.prod.outlook.com>
References: <AM0PR03MB35228092287B38B95D7056F7E5809@AM0PR03MB3522.eurprd03.prod.outlook.com> <3c69571d0bcb4a6ea1d08bee53c0277d@huawei.com>
In-Reply-To: <3c69571d0bcb4a6ea1d08bee53c0277d@huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb15:262:d900:6885:887b:4ad1:1f3]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: babf0b14-a778-449a-75fc-08d8d9b4744f
x-ms-traffictypediagnostic: MWHPR11MB1888:
x-microsoft-antispam-prvs: <MWHPR11MB1888F8E3B6057A210A2F9ADBD89E9@MWHPR11MB1888.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: K2W0KMv08HPWSdQm6sj4bkjZ8w7bvBEIrJJng+uWrRRgBo3XZO+OUmmOoJ+KHEq+qdnpHr/CNwA7HsS+X5muraHRGcQS91Y3X8b+vUSxNKNIfylGkiDO8w1HgCvWfSzMbbozrcii15PeJa4fBaZlts+Osyd4c3IHBMCrMO4OSUph+sC1PhM+0l6GIrHB8+kY8uPFJk9Ih2x4gaKYC8FtTYCsxFJIGAHoESi8q8znXudXJ2lN3mcg4jIT5Gi8fNo7Gnk/WgNB/jVJ82szkHf2lmjT4nFycoeucTAILrhA/bzFjphZuuF5CX9dgYM2l0XQVvvjZYgrWS+ogbhwQstOYn9H8Ug+UrpP9mdxF7uFKEeKtex5G1jcCzVg3Jn2T61+MVpMcJHjzXuksqYAE8PXXWqP/Ko8fo8gD2bsFLlUzn0zch6rsuZ7L597FiVetiXkgPGFwNC0FaHjzKRhSNdMvj9dannRjvOeHMngY/6GVoeDZHndzneB4q8xPYNgeXafgARagnnOvs7K7ZlVaN56cRWpgOZlPK+22acId46x4QhIxPgO6n6l7dv+5ZLU526JKqGerKGB+Uqx7oHV4Xf+KTxK9zeRbNPTHPTy/G1dp5o=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CO1PR11MB4881.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(39860400002)(366004)(346002)(136003)(396003)(376002)(33656002)(166002)(478600001)(966005)(52536014)(9686003)(86362001)(66556008)(5660300002)(55016002)(64756008)(66946007)(66476007)(110136005)(7696005)(66574015)(2906002)(66446008)(6506007)(83380400001)(53546011)(8676002)(8936002)(186003)(71200400001)(6666004)(76116006)(316002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: =?iso-8859-1?Q?oO8dRXdWKOy8gFKudaSrdllGslPo4ug4pUh+1rgM9V45VTrlxD9M9+Iadk?= =?iso-8859-1?Q?9pdvCdFbpDPLebdpnUHpERaZGtj+HycMvxn0M10xmAK+0tKemq8mFGf3a4?= =?iso-8859-1?Q?4x/3iFub+x63qFmE0ugd8qTvTkgD3GbiylC9e8WDccZ3/SqqOz/b8dh4HL?= =?iso-8859-1?Q?fsyxNH4048dy0UZEsROdTHoFDUsC27DINrvqAC6dVzRZ5M25bqUYa5i/Cw?= =?iso-8859-1?Q?FVyXuMJ4Mrip61CCLT6/G1+NzUMc3zvdaXt0UDhjBrvybO00SDyPUPlQLb?= =?iso-8859-1?Q?4UQAMJ13JDGXoFsEk+3zWqqzbh7yAxf86Gz0o8u6Ty4r0IpINGnusRX6OW?= =?iso-8859-1?Q?8fshAhErGHbPA4dKH02SfQNhjyVIZtxCIG/76gRGPWRBZlc9cV8mQGkqWL?= =?iso-8859-1?Q?LuNh5dE+Jqmr8JbNmLcxPI08KK3BQxkt8PKvWax4JXH8xWWzEDeDH29JDU?= =?iso-8859-1?Q?i5rI/WDVOQE3b5UUHPZp7LiBdMBH7O+10rmomNSepgjWfqAgoPD/WFL0M7?= =?iso-8859-1?Q?E7dlpHd+xoeD5gSUCAc8g6kS5N1XzNp2kSUkfwd5F6v8fd/vEgARfZCzER?= =?iso-8859-1?Q?C35Jqe+fryTIRrJ+vUksiBXqto5hWbNg22fbCjOEaNii+89WEcSzmmmhre?= =?iso-8859-1?Q?61rwPZ3m7cAqendiQVTEPU3ANMNLl9pSq3MWXPuZNCRVTmVoTY/jqvZG//?= =?iso-8859-1?Q?GC/uSZEabDri7JSh4OTp2bcOjfVxhJheTWmTcbCXWr8XYg1P1Bc6YY0e1B?= =?iso-8859-1?Q?ruPKFruxzXVl2uP4wVDXZTq5xshB/XrkI9yB63JpEHWhPkQ2p/6fLEGaKC?= =?iso-8859-1?Q?0be+lTMrY9sk8D/XtPVgSPGhl+y0g7zCnf8Jl8gJZE2qJ/BN1TF30cNG5J?= =?iso-8859-1?Q?CdMr4Q54Y3w0udURvNyMMrCyvZCS0Am0wG3E3DqUjxo8qSnNYVVUwEthN4?= =?iso-8859-1?Q?s+MwdDySZS/2EO2UdYgOQAQI0GlLW5j9c0qOfkifrVc9O96T3Bpp+XhaX9?= =?iso-8859-1?Q?7BuelsH5u9PnrdUTqvqjibK/eSEdDxWOsmy1bKbTcugUEebWu9/EHhny+v?= =?iso-8859-1?Q?wuoV1GAjAvfc3NnAwF//5uvvIRlwncDisZ+tupv3sd57pfyRgM5m2aZNZn?= =?iso-8859-1?Q?QlTeFhOGJUH1Aw8dckMu7EjaTSdiYwiZITbd0T5yTEmC2lzA1cIPpr0+Js?= =?iso-8859-1?Q?rT/qSpLJrzlLMpN9ji0l4Tk9xpQqgQFgUwvhHQi1sCVV2qjDXlSD1pR2HP?= =?iso-8859-1?Q?iQdXBqkYi2175TbRYRYebhzbw/qi5nISpCUAYVou5pkjAkLCjNR/BP0UvR?= =?iso-8859-1?Q?Y7+04UpHOMuoCE+iJdM7eMiEwLhcr5WFExHYM3b0z5O/xtk58KqS+d7R09?= =?iso-8859-1?Q?1xeZqK9AcnMqMsIJ07kXR3dNMV5ptgnhjiVNDPMRYAof2rTs1MhgRnqisO?= =?iso-8859-1?Q?kZP75rh95RGoZ+rr?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CO1PR11MB488181838180DBE6F5DB3B5BD89E9CO1PR11MB4881namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CO1PR11MB4881.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: babf0b14-a778-449a-75fc-08d8d9b4744f
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Feb 2021 17:40:34.0296 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YKPTBFcXfO/uhQlkky7F7/lMHpdRA4xZmOOK327ERbHT1qc/dVYIR3Ph2LCuDZ9gj9MdLMoha6I/gmcuinByEA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1888
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.20, xbe-rcd-005.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/U0C39VduSosApXuBL4Dfc8h0qdA>
Subject: Re: [Pce] new draft on segment routing approach to TSN
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2021 17:41:13 -0000

Hi Yaakov and all:

Whereever Yaakov decides to place it I'll be there supporting the work. The draft itself is incredibly well-written and information-rich.
Note that there's also work in RAW that mentions SR operation DetNet related operations (draft-pthubert-raw-architecture<https://tools.ietf.org/html/draft-pthubert-raw-architecture-05>)5>). RAW has vested interest in intelligent forwarding decision, that would be the trademark vs. DetNet. With this draft, the forwarding is not based on Qbv schedule but the forwarder has some latitude as long as it matches the hop deadline. So RAW may be a good place.
And then there's draft-chen-detnet-sr-based-bounded-latency<https://tools.ietf.org/html/draft-chen-detnet-sr-based-bounded-latency-01>01>. Ideally all these related items would progress in the same room.

Also a few notes on the draft itself:
- maybe use latency instead of delay; it would be nice to maybe define delay as something else, e.g., the delay representing the time the packet spends queued in one hop vs. the latency that is end to end?
- not sure the term green wave is well understood by the public here; the draft gives the impression that the TSN path is faster than the best effort and involves no queueing. For the most part that is untrue; the latency is bounded but for most flows it is longer than best effort. Best effort can be really fast with passthrough in an empty network. The problem is the long tail and possibly congestion loss. For TSN, there can be very special flows that will traverse the city with all the lights green, but usually there'll be queuing. The difference is that the queueing latency is constant and the overall latency is withing bounds.
- Time triggered is not the only TSN operation. I wonder what the draft would become with asynchronous shaper in mind. We designed (and as I must announce, patented as US9602420<https://patents.google.com/patent/US9602420>) a system very similar to the one proposed in the draft, but that is designed to adapt QoS depending on whether the packet is early or late vs. its schedule, and not tagging the schedule in the since the latency is considered end to end not hop by hop. The use case is slightly different since we apply this without a global controller and a provable guarantees all flows will meet the deadline - so not really detnet-, but more like a best effort that all flows meet their deadline in a stochastic environment. If Yaakov is interested, we can contribute on that aspect.

Good luck with the draft,

Pascal


From: detnet <detnet-bounces@ietf.org> On Behalf Of Tianran Zhou
Sent: jeudi 25 février 2021 9:14
To: Yaakov Stein <yaakov_s@rad.com>om>; detnet@ietf.org; spring@ietf.org; pce@ietf.org
Subject: Re: [Detnet] new draft on segment routing approach to TSN

Hi Yaakov,

This is an interesting topic.
After a quick review, there are several questions as follows:
1. It's clear to me to have a deadline for each packet. So that router can schedule the packet based on the urgency. But what's the motivation to split the end to end deadline to several local ones?
2. How to divide an end to end deadline into several local deadlines? Is there any example algorithm that could be used by the controller?
3. As far as I know, most devices do not support edf. I am not sure whether your proposal based on edf could really be useful.

Cheers,
Tianran


From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Yaakov Stein
Sent: Tuesday, February 23, 2021 9:14 PM
To: detnet@ietf.org<mailto:detnet@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>; pce@ietf.org<mailto:pce@ietf.org>
Subject: [Pce] new draft on segment routing approach to TSN

All,

I would like to call your attention to a new ID https://www.ietf.org/archive/id/draft-stein-srtsn-00.txt
which describes using a stack-based approach (similar to segment routing) to time sensitive networking.
It furthermore proposes combining segment routing with this approach to TSN
resulting in a unified approach to forwarding and scheduling.

The draft is information at this point, since it discusses the concepts and does not yet pin down the precise formats.

Apologies for simultaneously sending to 3 lists,
but I am not sure which WG is the most appropriate for discussions of this topic.

  *   DetNet is most relevant since the whole point is to control end-to-end latency of a time-sensitive flow.
  *   Spring is also directly relevant due to the use of a stack in the header and the combined approach just mentioned.
  *   PCE is relevant to the case of a central server jointly computing an optimal path and local deadline stack.
I'll let the chairs decide where discussions should be held.

Y(J)S