Re: [tsvwg] [Int-area] 2nd TSVWG WGLC on ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May 2019

Jonathan Morton <> Sat, 27 July 2019 12:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8FD2A1202C4; Sat, 27 Jul 2019 05:50:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EsGZR6bh4VC3; Sat, 27 Jul 2019 05:50:20 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E52371202C0; Sat, 27 Jul 2019 05:50:19 -0700 (PDT)
Received: by with SMTP id a15so55305123qtn.7; Sat, 27 Jul 2019 05:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=76UUIPhatGW8Lzvo0RLq4m6Brn97TbWacvOYskYzqug=; b=cjc8KUsrfaDg4Bh/SFknaqy/D6qft6p3GFQ43kFcdbf14wjIqw5dU9Ec5wAVYAajFS 2JODBJopwc1t64dX0nScUgHqo4mtCUqOkn48vdf6pFyPcLKdpdfLJY1gtewqMAtUEhsO Rm2zW2o3N3H+aprhyj5fnuzCjgakH9c5MTbWth7BKA4tGQAz16yPMNHwQh2n85OaG/++ 2dBYI67gjzhq0lOH9cec/HN7QklMDQcivuXNU3IJxCw7c8gnstcjIGYJtaIaAsaAvnjY dxHQUatTe8nstXDSvjwY2GF9Z6ieaItR7YLbfUZOcVyxqorX3oowWCav0wPJYxBmPnHH Zz/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=76UUIPhatGW8Lzvo0RLq4m6Brn97TbWacvOYskYzqug=; b=CozUML3gJzQTHdwXEir691RIT2dAQhVeTB7IH3AOqXs5SgMpQV7CHqz/6v9qKjk8Lj 0JsmLhPeZHtwoQBVUygossrP/DLqP9Zio3alZeV0ufCqcKLK7Ua/8c5l0ZP1uNZmw3Oj nTWPMH9RzDmsZA1jXoPgisufxXDxiDR6cha2IxknMGgcDNSKsqJ/H9wMsfUfYndLVVxK SVnP21Psj95NG0FCOvYlgi2+8Gr2hO9PNWozfUP6Bo5NqRwgxnFV4OPYCpUIR7M5biid Xoqj5v3v20pPOqs53p0vCb29v2in7d+vBf141nzCpzP6V1JPAspsdPJxVFl1EJLFYTkK xdmw==
X-Gm-Message-State: APjAAAX2MuLm2GIPUI+H5Hx3E23+dgzNY+2y9i1LXGCn8AiRRurlYQZk ryisvhJDkkTXBzxTHquQs0u6aFSqDWk=
X-Google-Smtp-Source: APXvYqwoUTqCmyJ/s2H4F9TJWT0LnTu5/YRLq7blmKQt0Lo4Q02eFaYig7edLSPX0vvfaBOp6kRRzw==
X-Received: by 2002:a0c:f909:: with SMTP id v9mr72116209qvn.83.1564231818622; Sat, 27 Jul 2019 05:50:18 -0700 (PDT)
Received: from jonathartonsmbp.lan ( []) by with ESMTPSA id z1sm28417296qkg.103.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 27 Jul 2019 05:50:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <>
In-Reply-To: <>
Date: Sat, 27 Jul 2019 08:50:15 -0400
Cc: Joe Touch <>, "Black, David" <>, "" <>, tsvwg <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Bob Briscoe <>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <>
Subject: Re: [tsvwg] [Int-area] 2nd TSVWG WGLC on ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May 2019
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 27 Jul 2019 12:50:22 -0000

> On 27 Jul, 2019, at 6:01 am, Bob Briscoe <> wrote:
> Yes, with byte-preserving, as packets are re-assembled the number of marked packets reduces. Counter-intuitively, that's correct, even for compatibility with TCP's single congestion response per RTT.
> I originally suggested the requirement in RFC3168 to preserve the number of marked packets, but it's incorrect. It's not compatible with TCP's single response per RTT (or the response to the proportion of marks of other TCP-Friendly real-time congestion controls).
> This is not a matter of compatibility with just one of SCE or L4S. The logical OR approach is wrong for both, and the byte-preserving approach is correct for both - see previous response to Markku.
> Reasoning: the paramount requirement when reassembling fragments is to reconstruct the marking probability that would have occurred had the packets not been fragmented when the AQM in the tunnel marked them. The logical OR approach increases the marking probability as if congestion was higher, while byte-preserving keeps it constant.

I think you are still thinking in terms of marking *probability*, which is not correct in at least conventional RFC-3168 semantics.  Conventional TCPs are sensitive to the number of RTTs between marks; the DCTCP response function is sensitive to the number of marks per RTT.  Both are *time based* relationships.

Codel, the most deployed AQM, is a *time based* marking function.  Preserving the marking probability while the number of packets decreases would reduce the number of RTTs containing a mark.  The original logical-OR function correctly preserves this property, and only fails when there's a mixture of ECT(0) and ECT(1) marks on fragments for a single packet (which can legitimately happen with SCE but not L4S, ironically enough).  Preserving the number of marked bytes does not preserve the number of marks over time, and therefore does not preserve the intent of the marks applied by the AQM.

That's the logic behind my suggested series of rules.  I carefully held both L4S and SCE requirements in mind, as well as those of RFC-3168, while drafting them.

 - Jonathan Morton