Re: [Detnet] I-D Action: draft-ietf-detnet-mpls-12.txt

Toerless Eckert <tte@cs.fau.de> Mon, 14 September 2020 15:26 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 D4E3A3A0B9C; Mon, 14 Sep 2020 08:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level:
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] 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 Ppf8LrJ4XZwT; Mon, 14 Sep 2020 08:26:24 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 40D333A0B98; Mon, 14 Sep 2020 08:26:22 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id DEC6F54860E; Mon, 14 Sep 2020 17:26:17 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id D5FC0440059; Mon, 14 Sep 2020 17:26:17 +0200 (CEST)
Date: Mon, 14 Sep 2020 17:26:17 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: detnet@ietf.org, iesg@ietf.org
Message-ID: <20200914152617.GD45828@faui48f.informatik.uni-erlangen.de>
References: <159974030624.24805.8881456598444175510@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <159974030624.24805.8881456598444175510@ietfa.amsl.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/NW9Bw__upP_HpIbF7t0Qa4E7UgI>
Subject: Re: [Detnet] I-D Action: draft-ietf-detnet-mpls-12.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, 14 Sep 2020 15:26:26 -0000

Now -12 says:

"DetNet provides a capability for the delivery of data flows with extremely low packet loss rates and
 bounded end-to-end delivery latency"

What exactly is the capability that DetNet provides for bounded end-to-end delivery latency ?

I can only find hidden evidence in the text that DetNet MPLS can operate on top of pre-existing
technologies that could provide these benefits, but thats not what the document says,
and to me there is a big differnce between provide capability" and "can operate on top of"
so i continue to say that this is false adertisement: Any p2p LSP could claim to proide
these capabilities as long as somebody figured out e.g.: how to deploy and operationalize rfc2212.
Which i am not aware anyone has done. Nor do i see in section 5.2 any specific parameters
 that would be required to instantiate 2212, but just hand waiving.

Cheers
    Toerless