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

"Andrew G. Malis" <agmalis@gmail.com> Mon, 17 January 2022 15:13 UTC

Return-Path: <agmalis@gmail.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 DF9003A0D9E; Mon, 17 Jan 2022 07:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ovFfN1U9qqkU; Mon, 17 Jan 2022 07:13:16 -0800 (PST)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EB743A0D96; Mon, 17 Jan 2022 07:13:16 -0800 (PST)
Received: by mail-il1-x12c.google.com with SMTP id u5so10738010ilq.9; Mon, 17 Jan 2022 07:13:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FQbQERF7GcaSM4v80+j7lHpzGsX8aWNt2gNwa/2hI/I=; b=T5KlbOCoAVQqA6nQn6hOzPftUJWgO4w3XEdxuOj6WF5N+FueJNp+j1qeXHU0eDmC81 rXZZzqOgqg195cNEL3Q37gOaHy8X5L296KcFXxiMuo+eGP+XEKrYXfkFsY6shJoSBZ+6 M94MWszWZ33cND96qDzAQvShOfBiRZrUusitmxavznS8evr37Pw6BH6xanUw9LmfvnwV Mht0A9tdHwmNkRmcnAG010m3TpsKEl2VvnjklXoT9GebRBO7DTGKUG0uSscC1tOo4rmY enMFxEF48aqRkLfe8oO7Nayo/akATvADkJwzHdWyxBFDuESIqHif443NqvrYev+Oxibq NAeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FQbQERF7GcaSM4v80+j7lHpzGsX8aWNt2gNwa/2hI/I=; b=7jhW8KO/s4Msv0JjLYESsJCDypI+aLIKAPdDOReUjj2uzuhP7tbQLyjMT9bJB2uo03 EPq5pnWmTHCfaNtb1boDbNAJJ/+Okf5lXGbpBOt91BJe9waQmPSHn1gtM5KAtAbv+ptH 7bllyAFrUwyBD76edjI0dWNpwiuItKCp3sOZjv+YfVUgcA2ctY6pJH9/vfjQASlGFoCh Vrzgucjx30VBPJr1o/2Bg6YW0eXW2h9pFZwEEnbcmhQ7NwfWYiXVT+GTRYJVMVbphADW XdijdqdKXd5nJysRWZEyWu33Wqzf8c19FaMG5hS8U9qas4fK92KSYyz+rO0JFv686TkW AJAQ==
X-Gm-Message-State: AOAM531TDXDk1PesAMhgUD9E5+9zTkIn5AHTDOY26i351jMqtiCT3oXI 3jGW8ILR0vWLflhbnrsN/8UGiktPt1vF7+8xph8=
X-Google-Smtp-Source: ABdhPJx9Ouq0vbu2NzUNVSOWmqRyacHJQ3NcMiIdoahRw8XfhboKdNtHGWXJTBC/efHtc5r5wL1zZO0nkkXxkEhpsuM=
X-Received: by 2002:a05:6e02:180e:: with SMTP id a14mr10896797ilv.300.1642432395238; Mon, 17 Jan 2022 07:13:15 -0800 (PST)
MIME-Version: 1.0
References: <164190363391.26857.15141258232852647447@ietfa.amsl.com> <c945ba9a62174d07a072f09a93a31805@huawei.com> <100ef047-921f-ea06-c4c2-083c17dafb7d@labn.net> <d04d10e5654a4de886b4b02b0ca023f4@huawei.com> <CAA=duU233xhFeQ3o-i6EZOGMVEbBpPuuGrkc4CGNz+NCN0ntEA@mail.gmail.com> <fca66e38824c4a9093b06e9fd4b47d06@huawei.com> <CAA=duU2+3bX7UiNkbm3jN=j4jk5dhYsdbh-zsrziLmMCUc7EYQ@mail.gmail.com> <SJ0PR14MB47928558B89C65F6BF37F914C3579@SJ0PR14MB4792.namprd14.prod.outlook.com>
In-Reply-To: <SJ0PR14MB47928558B89C65F6BF37F914C3579@SJ0PR14MB4792.namprd14.prod.outlook.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 17 Jan 2022 10:12:58 -0500
Message-ID: <CAA=duU3k63pBNFSyjXdEZn9=xh1sfx04hcHN2Zv6OfgrbG-jKw@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Cc: Dirk Trossen <dirk.trossen@huawei.com>, Greg Mirsky <gregimirsky@gmail.com>, DetNet WG <detnet@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007c5fa605d5c897b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/qER3nJogAibjMWAHFM9qlcPhkAo>
Subject: Re: [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: Mon, 17 Jan 2022 15:13:22 -0000

Lou,

As you noted, this is a framework document, not a protocol extension
document. Dirk asked a question about whether he needed to discuss the need
for RSVP control of DetNet, and I was just reminding him that it's already
included in the framework draft.

Cheers,
Andy


On Mon, Jan 17, 2022 at 8:49 AM Lou Berger <lberger@labn.net> wrote:

> Andy,
>
> Are you expecting to put in RSVP extensions for jetnet in this document?
> Typically we don't see protocol extensions in framework documents...
>
> Lou
> ------------------------------
>
> On January 17, 2022 7:28:40 AM "Andrew G. Malis" <agmalis@gmail.com>
> wrote:
>
>> Dirk and Greg,
>>
>> As always, comments and improvements on the draft are welcome!
>>
>> Cheers,
>> Andy
>>
>>
>> On Mon, Jan 17, 2022 at 3:26 AM Dirk Trossen <dirk.trossen@huawei.com>
>> wrote:
>>
>>> Andy,
>>>
>>>
>>>
>>> Thanks, indeed, this was our entry point and I’m studying the latest
>>> version to see how we can build on and extend from it.
>>>
>>>
>>>
>>> Best,
>>>
>>>
>>>
>>> Dirk
>>>
>>>
>>>
>>> *From:* detnet [mailto:detnet-bounces@ietf.org] *On Behalf Of *Andrew
>>> G. Malis
>>> *Sent:* 14 January 2022 18:37
>>> *To:* Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>
>>> *Cc:* DetNet WG <detnet@ietf.org>; Lou Berger <lberger@labn.net>; TEAS
>>> WG Chairs <teas-chairs@ietf.org>
>>> *Subject:* Re: [Detnet] FW: New Version Notification for
>>> draft-trossen-detnet-rsvp-tsn-01.txt
>>>
>>>
>>>
>>> Dirk, Lou, et al,
>>>
>>>
>>>
>>> Don't forget that draft-ietf-detnet-controller-plane-framework already
>>> has some text discussing the use of RSVP-TE as (a part of) the DetNet
>>> control plane.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Andy
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 14, 2022 at 12:18 PM Dirk Trossen <dirk.trossen=
>>> 40huawei.com@dmarc.ietf.org> wrote:
>>>
>>> Lou,
>>>
>>> Thanks for coming back on this. Great to hear the discussions with the
>>> TEAS chairs, shedding light on the key issue from 110 regarding the long
>>> term home.
>>>
>>> When you talk about the 'general solution for RSVP control of DetNet',
>>> are you talking about identifying the need (e.g., use cases) for doing so
>>> or the actual solution for doing so (beyond just TSN-based L2s)? The former
>>> is currently included as a note in the (small) draft update, i.e.
>>> attempting to provide a better motivation as to why end user initiated
>>> reservation would be used; our plan is to include this into the next
>>> update. For the latter, our approach was to narrow the scope to RSVP over
>>> TSN networks, i.e. it's not a general solution. Are you saying that such
>>> general solution ought to be addressed first before a narrower one for TSN?
>>>
>>> Best,
>>>
>>> Dirk
>>>
>>> -----Original Message-----
>>> From: Lou Berger [mailto:lberger@labn.net]
>>> Sent: 14 January 2022 14:20
>>> To: Dirk Trossen <dirk.trossen@huawei.com>
>>> Cc: TEAS WG Chairs <teas-chairs@ietf.org>; DetNet WG <detnet@ietf.org>
>>> Subject: Re: [Detnet] FW: New Version Notification for
>>> draft-trossen-detnet-rsvp-tsn-01.txt
>>>
>>> Dirk,
>>>
>>> Thank you for this and reviving your work.   The AD and TEAS/DetNet
>>> chairs did discuss this and agreed that TEAS is probably the right long
>>> term home for this work, but only once the DetNet WG agrees that this work
>>> should move forward.
>>>
>>> One key comment (I think made at 110 or on the list) that needs to be
>>> addresses before this work can be really considered  is identifying the
>>> general  solution for RSVP control of DetNet. Your work can be the
>>> foundation for this or it can be done in a separate document -- in other
>>> words, RSVP for DetNet is a necessary precursor for RSVP extensions in
>>> support of DetNet/TSN.
>>>
>>> We hope that you are willing to work on and even publish the initial
>>> version of an RSVP for DetNet document.
>>>
>>> Thank you,
>>>
>>> Lou
>>>
>>> As DetNet Co-Chair
>>>
>>> On 1/11/2022 7:26 AM, Dirk Trossen wrote:
>>> > 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
>>> >
>>> >
>>> > _______________________________________________
>>> > 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
>>>
>>>