[Detnet] Work on 'control plane signaling'

Dirk Trossen <dirk.trossen@huawei.com> Tue, 15 December 2020 15:53 UTC

Return-Path: <dirk.trossen@huawei.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 E46443A11F7 for <detnet@ietfa.amsl.com>; Tue, 15 Dec 2020 07:53:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 X24dBLhR5yaK for <detnet@ietfa.amsl.com>; Tue, 15 Dec 2020 07:53:58 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 201463A11F6 for <detnet@ietf.org>; Tue, 15 Dec 2020 07:53:58 -0800 (PST)
Received: from fraeml736-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CwN6N0wksz67QLR for <detnet@ietf.org>; Tue, 15 Dec 2020 23:51:40 +0800 (CST)
Received: from lhreml707-chm.china.huawei.com (10.201.108.56) by fraeml736-chm.china.huawei.com (10.206.15.217) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2106.2; Tue, 15 Dec 2020 16:53:55 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2106.2; Tue, 15 Dec 2020 15:53:54 +0000
Received: from lhreml701-chm.china.huawei.com ([10.201.68.196]) by lhreml701-chm.china.huawei.com ([10.201.68.196]) with mapi id 15.01.2106.002; Tue, 15 Dec 2020 15:53:54 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: DetNet WG <detnet@ietf.org>
Thread-Topic: Work on 'control plane signaling'
Thread-Index: AdbS+lqYa7+TQjYfReuHab85wVHsgQ==
Date: Tue, 15 Dec 2020 15:53:54 +0000
Message-ID: <8fd6aff268b84760bc96377c109bedaf@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.48.221.253]
Content-Type: multipart/alternative; boundary="_000_8fd6aff268b84760bc96377c109bedafhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/u-cwpwvEjXJbVouV9Y-JHucEMhQ>
Subject: [Detnet] Work on 'control plane signaling'
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, 15 Dec 2020 15:54:00 -0000

All,

many thanks for the great discussion during last week's interim on our plans to progress the 'control plane signaling' draft.

As we tried to outline in our revised structure (for the next draft update), our intention is to specify the required distributed end-to-end signaling for deterministic networking scenarios, not relying on managed, e.g., centralized, TE methods. With this in mind, we see the combination of RSVP-TE aspects and the interaction between RSVP at L3 and L2 solutions as the core of our contribution, labeled as 'RSVP-detnet' in our slide material. From this perspective, TSN is just one example for said L2 solutions.

Another possible route forward could be to narrow the discussion (and contribution) purely to the L3/L2 interactions between RSVP and specific L2 technologies, such as RAP (for TSN) - this route would lead then to something one could label as 'RSVP-tsn'.

We would like to seek your comments and thoughts on those possible routes. If anybody is interested in joining the efforts, please do let us know.

Best,

Dirk, on behalf of the draft authors