Re: [Detnet] liaison response to ITU-T SG13 LS217

Janos Farkas <Janos.Farkas@ericsson.com> Tue, 23 November 2021 12:25 UTC

Return-Path: <Janos.Farkas@ericsson.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A633A077E for <detnet@ietfa.amsl.com>; Tue, 23 Nov 2021 04:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level:
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.701, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, GB_ABOUTYOU=0.5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 yB0YKgXSGl2Z for <detnet@ietfa.amsl.com>; Tue, 23 Nov 2021 04:25:25 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150085.outbound.protection.outlook.com [40.107.15.85]) (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 56FB83A0780 for <detnet@ietf.org>; Tue, 23 Nov 2021 04:25:25 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lnRv3+zv95CNdWOY+Ms/wNnMWgph1shjelA/1pRLZ6I7TjZngNh9CYDkgkq0rzcKmqcz92mBUUR+WXMYBEPpnzFOOCXOC6609rQW2R3M2VkrZHG11sGAcP+NSBfQddlzrDqaeGGmiT0bceytrf6WXJ8e6XzqQKmXgigkCVLwpPyK/fLJ93q/BKGTVgROZxb4UzCP6ZNxhPMncf/tuzkx48/kzmgRtksRIj0AZJKR09NFgZwzuU8N7y98V/oMcXU3z0ODTiI74lubfvyXCmsUL6EReamXgy4+49ao1G7SZvNVgxDneT2bCLwQgEOSoHxOqZX1UTjusQYZuVIDZ6RJ1w==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YH2bRJHA0kNRAi2s4Adhw0YdZFaUIU5DSCd2PbV+Ag8=; b=L5yF3p3YsFfgpxpsrUKbHTYmIXtmgDSleJ9ldI6k1XWKTFY8DQpoYT8/hcI97h2sqY+dafMUa3+ooCiwQ2Cw18mRr6uNGoJqDd6EHTjKebORt+L+kVcI80O1Iv9h1sWK1yJjJzDMj5vTPU4EXSHXJ8OmaiKcqgChRQ+ruahuINHBHm93QaffpMRwfj7p7zkAhF8/eG1xwkuFFfaneNbZO/EdyMHgCDXGtxpBvV+cAz4lopCdwsi1zH49hTmhI9coXwwduYvkveHZj+YNdG8liJXzA7cUoHl2ySZ+m2YqffWhiwQV37rfvfeESE+vH6YeJyPl6dJmiMrChYHh9wrkaQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YH2bRJHA0kNRAi2s4Adhw0YdZFaUIU5DSCd2PbV+Ag8=; b=qyG92DvExdlOKirSQvgicCOl6DtxMevP92KP0nk4JHtyCFP/Caw2I9Kc1Jha1YvVfaOBTRyt1DrcFQlYvGw/u0rwV0buw+vdiH6OxoUTqjFHqapEp4+SFxsucJjLLsF5s1CSB9e/c3kFQ3VJ6yjfYJfmKIvhe0SF5juGZ2ifKvY=
Received: from AS8PR07MB8298.eurprd07.prod.outlook.com (2603:10a6:20b:37d::6) by AS8PR07MB8249.eurprd07.prod.outlook.com (2603:10a6:20b:378::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4734.20; Tue, 23 Nov 2021 12:25:20 +0000
Received: from AS8PR07MB8298.eurprd07.prod.outlook.com ([fe80::8c1a:d057:2044:25ea]) by AS8PR07MB8298.eurprd07.prod.outlook.com ([fe80::8c1a:d057:2044:25ea%9]) with mapi id 15.20.4734.017; Tue, 23 Nov 2021 12:25:20 +0000
From: Janos Farkas <Janos.Farkas@ericsson.com>
To: DetNet WG <detnet@ietf.org>
CC: "liaison-coordination@iab.org" <liaison-coordination@iab.org>, Scott Mansfield <scott.mansfield@ericsson.com>
Thread-Topic: [Detnet] liaison response to ITU-T SG13 LS217
Thread-Index: AdfXzsD4M/FimOt+TZOvDZAXLdLwIAAbPK0AAI0/SIAAfNUqcAEAOGeA
Date: Tue, 23 Nov 2021 12:25:20 +0000
Message-ID: <AS8PR07MB8298CCF23284873FFF6A6B4DF2609@AS8PR07MB8298.eurprd07.prod.outlook.com>
References: <AS8PR07MB82989F4C659AB79AE0653B56F2959@AS8PR07MB8298.eurprd07.prod.outlook.com> <YY8sIDMniQ9mpPN7@faui48e.informatik.uni-erlangen.de> <AS8PR07MB8298C8D772BE8E6580A23113F2989@AS8PR07MB8298.eurprd07.prod.outlook.com> <AS8PR07MB82987A2AC203B3703EC44B37F29B9@AS8PR07MB8298.eurprd07.prod.outlook.com>
In-Reply-To: <AS8PR07MB82987A2AC203B3703EC44B37F29B9@AS8PR07MB8298.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=ericsson.com;
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ecd863fe-db2d-4a87-3a3f-08d9ae7c50f2
x-ms-traffictypediagnostic: AS8PR07MB8249:
x-microsoft-antispam-prvs: <AS8PR07MB82495039DBAF1164BAC63618F2609@AS8PR07MB8249.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: laBojq11kHyMkngjCWA3mnZjITHAkpeluJWKp37CBl7IGcwnppf6moo4AKa9NjCGIN5pwwgbDTaJPlJgKNaxenZfJy8o/QoCVHCQulCvSYADkA6Pn7M5yY1djKg0+KcL+e0GWbjquMJr4e+l6ICrnPoh/qLwMHiFiPfJpPmHg190l112r00PLpHu0hLeH1l3CQ4/dfkqVVVBzAtFS863iKYgdb4B++e5Y5KuVWlTRyrNQtefpWLi6upCoOT4QX6tbtFygfLO1Ivmz8YL6oAfKtfr9lBiOsE7KZoB4h2h9DI0fODLhvmb04RKu1l6qzNd/4fwouUufOVkZZAccqfen3vw5dy/fonSQf9JtfXeD73iAnqaRZ3Yo2fPsHUj1EWeuOjHq01Mjc+q/eTc+zAi/IKAIWQxP/FMuzik1nNsCnML5sD8Czni22HpXs8eF8LSfawq9eW3aHZH+XE+IaUdTmrTssEZUVv9AQmuCNvX97fFRNCUBWzOCKyqh+NZKV/86jO+eLGETHdat/FDiGLKD06QRiL+JhatJLPgIb+/l/d4n5q0i08lK8M7qmbcuju87Hdc5sRNSQjZd6n3MtCn+G3f4kJ8aWxPnJf85hrXdq/V3TOxecYQqjXcjVP6r3S3FcBrEWeqZR2hUSTdCeQIOw7xToxEanGknf4LcoZsK0yPCIoCTJUpUZavWDOSkjr/3wk2acqdVbAuOElI6uTlWgHOykmea+jGdBsjjfbeN3mviyCWsEADBVMofdgjAT1kiVme2lbjBFpq1W0XsLYRTl/QlQrs/7mNkYbzG+Yh9MyOJXVqXvxY2h1GUkx8BbnBO5+7ALp6I7OdEOTBEokyYQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AS8PR07MB8298.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(86362001)(71200400001)(53546011)(122000001)(30864003)(38070700005)(6506007)(508600001)(54906003)(66476007)(83380400001)(33656002)(4326008)(5660300002)(66946007)(66574015)(107886003)(76116006)(66556008)(66446008)(38100700002)(2906002)(64756008)(316002)(52536014)(966005)(6916009)(55016003)(186003)(7696005)(26005)(8676002)(8936002)(82960400001)(9686003); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?iso-8859-1?Q?8NnE+Zvw4N2p45RltarPQEkgp+x/C/BXqV6ngobsyEtAOtACqHlIRemSoj?= =?iso-8859-1?Q?c/lMeO2YLUImkwou8Ay3eqFzCduhTXFcuvDqQ339C1ffYyDBNQgg8P7UOk?= =?iso-8859-1?Q?JLrwQrmIhsnNfIlRDAqQLLDiOMuTAXmT8L9uVdzjRBvjWLED/k+GtFjNkn?= =?iso-8859-1?Q?VUVs4Vtn7993NukmU1/dQwe+weAXgDSL6qnlAO7yEKGFwano1SP5+nvZ7B?= =?iso-8859-1?Q?/1yURAPq9fYlQmXafe1l0Qq8Uv1OXpiIEQmJZtfHywjFItUGusUBNK72ph?= =?iso-8859-1?Q?6qjYquBjVb26K26U08J2jTyhGAsoDRUlf9okUAMEKntG7cdkX7bqukmZMt?= =?iso-8859-1?Q?VvQN5Q7TMLyFZSKMe0bwtRbJBA/aq69RxRKKe3D+tY+OlLQ5ceXy+wDSsS?= =?iso-8859-1?Q?LLuwqtSjr+bSnhAxMbIcyQRKILWCafhN9uU9Q/yqHF3FpufVb+0i6JG7GP?= =?iso-8859-1?Q?Yg6zQdq8X05APGQWzCt8/vK0MpKIHsi0Gnd8emFv+ZGWvDAz0gCkBRET0z?= =?iso-8859-1?Q?yDxtkH8uTWfZa129k2Y96NxLy2Wy8TEE/bVs96mNMNxpb1CiGzXQ/5z2xO?= =?iso-8859-1?Q?VX7Dx7vyEoMTJFCVWS1WAX2aqVXSBNgrMv+H1tkcEcfsFnTDNGEE/YJRCF?= =?iso-8859-1?Q?7OEVVVA7fnlFbqcC5dDjpud6fLJn+zBEqWUhmlxSDrwTrJv7uIVDJmAZ8n?= =?iso-8859-1?Q?59qHZAQ0iUaPFrHlp/VikdtXGRKtk3jJzr/6ciW9fKHjbvYv6WTpl3WoO1?= =?iso-8859-1?Q?sbHEb9qSzhlgVg97FneWpXCmNxHTGtRvqyuVpbXn1/fc6+5i6c8nlF1p2V?= =?iso-8859-1?Q?kcUGBvY9ppUtkEK9Rs8I45f/bP33DdOWxTwotwPlYPAmOfawWOXbv6BpT/?= =?iso-8859-1?Q?hwXQUz+WLL6OThRm1ID+MsXW3ypY7rESqryhNN8P7apPO3h7rXm2Yfj0Re?= =?iso-8859-1?Q?IZbMUBl6X/Ou4MGNEm0ZN8iLeaftGASWrDA1Qr2tx5GD9s/7Zr9w5Uay07?= =?iso-8859-1?Q?bXxG16vVhDCHWbbVwC9DRX8A5FrOedGXXArVd/nMIoCtSOiu0AecmlflA7?= =?iso-8859-1?Q?/kjXPxAP8mjFInppUT0CPwZ10vRxav5T5XtiQ4yUggwD9tBKy8A17M8vCk?= =?iso-8859-1?Q?Sqvs9HyBRQQ4QKnKB/VUbod7Nc8yj9Gsz9j+NT0PJ9nk1fq+E/xx7YIpXd?= =?iso-8859-1?Q?qFXaS2WUJA7MctevF0LTaZmD9C4Izkx1aYqGv4bnXR1L9zW+PuxKjNHm6L?= =?iso-8859-1?Q?RwsJoC3nBFg2Yjp9Y68QvYEEfItxgjyCTp/2OobzCFQOdMEL7qVBxxqbix?= =?iso-8859-1?Q?FTOP/4U4c9MiRHPS7f65zlfRG3zC3uowJjzI2Rc3C6aOzu2sF22ORjEwCo?= =?iso-8859-1?Q?Rdeo8AP1/2E/sHED3Jyry+p9fmVkAWHrI1j+jQS85jSpyjeIJDjpxHxN/n?= =?iso-8859-1?Q?Pp3J50zCZY1Usvoj2dRwQcV+PfbTTkOSP6JRUp3/USpUvg4WturIpfLSx4?= =?iso-8859-1?Q?1IqqpbFxqBAaD+BxPxgBxN79wozL/c+/sFAMCWZiqtFsDFoGFrU5IOk1y0?= =?iso-8859-1?Q?uNzyo9Sq9pR8khbQfSwDeSrmhi4aWbjpyj281v0h52P4HWQjqMqEoMHp7i?= =?iso-8859-1?Q?JnEQaB0hNxC/x7n+Sn8JRvGaaRrPmQrZVLTpvxXj3D4fLNzpmjWpDjjEpY?= =?iso-8859-1?Q?q7tvYQGSSW2sazXDsnp+81VhpEvwiuPpQ3ObABZTuyg1HhFsuvd7FhD3ev?= =?iso-8859-1?Q?m5OQ=3D=3D?=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AS8PR07MB8298.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ecd863fe-db2d-4a87-3a3f-08d9ae7c50f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Nov 2021 12:25:20.6297 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: W/hrWfx1hs5Zv0XoX7aD4fRqgSrmBtxDcGiWAur0Fo6R7+Mhp0RtROUKaLaogxftjk9e+hCcS9c85q265+y26IQr6a9KziZ1vbPKtmnD7KU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AS8PR07MB8249
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/4UXqi46iXDhbMnoK_ZXn19DL36Q>
Subject: Re: [Detnet] liaison response to ITU-T SG13 LS217
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2021 12:25:31 -0000

Hi,

We have not received any further comments. We are moving on and sending the latest version copied here.

Regards,
Janos

-------------------------------------
Dear Colleagues,

The Internet Engineering Task Force (IETF) Deterministic Networking (DetNet) Working Group (WG) appreciates your liaison statement informing us about your work. We would like to take the opportunity to inform you about our work and share some of our observations on the work referenced in your Liaison https://datatracker.ietf.org/liaison/1753/.

For those not familiar with the IETF DetNet WG, a description of its charter cand be found at https://datatracker.ietf.org/wg/detnet/about/. The WG defines technology for Internet Protocol (IP) and Multiprotocol Label Switching (MPLS) networks to achieve bounded latency, including upper and lower bound, i.e., bounded packet delay variation (sometimes referred to as jitter), bounded loss, and high availability/reliability. The DetNet WG collaborates with the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group (TG) to define a common architecture for both Layer 2 and Layer 3. 

As a Layer 3 routed technology, one of the benefits of DetNet is that it provides desired deterministic characteristics at a larger scale than TSN. We would also like to point out that the way of working in the WG is evolutionary, from addressing more tractable problems towards more complex problems. We would like to inform you that the first phase of DetNet standards is mature, the majority have been published, see: https://datatracker.ietf.org/wg/detnet/documents/.  Considering your interest on large scale networks, we note the WG has already begun work on addressing larger scale networks. For example, see https://datatracker.ietf.org/meeting/interim-2021-detnet-01/session/detnet and https://datatracker.ietf.org/meeting/112/session/detnet.

Upon reading your documents, we think that DetNet has technology solution components for many of the requirements you describe in your documents. However, we note that DetNet work appears to not be reflected  in either ITU-T Y.3113 or the Draft Recommendations attached to your liaison. Draft Recommendation ITU-T Y.IMT2020-jg-lsn references the use of the time-stamping function of RTP, UDP and TCP, implying the use case is IP packets, whereas the statement in this Draft (and ITU-T Y.3113) says, "Routing and upper layer functions lie outside the scope of this Recommendation". It is not clear if this solution is targeted to IP networks. As we have explained above, the DetNet WG is chartered by the IETF to provide bounded latency solutions for IP networks.

The definition of domain (3.2.2 in ITU-T Y.3113 and ITU-T Y.IMT2020-fa-lg-lsn) cites RFC 8655, "Deterministic Networking Architecture". However, this definition of domain is different than RFC 8655, which focuses on the capabilities of the nodes, not their administrator. The definition of "large scale" in the provided documents is  "16 or more relay nodes". It is not clear where the number 16 is derived as a definition of a large-scale network. Please note that the DetNet WG defined solutions have no specific node count limitations and are support networks with more than 16 hops.

We note that ITU-T Y.IMT2020-jg-lsn relies on a solution published in a Journal, and timestamping each packet of data flows. We suggest consulting IETF experts in the Timing over IP Connection and Transfer of Clock (tictoc) WG. We also note other relevant work in ITU-T SG15/Q13, IEEE 1588, IEEE 802.3, and IEEE 802.1.
As the IETF's Liaison statement to ITU-T-TSAG (https://datatracker.ietf.org/liaison/1677/) expressed, if the intent of this work covers IETF technologies, requirements or proposals, it is requested for solution work to be discussed in IETF before any work in other SDOs. The success of standardization efforts is dependent on collaboration among the SDOs, as opposed to duplication of efforts and multiple diverging solutions, which will not benefit the industry. 

The DetNet WG is interested in addressing the needs of the industry. If there are specific questions about DetNet or certain aspects that you consider as gaps to meet your requirements, we encourage your participants to bring those questions and discussion points directly to the DetNet WG. We are also always open to organize meetings for discussions about DetNet. We look forward to seeing DetNet being adopted by your members to support your specifications and we welcome all interested parties to join our efforts.





-----Original Message-----
From: detnet <detnet-bounces@ietf.org> On Behalf Of Janos Farkas
Sent: Thursday, November 18, 2021 11:17 AM
To: DetNet WG <detnet@ietf.org>
Cc: liaison-coordination@iab.org; Scott Mansfield <scott.mansfield@ericsson.com>
Subject: Re: [Detnet] liaison response to ITU-T SG13 LS217

Hi,

I think the latest version below is good to be sent.
Please let us know if you have further comments or any objections.
If no objections on the list until November 22, then we will send the liaison response (so that they receive it in time for their upcoming plenary).

Regards,
Janos


-----Original Message-----
From: detnet <detnet-bounces@ietf.org> On Behalf Of Janos Farkas
Sent: Monday, November 15, 2021 11:44 PM
To: Toerless Eckert <tte@cs.fau.de>de>; DetNet WG <detnet@ietf.org>
Subject: Re: [Detnet] liaison response to ITU-T SG13 LS217

Hi Toerless,

Thank you for the suggestions!
I've incorporated them in the updated version below, please see the 4th and the last paragraphs. 

I've downloaded Y3113 from: https://www.itu.int/rec/T-REC-Y.3113-202102-I.

I understand the not to be lost too much in details approach. However, I think it is good to point to a couple of specifics.

Cheers,
Janos


-------------------------------------
Dear Colleagues,

The Internet Engineering Task Force (IETF) Deterministic Networking (DetNet) Working Group (WG) appreciates your liaison statement informing us about your work. We would like to take the opportunity to inform you about our work and share some of our observations on the work referenced in your Liaison https://datatracker.ietf.org/liaison/1753/.

For those not familiar with the IETF DetNet WG, a description of its charter cand be found at https://datatracker.ietf.org/wg/detnet/about/. The WG defines technology for Internet Protocol (IP) and Multiprotocol Label Switching (MPLS) networks to achieve bounded latency, including upper and lower bound, i.e., bounded packet delay variation (sometimes referred to as jitter), bounded loss, and high availability/reliability. The DetNet WG collaborates with the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group (TG) to define a common architecture for both Layer 2 and Layer 3. 

As a Layer 3 routed technology, one of the benefits of DetNet is that it provides desired deterministic characteristics at a larger scale than TSN. We would also like to point out that the way of working in the WG is evolutionary, from addressing more tractable problems towards more complex problems. We would like to inform you that the first phase of DetNet standards is mature, the majority have been published, see: https://datatracker.ietf.org/wg/detnet/documents/.  Considering your interest on large scale networks, we note the WG has already begun work on addressing larger scale networks. For example, see https://datatracker.ietf.org/meeting/interim-2021-detnet-01/session/detnet and https://datatracker.ietf.org/meeting/112/session/detnet.

Upon reading your documents, we think that DetNet has technology solution components for many of the requirements you describe in your documents. However, we note that DetNet work appears to not be reflected  in either ITU-T Y.3113 or the Draft Recommendations attached to your liaison. Draft Recommendation ITU-T Y.IMT2020-jg-lsn references the use of the time-stamping function of RTP, UDP and TCP, implying the use case is IP packets, whereas the statement in this Draft (and ITU-T Y.3113) says, "Routing and upper layer functions lie outside the scope of this Recommendation". It is not clear if this solution is targeted to IP networks. As we have explained above, the DetNet WG is chartered by the IETF to provide bounded latency solutions for IP networks.

The definition of domain (3.2.2 in ITU-T Y.3113 and ITU-T Y.IMT2020-fa-lg-lsn) cites RFC 8655, "Deterministic Networking Architecture". However, this definition of domain is different than RFC 8655, which focuses on the capabilities of the nodes, not their administrator. The definition of "large scale" in the provided documents is  "16 or more relay nodes". It is not clear where the number 16 is derived as a definition of a large-scale network. Please note that the DetNet WG defined solutions have no specific node count limitations and are support networks with more than 16 hops.

We note that ITU-T Y.IMT2020-jg-lsn relies on a solution published in a Journal, and timestamping each packet of data flows. We suggest consulting IETF experts in the Timing over IP Connection and Transfer of Clock (tictoc) WG. We also note other relevant work in ITU-T SG15/Q13, IEEE 1588, IEEE 802.3, and IEEE 802.1.
As the IETF's Liaison statement to ITU-T-TSAG (https://datatracker.ietf.org/liaison/1677/) expressed, if the intent of this work covers IETF technologies, requirements or proposals, it is requested for solution work to be discussed in IETF before any work in other SDOs. The success of standardization efforts is dependent on collaboration among the SDOs, as opposed to duplication of efforts and multiple diverging solutions, which will not benefit the industry. 

The DetNet WG is interested in addressing the needs of the industry. If there are specific questions about DetNet or certain aspects that you consider as gaps to meet your requirements, we encourage your participants to bring those questions and discussion points directly to the DetNet WG. We are also always open to organize meetings for discussions about DetNet. We look forward to seeing DetNet being adopted by your members to support your specifications and we welcome all interested parties to join our efforts.




-----Original Message-----
From: Toerless Eckert <tte@cs.fau.de> 
Sent: Saturday, November 13, 2021 4:08 AM
To: Janos Farkas <Janos.Farkas@ericsson.com>
Cc: DetNet WG <detnet@ietf.org>
Subject: Re: [Detnet] liaison response to ITU-T SG13 LS217

Janos:

Thanks a lot for the writeup.

I find this liaison exchange standalone cumbersome and most likely not very useful by by itself. You found a couple of technical points and gave them a few more pointers, but will that affect anything on their side ? (btw.: i don't have access to Y.3113, so i can't judge what you wrote, but i am sure its correct)

Maybe a bit tongue in cheek, but fundamentally honest:

" Thank you for your liaison. Upon reading your documents, we
  think that DetNet has technology solution compoments for
  many of the requirements you describe in your documents.
  We look forward to see DetNet being adopted by your members
  with the help of your specifications.
  
  If there more specific questions about DetNet and/or
  gaps you identify in it to meet your requirements, we encourage
  your participants to bring those questions and discussion points
  directly to the DetNet WG. We are also always open to look into
  organizing workshops for a more structured ToI and/or discussion
  about DetNet. "
  
In other words: why not market/explain DetNet to them and/or have them tell us what we're missing. For example upon scanning their documents i saw them discussing an aggregation function/component, which Pascal also is interested in. So it might be useful for more DetNet folks to identify if anything theyve written can serve as additiona evidence for gaps we have.

And wrt to Toi: Last time we had good overview of DetNet was in Bangalore (joint meeting with TSN), so not a bad time to think having a similar event again.

And doing it virtually might actually reach more people than in-person, especially when we do it on IETF webex and make it easy to attend. As i said, there is likely a larger research community out there working on TSN that we might attract as well if we spend a bit of time upfront to market the event to researchers and are careful with the timing so its useful for such type of attendees.

Cheers
    Toerless


On Fri, Nov 12, 2021 at 02:09:38PM +0000, Janos Farkas wrote:
> WG,
> As we discussed this week, we suggest responding to the liaison we received from ITU-T SG13: https://datatracker.ietf.org/liaison/1753/.
> Several of us worked on an initial draft proposal as contributors, see below.
> Please review and comment.
> Regards,
> János and Lou
> 
> 
> Dear Colleagues,
> The Internet Engineering Task Force (IETF) Deterministic Networking (DetNet) Working Group (WG) appreciates your liaison statement informing us about your work. We would like to take the opportunity to inform you about our work and share some of our observations on the work referenced in your Liaison https://datatracker.ietf.org/liaison/1753/.

> For those not familiar with the IETF DetNet WG, a description of its charter cand be found at https://datatracker.ietf.org/wg/detnet/about/. The WG defines technology for Internet Protocol (IP) and Multiprotocol Label Switching (MPLS) networks to achieve bounded latency, including upper and lower bound, i.e., bounded packet delay variation (sometimes referred to as jitter), bounded loss, and high availability/reliability. The DetNet WG collaborates with the IEEE 802.1 Time-Sensitive Networking (TSN) Task Group (TG) to define a common architecture for both Layer 2 and Layer 3.

> As a Layer 3 routed technology, one of the benefits of DetNet is that it provides desired deterministic characteristics at a larger scale than TSN. We would also like to point out that the way of working in the WG is evolutionary, from addressing more tractable problems towards more complex problems. We would like to inform you that the first phase of DetNet standards is mature, the majority have been published, see: https://datatracker.ietf.org/wg/detnet/documents/.  Considering your interest on large scale networks, we note the WG has already begun work on addressing larger scale networks. For example, see https://datatracker.ietf.org/meeting/interim-2021-detnet-01/session/detnet and https://datatracker.ietf.org/meeting/112/session/detnet.

> We note that DetNet work appears to not be reflected  in either ITU-T Y.3113 or the Draft Recommendations attached to your liaison. Draft Recommendation ITU-T Y.IMT2020-jg-lsn references the use of the time-stamping function of RTP, UDP and TCP, implying the use case is IP packets, whereas the statement in this Draft (and ITU-T Y.3113) says, "Routing and upper layer functions lie outside the scope of this Recommendation". It is not clear if this solution is targeted to IP networks. As we have explained above, the DetNet WG is chartered by the IETF to provide bounded latency solutions for IP networks.

> The definition of domain (3.2.2 in ITU-T Y.3113 and ITU-T Y.IMT2020-fa-lg-lsn) cites RFC 8655, "Deterministic Networking Architecture". However, this definition of domain is different than RFC 8655, which focuses on the capabilities of the nodes, not their administrator. The definition of "large scale" in the provided documents is  "16 or more relay nodes". It is not clear where the number 16 is derived as a definition of a large-scale network. Please note that the DetNet WG defined solutions have no specific node count limitations and are support networks with more than 16 hops.

> We note that ITU-T Y.IMT2020-jg-lsn relies on a solution published in a Journal, and timestamping each packet of data flows. We suggest consulting IETF experts in the Timing over IP Connection and Transfer of Clock (tictoc) WG. We also note other relevant work in ITU-T SG15/Q13, IEEE 1588, IEEE 802.3, and IEEE 802.1.
> As the IETF's Liaison statement to ITU-T-TSAG (https://datatracker.ietf.org/liaison/1677/) expressed, if the intent of this work covers IETF technologies, requirements or proposals, it is requested for solution work to be discussed in IETF before any work in other SDOs. The success of standardization efforts is dependent on collaboration among the SDOs, as opposed to duplication of efforts and multiple diverging solutions, which will not benefit the industry. We welcome all interested parties to join our efforts.
> 

> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet


--
---
tte@cs.fau.de

_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet

_______________________________________________
detnet mailing list
detnet@ietf.org
https://www.ietf.org/mailman/listinfo/detnet