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

Haoyu Song <haoyu.song@futurewei.com> Mon, 08 March 2021 02:41 UTC

Return-Path: <haoyu.song@futurewei.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 DE7453A2240; Sun, 7 Mar 2021 18:41:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 LulpL-3_Z5kd; Sun, 7 Mar 2021 18:41:24 -0800 (PST)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2119.outbound.protection.outlook.com [40.107.223.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F5813A223C; Sun, 7 Mar 2021 18:41:24 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kx5IaaSY15rHvK9BwohbUpXyHf6B55Gnm1NifjjjZsJAaazZQdNTr/HMZtAkl0WR0a+TF29fvJv7QEfnTqXYpAWiBdIiI8eDnk2P/7R1nKciCk+o7cN++AH5S4wXcq+JQEdvJhm4Vf621TCR6CpZ0E0eHl+1ZP9tBz5ak3bRCQx/RgEik7+rrUdCg32OvwuAY9XI5jeKw6HEL+vWeBv8/4IN6ih9b1TlwHz2knuuqxIUq6b14uzind7z78MwfEOtwKDkBWpNb0LEbVVDMd5W7kShxGloQraZSKQCk05JlA1U11gFsPmBbzPaVzVpfGdkWLieVEFdWQFUAEp4B4Zs2w==
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=d1kATNH2nRW0JZgp2YfobLhfWaJtJQT9WSMfZ51gLcc=; b=eV7i2frTNwfLrlgoVpiwsJ0F6h5ZuHv+f3HsT4W0kOnSROyVB0r2zi2p6xT9HFXRRabaRR4dB03Ob3wDU+C+XC8UidjYHdo7mzyS2OYaGqoV3JUTW1githoTYn0lGxOO0Mm1Y9n0o1xlzKS9O/xCQZoR+aK63TDnKXyPxCzMD5ypDVGy6nlXGAFAAAGJFFfdCWv2tmwHvd2dx1yuh6VNgtgCCzvEn5R6e3w/lDnHG2YrKAXGXseMEJqJWmznMNbUpgT4qGkEQ5TVmdAVDMYA+7grR5HU3aDzr7qEMSYdvovgGe93eOe0/aXLycYKb1JSffbh4bJwuIatMib2K4mpBQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d1kATNH2nRW0JZgp2YfobLhfWaJtJQT9WSMfZ51gLcc=; b=W09BI+1AbwRas8zdA/xniAofULaTdoLTqVL+1DD0I7nloFzmh90kB4Pg/6DTyOtUXaT4qkBg/kQdUjC7kSn+SXiIBV0/Ee/CmUGRl+rSOZU5xdsutlcL6cPhtnjUQccqM7aYOATNW7a+1yP5FhpQLDXLWYltyajvw4lINTMzouo=
Received: from DM6PR13MB2762.namprd13.prod.outlook.com (2603:10b6:5:13c::13) by DM6PR13MB3114.namprd13.prod.outlook.com (2603:10b6:5:19e::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3933.14; Mon, 8 Mar 2021 02:41:18 +0000
Received: from DM6PR13MB2762.namprd13.prod.outlook.com ([fe80::cd7c:ab34:e7f7:203e]) by DM6PR13MB2762.namprd13.prod.outlook.com ([fe80::cd7c:ab34:e7f7:203e%6]) with mapi id 15.20.3912.026; Mon, 8 Mar 2021 02:41:18 +0000
From: Haoyu Song <haoyu.song@futurewei.com>
To: 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/vUDwUAIGpPHgAEKRNTAALm7rkA==
Date: Mon, 8 Mar 2021 02:41:17 +0000
Message-ID: <DM6PR13MB27624F07A612BDCF98A8C92F9A939@DM6PR13MB2762.namprd13.prod.outlook.com>
References: <AM0PR03MB35228092287B38B95D7056F7E5809@AM0PR03MB3522.eurprd03.prod.outlook.com> <DM6PR13MB2762033C6ACECC4A816830AC9A969@DM6PR13MB2762.namprd13.prod.outlook.com> <AM0PR03MB3522BD9D4D0A3134FE16B49FE5949@AM0PR03MB3522.eurprd03.prod.outlook.com>
In-Reply-To: <AM0PR03MB3522BD9D4D0A3134FE16B49FE5949@AM0PR03MB3522.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: rad.com; dkim=none (message not signed) header.d=none;rad.com; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2600:1700:38c4:650:a9b5:3b9:2c14:3108]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3a931c89-b948-496b-a420-08d8e1dba682
x-ms-traffictypediagnostic: DM6PR13MB3114:
x-microsoft-antispam-prvs: <DM6PR13MB311473993A442483BB44753D9A939@DM6PR13MB3114.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:4303;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: PiuNp+DmmgVFIAcko6ITjo1oqRmkPHQkmIQyZMz0KMOEvGGlUu1Qcjm/m/RVvwJnqHfPMq07811uNLFesm11914gpfNKPabTw+oT1+Rsulc8Iosf5poQGqkdOe20mF492tdFBpVTMPRu8L7tNTQi0wX9tLf3qVCILIxFU4uHL1DAKfehwu0bdQVyaLYMta/iUAda7ync3t7bRdQqPtBPlvUU5e/o0EErM1egfNQZThY9hMdWpoVTGaCFO64EsT7DB4mMOOJPaoNBCD9QQc0qN3yEb8E036e5VZ68GB1QyZC8tY5YuW/V93q/2voD4BuPiK5v8D+mm/AzgPqoIBwVr8mw2XGMXFTVBKGdHBQQU9BapiZfhPWbX6TMzxN0lJwEXfMku5BIo7hDgvUCOznm8HLXr9MSHkaTDWf4GY2egkJAYYb9AUt4fnGbhjxm0hfqADhU5dXPSq4fIczZURteACgf9U5yJEk7+KuR8VTKir86Qf3UNaxmrNWTgAFY+kF4cdseprWrouHWLVx52AqJghPppVSmVhJzCRkYUcf3EiMJW7hP5xisHz7VD72NlgWok504jcck/WAEoIqYz8xKPXtJIELfypmTfXijzQqLhy6VylOnhfpS1Gkkpdh6/sjerutYPlSJpFDobjz3DadBFQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DM6PR13MB2762.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39830400003)(366004)(346002)(136003)(396003)(376002)(9326002)(186003)(66946007)(66574015)(66446008)(64756008)(66556008)(66476007)(33656002)(2906002)(8936002)(478600001)(53546011)(6506007)(71200400001)(76116006)(83380400001)(7696005)(966005)(166002)(110136005)(9686003)(86362001)(44832011)(52536014)(5660300002)(55016002)(316002)(8676002); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?AGlP/AHC1Q+uRxqO1GC/gSM3ya+NJpmBNsNN4YP2PfP16PDdFPY8Xd7VNa3f?= =?us-ascii?Q?Hd+bR13H5AD+KkVIrtSWfQrc6gHWySzQ+1NAt6/CXTjTsdhOTQPxKiSjj9oj?= =?us-ascii?Q?cZ7CIbiG+Ixt3iK6o3OFiV1jH9ZY1AKdAjkDFNCqN2lQb1pVbVKlnAlIevf8?= =?us-ascii?Q?aGCEquvAbsUYnugH87QBW/axr86Y8+UqqcNwFiNZ0ptmWEC9w/tHS4EOG8is?= =?us-ascii?Q?RqCahqXtGdzCUMaZ0vMKwrkV6Wf7c45WiIGgeD6RIuNJ/92HziSiC0ZXYxOv?= =?us-ascii?Q?/yHo0I34auU1BHQrF+rpKRy0oUg1W1RqpXJvlmWH1n/odiHO1PSfxGP/rJ5u?= =?us-ascii?Q?IHxsOXJJm0kETXsB00/EH4giQBlyd5a2KdJvvMRCWw7z6aRhw2KkCMSOFE4Y?= =?us-ascii?Q?QxM6AN/TLqklDzqK8EYmXiQ+Rcl4P6oppUSYZl2wXpzOFqxPVAlAi0q6i4HE?= =?us-ascii?Q?C8LbnlF4VQv+T43NfPMDyhZYIqBQGS5zTUdh5BBVc3+/nEjXS54qtx5hNcEc?= =?us-ascii?Q?aG72o7dIx47DoN3u1JLXACgxWXMMxRGlZcTNZdRIFMPxsThQ6mGHWtHNTd7m?= =?us-ascii?Q?iL7PwD7ZupL21h9jhvqyB2L1OReQNh1MtNvzR2LDh2hXlB/sQSlInHURqnzW?= =?us-ascii?Q?n41yLv7qpSvHntodtniCBzQ/XPKOOPxmrq/DRPGQQzq6J7PUTZhthx0acWIg?= =?us-ascii?Q?yskMEsS7jlGHpPRvOgwPbfPF5FUd5c7v5nT7madO6EfS+HlK8NqsKL4IC9Xr?= =?us-ascii?Q?3U11UF0Adz73XH8OB2j2D1+4TvdValyFuiCoNRFaAgUWcLnriq9aTz4jeC6T?= =?us-ascii?Q?1/TY15vo7x2275BKJ/h0XNes38Ts4dqL7SwwFVTdF7FzzbNeerClpQrjYbCy?= =?us-ascii?Q?D7DLb6bcMGH71peZ5o7PKFfZPBdRNCPg3L8R9NapRIilvuHzAiz58tncBxGV?= =?us-ascii?Q?/hJDVxjxXjTmN4Zz1Xw6Pb65fyTW5Q+ZN016ssyWbUotvRjvoq33Zs4GtU9L?= =?us-ascii?Q?gmA7DPD9g7ZjWVVyvHzxhODl4wmOwIaHltym7GaNUICme17ZXN/MbXeNnSoy?= =?us-ascii?Q?L+s3BCjo6ta2VYH0ur2EbAUPSXuY+TvAYpY66BoAwqgFyaU7BpTZDHUtdhrB?= =?us-ascii?Q?miAVU0w9N6n8A+QPORjWS++yH7T14i+jtcx+uYYbdAxKLHxY5XS/mxzEJuKr?= =?us-ascii?Q?VI/8J27xVFgsJ4172x6fx5YyY/kpURW7LIbas6UXHEkRkZHNmbxwd0x7tSih?= =?us-ascii?Q?ezj8vyLd1iQX7P0tPYijFk6nmtw1Can4F99MTHIYyK7Rdk4Fut0RKbJL9RLC?= =?us-ascii?Q?9wm4uFAHThgzLYjVPh4z2VxfTir2RRRC0xagvjTe3E4ohNacmtzu0OaCercb?= =?us-ascii?Q?uqZXSvfZFZU1xlAEHTFbxHGRmPDd?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR13MB27624F07A612BDCF98A8C92F9A939DM6PR13MB2762namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR13MB2762.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3a931c89-b948-496b-a420-08d8e1dba682
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2021 02:41:17.9033 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YAbyIzU3NO686J+WSQq0qOVCADwMKLPHj32EjXhL3YzysiUGkYYQ5s2cpi+qlFJ3WMOubqSvDN5p63nDdEUXwA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR13MB3114
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/9nyn3hxsV22R8haH34u9euenQWE>
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: Mon, 08 Mar 2021 02:41:27 -0000

