Re: [Detnet] WG Last Call: draft-ietf-detnet-bounded-latency-02

Toerless Eckert <tte@cs.fau.de> Thu, 25 February 2021 19:01 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 65EC13A1EA0; Thu, 25 Feb 2021 11:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 qz170kCIjzPA; Thu, 25 Feb 2021 11:01:15 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DBCF3A1E92; Thu, 25 Feb 2021 11:00:41 -0800 (PST)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id AF4AA54804B; Thu, 25 Feb 2021 20:00:35 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id A765B440163; Thu, 25 Feb 2021 20:00:35 +0100 (CET)
Date: Thu, 25 Feb 2021 20:00:35 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Lou Berger <lberger@labn.net>
Cc: DetNet WG <detnet@ietf.org>, "draft-ietf-detnet-bounded-latency@ietf.org" <draft-ietf-detnet-bounded-latency@ietf.org>
Message-ID: <20210225190035.GA44877@faui48f.informatik.uni-erlangen.de>
References: <d38af2a0-843f-e117-3368-570f4e26c105@labn.net> <371c2363-4f15-b32f-4c96-483a31ae1c77@labn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <371c2363-4f15-b32f-4c96-483a31ae1c77@labn.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/xGW4vZ-3OSWaJlYrGO6FFFAB0ug>
Subject: Re: [Detnet] WG Last Call: draft-ietf-detnet-bounded-latency-02
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: Thu, 25 Feb 2021 19:01:18 -0000

Mea maxima culpa for missing tihs deadline, but will be happy to resubmit when it comes back to IETF
review, otherwise feel free to alreay read now and consider my input:

Very nice document overall. Due to time i'll have to postpone some more knucklehead text
details to IETF review time slot.

The one very high level comment i have is that i am missing any linkage between this
document and where in the DetNet forwarding plane to apply bounded latency control.

I also looked through the architecture and could not find anything. Likewise MPLS and
IP RFCs. Aka: nowhere in the documents can i find something saying "this is a
DetNet forwarding function where bounded-latency control is to be applied".

I am not even sure if the WG knows or agrees where that would be. Without any such tie-in,
the claims of the architecture that bounded latency is provided for by DetNet
seems like an undelivered promise. and readers of our documents would likely become
very frustrated trying to figure this out because this gap is not even explicitly acknowledged.

For example, i imagine that the most simple instance of applying bounded latency
to detnet would be a DetNet MPLS deployment, where every MPLS forwarder is a
DetNet service-node? (if that is he right word), the S-Label is label switched,
hence allowing for the forwarder to have DetNet Flow awareness and tie the appropriately
selected per-flow bounded latency operations to packets of the flow.

Of course, i would have hoped to find such text in the forwarding or architecture
RFCs, but without anything so explicit thre, why not add such a simple example
to codify this tie in between he concepts presented in this draft and the 
DetNet fowarding plane.

If there are no explicit examples for the most simple detnet forwarding functions
and where/how to apply bounded latency to it, then i think that too should be
explicitly written into this document to set expectations straight.

Cheers
    Toerless

On Sun, Feb 21, 2021 at 05:15:38PM -0500, Lou Berger wrote:
> All,
> 
> The WG last call is complete.
> 
> Authors,
> 
> Please bring any resolutions to comments received to the list. Once all
> comments are addressed please update the draft and let the WG know that it
> is ready for submission to the IESG for publications.
> 
> Thank you!
> 
> Lou
> 
> On 2/5/2021 8:30 AM, Lou Berger wrote:
> > All,
> > 
> > This starts working group last call on draft-ietf-detnet-bounded-latency-02
> > https://datatracker.ietf.org/doc/draft-ietf-detnet-bounded-latency/
> > 
> > The working group last call ends on February 19th.
> > Please send your comments to the working group mailing list.
> > 
> > Please note, there was an IPR disclosure against this document
> > submitted on January 14, 2021, see https://datatracker.ietf.org/ipr/4581/
> > While this disclosure came very late in the document life cycle,
> > it appears the filing was also relatively recent (2019-10-16) and
> > after the pre adoption IP call:
> > https://mailarchive.ietf.org/arch/msg/detnet/1mwYdadDzTLudcuH5T5O7R_KlDs
> > 
> > Positive comments, e.g., "I've reviewed this document
> > and believe it is ready for publication", are welcome!
> > This is useful and important, even from authors.
> > 
> > Thank you,
> > Lou (DetNet Co-Chair & doc Shepherd)
> > 
> > 
> > 
> > _______________________________________________
> > 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

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