Re: [Detnet] Magnus Westerlund's Discuss on draft-ietf-detnet-mpls-11: (with DISCUSS)

Stewart Bryant <stewart.bryant@gmail.com> Tue, 08 September 2020 16:36 UTC

Return-Path: <stewart.bryant@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 EB9123A0F7C; Tue, 8 Sep 2020 09:36:11 -0700 (PDT)
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 2076JSDoVKV2; Tue, 8 Sep 2020 09:36:10 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (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 ECD643A0F86; Tue, 8 Sep 2020 09:36:09 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id c18so19789823wrm.9; Tue, 08 Sep 2020 09:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=5TsIAWAJQDkcTTD8pMuSLOYnlOmyJ6MakyeAfZoOV2Q=; b=tJxUAdcA7F2ng5AdORtEIdjYSIwr05sGyJoKm8LvqGn5ONCRPWXI5fINlCTj1wNoQm RRU0xcZJWiSwWGMTtSAkYSNPRGVNHbtx29tswXEmhyM9W3BpQ2rO6ijiBI32Hk5P02JU ndBXs5hGiwPu2l+pfuEtoUvHxI5tA+2g00Ei5Fq10yZxyUAW6gctRMC+xZJfmRZKwMQS DgaJBacjjiCSK9B7+SdzkZmr/ah0MP18YODF521lMmI8aw5wXLbxe2bmYEr0S/zJrtqU AMHj7/jt+E+AiBqqqxpeEiN2jFjotsJ5NWPsKWwTK+AyRhRK8rhs1xe1Msg1ZGP6YKrQ vqdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=5TsIAWAJQDkcTTD8pMuSLOYnlOmyJ6MakyeAfZoOV2Q=; b=JBcsQp483sOevioGDSeL4GKbrptMmw2I9ySReZ7pCe7Ejwmi5OkKIiZK8TLH4nalUb Tg1ZJNlHHoOZZvCa8MBkmC/0mB2dSgpc8Uv1Ts5DU+mSNveIDU5TzCrTSIAeyWHCsISS SujMpvKb36WNivFx4fTUeW3ZMAKt8w1g/sizR+KO6nzQdJhr1zBqE8x/KxFn6csBFsIK TMIYlhD+KSvrVfcdVAKC2NfvyEnTvAQ7Wr7kRrWvO9UEYxzbWyA2tTuG/tYOtCAXoel6 hXTf0X/zLnGfETHGCQx3a82gcjQa2j3YpogLLlRFfyTip5V5J3sdftVX5cTXXKmCG92M erIg==
X-Gm-Message-State: AOAM533OxqDa/Viyuv0ZK/szTUPmoBh2N+OrKXql0+WAGKmvXu1dPfvD ar1Fz/z1Wl6JXLsVn+wR+NI=
X-Google-Smtp-Source: ABdhPJz9eymwvMHXtjllsOLnRJczP7nWYoYO/3HiBSe3VE64t2JJX/RfJPB3FQMYUGGtL5hReI216A==
X-Received: by 2002:adf:fe42:: with SMTP id m2mr439051wrs.367.1599582968435; Tue, 08 Sep 2020 09:36:08 -0700 (PDT)
Received: from [192.168.178.46] ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id c206sm34447908wmf.47.2020.09.08.09.36.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Sep 2020 09:36:07 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-Id: <A14A961D-E649-49AC-B6E6-C2DD7BB52122@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F42C7A82-E814-4F17-973F-2A52A1FE6729"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Tue, 08 Sep 2020 17:35:36 +0100
In-Reply-To: <159957776121.26189.12459072134609921207@ietfa.amsl.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, The IESG <iesg@ietf.org>, draft-ietf-detnet-mpls@ietf.org, detnet-chairs@ietf.org, detnet@ietf.org, Ethan Grossman <eagros@dolby.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <159957776121.26189.12459072134609921207@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/0oP9r8bDSXnRfWK0JYBIR-2n1MY>
Subject: Re: [Detnet] Magnus Westerlund's Discuss on draft-ietf-detnet-mpls-11: (with DISCUSS)
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, 08 Sep 2020 16:36:12 -0000


> On 8 Sep 2020, at 16:09, Magnus Westerlund via Datatracker <noreply@ietf.org> wrote:
> 
> Another point on 4.2.2.2:
> 
> When configured, the
>   implementation MUST track the sequence number contained in received
>   d-CWs and MUST ensure that duplicate (replicated) instances of a
>   particular sequence number are discarded.
> 
> That second MUST I think is possible to meet given that one discard all packets
> outside of the current window where one have information if a packet sequence
> number have been forwarded or not. Given that a very late packet beyond the
> amount of state for the flow likely anyway have little utility that is likely
> the right choice. However, I think it needs to be made explicit that this is
> okay.

Yes we need to make sure that when we are tracking sequence numbers, packets outside the window are discarded.

I am not sure how common the re-order option will be. In latency centric applications I suspect that re-order will not happen. I am also concerned about how a high performance implementation would do a re-order, so I suspect that this will only be applied to relatively slow flows that are processed by a classical pure software implementation. In turn I am not sure if we will ever see that in an MPLS network. So whilst the design has capability, I am not sure how profitable it is to drill down into the detail with some operational experience. I don’t think we need to do a lot of hand holding, since those that understand their actual requirement will understand how to do this, or soon work it out, and I so not see any interoperability issues per se with the text as it is.

- Stewart