Hi Yaakov,

Some feedback inline.

Best regards,
Haoyu

From: Yaakov Stein <yaakov_s@rad.com>
Sent: Saturday, March 6, 2021 8:36 PM
To: Haoyu Song <haoyu.song@futurewei.com>om>; detnet@ietf.org; spring@ietf.org; pce@ietf.org
Subject: RE: new draft on segment routing approach to TSN

Haoyu,

I'll address your points:

> The use of clock time as deadline requires network synchronization
That is a basic assumption of TSN networks (IMO the defining assumption).
However, the sync needn't be highly accurate - it depends on the tightness of the delay budgets.
>> Yes, I understand it. What I mean is that the method mentioned in the draft seems to be also applicable to other types of networks. For example, we can envision some time-critical traffic in DCN or WAN. If a protocol would be developed, can it also serve the other networks? If so, it would be better.


> accurate measurement of per-link propagation time
Yes, I am assuming that once an for all someone does a TDR or at least OWAMP/TWAMP/Y.1731-1wD delay measurement of the links, and these are stored in some database.
Once again, the required accuracy depends on the delay budgets.

> which can somehow limit the application scope of this work
If the delay budget only above the physically minimal delay by say less than 100 microseconds,
I agree that the previous two issues MUST be carried out. But in such cases there is no alternative.
If the delay budget is much higher than that, then one could use an RSVP-like mechanism,
sending a packet (or several packets) from source to destination collecting a stack of timestamps,
and then using that stack for the following packets.

