[Detnet] FW: New Version Notification for draft-trossen-detnet-rsvp-tsn-01.txt

Dirk Trossen <dirk.trossen@huawei.com> Tue, 11 January 2022 12:27 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 AF71B3A0C05 for <detnet@ietfa.amsl.com>; Tue, 11 Jan 2022 04:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 04tdKttoTJUy for <detnet@ietfa.amsl.com>; Tue, 11 Jan 2022 04:27:04 -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 206D63A0C04 for <detnet@ietf.org>; Tue, 11 Jan 2022 04:27:04 -0800 (PST)
Received: from fraeml743-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4JY8y60msbz6GD5J for <detnet@ietf.org>; Tue, 11 Jan 2022 20:24:14 +0800 (CST)
Received: from lhreml704-chm.china.huawei.com (10.201.108.53) by fraeml743-chm.china.huawei.com (10.206.15.224) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.20; Tue, 11 Jan 2022 13:26:59 +0100
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.20; Tue, 11 Jan 2022 12:26:59 +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.2308.020; Tue, 11 Jan 2022 12:26:59 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: DetNet WG <detnet@ietf.org>
Thread-Topic: New Version Notification for draft-trossen-detnet-rsvp-tsn-01.txt
Thread-Index: AQHYBuWkRLAYTGZzD0CRr6lof43CsqxdveYw
Date: Tue, 11 Jan 2022 12:26:58 +0000
Message-ID: <c945ba9a62174d07a072f09a93a31805@huawei.com>
References: <164190363391.26857.15141258232852647447@ietfa.amsl.com>
In-Reply-To: <164190363391.26857.15141258232852647447@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.205.184]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/yMW1iYnZImiRuuABPb4b_5KUeG4>
Subject: [Detnet] FW: New Version Notification for draft-trossen-detnet-rsvp-tsn-01.txt
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, 11 Jan 2022 12:27:09 -0000

All,

Apologies from our side for the silence in updating the RSVP-TSN draft (see below), capturing the main points of the discussion during the IETF111 presentation. We would want to rekindle the work after clarifying some aspects internal to the authors' organizations.

The main points, also addressed in the small changes to the previous version related to two aspects:
1. during the IETF111 discussion, the question was raised as to where the work should be placed or with which other WG to liaise with for this work (TEAS and CCAMP were mentioned). This aspect is added to the introduction and we would like to invite the list to comment on this.

2. there was a question on the use of RSVP for detnet in general, i.e. the need for endpoint-signaled communication. We placed a note into the use case section on this, intending to provide more info on this in another update before IETF113. 

Not included in this update but planned for the aforementioned update before IETF113 are also additions to the protocol formats. Also, we would like to explore the interest in a demo that could be provided to the community. 

Best,

Dirk

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: 11 January 2022 13:21
To: Dirk Trossen <dirk.trossen@huawei.com>; Juergen Schmitt <juergen.jues.schmitt@siemens.com>
Subject: New Version Notification for draft-trossen-detnet-rsvp-tsn-01.txt


A new version of I-D, draft-trossen-detnet-rsvp-tsn-01.txt
has been successfully submitted by Dirk Trossen and posted to the IETF repository.

Name:		draft-trossen-detnet-rsvp-tsn
Revision:	01
Title:		RSVP for TSN Networks
Document date:	2022-01-11
Group:		Individual Submission
Pages:		16
URL:            https://www.ietf.org/archive/id/draft-trossen-detnet-rsvp-tsn-01.txt
Status:         https://datatracker.ietf.org/doc/draft-trossen-detnet-rsvp-tsn/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-trossen-detnet-rsvp-tsn
Diff:           https://www.ietf.org/rfcdiff?url2=draft-trossen-detnet-rsvp-tsn-01

Abstract:
   This document provides a solution for control plane signaling by
   virtue of proposing changes to RSVP signaling with deterministic
   services at the underlying TSN enabled layer. The solution covers
   distributed, centralized, and hybrid signaling scenarios in the TSN
   and SDN domain. The proposed changes to RSVP IntServ, called RSVP TSN
   in the remainder of this document, provide a better integration with
   Layer 2 technologies for resource reservation, for which we outline
   example API specifications for the realization of RSVP TSN.

                                                                                  


The IETF Secretariat