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

Greg Mirsky <gregimirsky@gmail.com> Fri, 14 January 2022 18:42 UTC

Return-Path: <gregimirsky@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 385083A0828; Fri, 14 Jan 2022 10:42:24 -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 XkFr7hU57LjS; Fri, 14 Jan 2022 10:42:19 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 9A76E3A0823; Fri, 14 Jan 2022 10:42:19 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id z22so37161591edd.12; Fri, 14 Jan 2022 10:42:19 -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=gTkLzDLt0p394RzNeslDj3q8iERWe2r6HHKUC0OMSHk=; b=V6ppNS+Kwb49uCqu4nNlGWXbCwrOSJlbVWTuPtHTVblNgW9f33U0R1AV09M+Pd/IF5 mhMFcs4l1J47ZYW1WdYd8NSF1eD8rIraiW+FxKRUTfLYl/o0l7SRV4vC+ETC4QfGoJyo LYGBKR0Ev8gW/6tfY7VfQhEFt3dRqUFYCByEKVX9uduFYMZx7wnfC8v2+TMIu+N4nmFL qm9XSn/Dohu8o9gF0dxN1HVKZ7Zd3Os5SAWOv0v9HQzxh2McsBKfgEd0cGjCwMBQpOwc IghfdngMDdHCH1wpZ7lOaknKfWwPk6dmidCxniiNsLlGdjIuI9yfxl5Hyd7Rn0I7ahVd vQog==
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=gTkLzDLt0p394RzNeslDj3q8iERWe2r6HHKUC0OMSHk=; b=XfgQOHQGMHPYJWjxGMiwJR9fJ4SPoc0HczzlP1tKwvI7aKTVZ4mhhytdVCX619dGjQ VQovJXfCi67tZDOpHTd3zZEm6PTjRFjv+MZUkWLwUtdqJ2DglS386c6OphVi7U4Pu5di FWoHfRwX3p7r8vDpeYZbCegX7J9dM8GN/UO8vXUSjv9CKfiPUsHrTd1uDXyQt8lgbV8y yU30juralWlkUpmCnnC6J9GNCCYn2BEyD3TyHBTahSESB8SZQz3roj010Nruj9H/VSo3 srrL2CPZKhR0wk0Jae5hU5I9kVkrMhas8jZagj1d5M9OLMcboo3mccblg5VsDvB5+w0W O+eg==
X-Gm-Message-State: AOAM533vtt6ODeMBxQDTyPQZDf82XT7ttgQlK+H2Q1I7zXxvgZu+XSb4 nh6TZjxYamoMN8oLXWy+nkGDhh+nEk1wxP2XYxfJSMcv
X-Google-Smtp-Source: ABdhPJwzpG+HTqvnMW34fdCVPc5aYhgeCE2zpQJGJ0f9UKn9/J7Om4lMX2NmVGvC7kyanV21tC8m1K/IqamJsYioZus=
X-Received: by 2002:a17:906:2802:: with SMTP id r2mr8690751ejc.172.1642185737340; Fri, 14 Jan 2022 10:42:17 -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>
In-Reply-To: <CAA=duU233xhFeQ3o-i6EZOGMVEbBpPuuGrkc4CGNz+NCN0ntEA@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 14 Jan 2022 10:42:05 -0800
Message-ID: <CA+RyBmWUuY=cjk1dDWYeG-wFNDt_whE_RUHMX-kPnAtO-50MuQ@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>, DetNet WG <detnet@ietf.org>, Lou Berger <lberger@labn.net>, TEAS WG Chairs <teas-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000878bec05d58f2982"
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/gs_C7kS_6SSC2rNoTd7NnoiIk3w>
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: Fri, 14 Jan 2022 18:42:24 -0000

Thank you,  Andy for the information. On that note, do you see any work on
the PCE side to have matching functionality in a controller?

Regards,
Greg

On Fri, Jan 14, 2022, 09:37 Andrew G. Malis <agmalis@gmail.com> wrote:

> 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
>>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>