> Mechanism should be provisioned to track where the timing requirement is violated and by how much
I'll leave the OAM for later. However there are already many high accuracy performance measurement techniques and protocols for this.
>> For this I mean something recorded in the same packet with the deadlines. If it misses the deadline, the receiver may need to know where it's violated. Other independent methods are possible, but it's better to consider if it can be integrated in the current proposal.

> Recently programmable scheduler research has proposed several primitives
Yes, I tried to stress that this ID is not limited to EDF (although sometimes that is a good strategy).
One can even reproduce Qbv behavior using a stack of deadlines (although why would one wish to do so?).

> such as PIPO and PIEO
I've heard of PIFO (Push In First out) but not PIPO. Is this a typo or something new?
I agree that there are mechanisms that are optimized for hardware, but I have come up with a very nice hardware implementation for PEDF
and prefer to find hardware implementations for optimal schedulers, rather than to determine schedulers based on optimal hardware.
>> Sorry that's a typo. I mean PIFO (although we do have a paper under review using the name PIPO). Yes I agree those are just abstract primitives. The actual implementation, if customized to a particular algorithm, would be simpler.

Y(J)S

From: Haoyu Song <haoyu.song@futurewei.com<mailto:haoyu.song@futurewei.com>>
Sent: 05/03/2021 22:46
To: Yaakov Stein <yaakov_s@rad.com<mailto:yaakov_s@rad.com>>; detnet@ietf.org<mailto:detnet@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>; pce@ietf.org<mailto:pce@ietf.org>
Subject: RE: new draft on segment routing approach to TSN


CAUTION: External sender. Do not click links or open attachments unless you know the content is safe.
Hi Yaakov,

Just got a chance to read your draft. I agree with the comments of the others that this is a very interesting work. I'll just add a few points.


  1.  The use of clock time as deadline requires network synchronization, and accurate measurement of per-link propagation time, which can somehow limit the application scope of this work. Alternatively, one can simply budget a device latency which require a router/switch to obey. In case the overall budget is evenly divided by the hops, a single parameter is enough. Of course, if one wants to customize the budget on each hop (which might be necessary considering the different capability/capacity of each hop), a stack is still needed.
  2.  Mechanism should be provisioned to track where the timing requirement is violated and by how much (e.g., using timestamp or flag). This would be very useful for troubleshooting.
  3.  Recently programmable scheduler research has proposed several primitives such as PIPO and PIEO and provided feasible hardware implementations. The scheme proposed in this draft can easily fit into these primitives.

Best regards,
Haoyu
From: spring <spring-bounces@ietf.org<mailto:spring-bounces@ietf.org>> On Behalf Of Yaakov Stein
Sent: Tuesday, February 23, 2021 5:14 AM
To: detnet@ietf.org<mailto:detnet@ietf.org>; spring@ietf.org<mailto:spring@ietf.org>; pce@ietf.org<mailto:pce@ietf.org>
Subject: [spring] 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<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Farchive%2Fid%2Fdraft-stein-srtsn-00.txt&data=04%7C01%7Chaoyu.song%40futurewei.com%7C6aeaab604ad842c5ca0f08d8e122721c%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637506885364131187%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHZdFoS63OmpW1tEcp9BBksGzRGfs8IF9NpJnS%2FlXa8%3D&reserved=0>
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