Re: [tsvwg] ECN encapsulation draft - proposed resolution

Jonathan Morton <chromatix99@gmail.com> Wed, 09 June 2021 19:37 UTC

Return-Path: <chromatix99@gmail.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E34D3A2364 for <tsvwg@ietfa.amsl.com>; Wed, 9 Jun 2021 12:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 I3ByNgIyOEMA for <tsvwg@ietfa.amsl.com>; Wed, 9 Jun 2021 12:37:16 -0700 (PDT)
Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (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 A63E73A231F for <tsvwg@ietf.org>; Wed, 9 Jun 2021 12:37:15 -0700 (PDT)
Received: by mail-lf1-x12c.google.com with SMTP id j20so10516001lfe.8 for <tsvwg@ietf.org>; Wed, 09 Jun 2021 12:37:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oeQEZ/nkgTmnvyu/V9NvluZ9mkC0p4iwjkdussBW7Tw=; b=bZffhSpveRMZ+iszBCa9xwRZSznobUV3oik4212RsYQN/ozqTOYJcknmjPsQSCJ+Fi zt3HteqJmNonGiU3qk3BacocirZSmI4ynaf2enLDChCX8jPx10VpbtHkY01Km0CUT5NX QTI+5nNbN/HQzEzHuE+N9mo5zAmxJiQb0WY9Qz+IXJaS0FbE01xTZq08Y8veSFVZRTqu TQVesfCYIehmZqGE7I3yjrNnx5cI3/SQvn1z7qhDIlcYyYuKw0smKLtXO+QibUp/r3OT CQKDeB2mIWEpqB9DstBq4aJumXKXZ26tCI2SW3svlMbWpHgS8C88OtB3gLtRghKyu37e q5ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oeQEZ/nkgTmnvyu/V9NvluZ9mkC0p4iwjkdussBW7Tw=; b=YhiLH/6kgDI/YRCJEOr8J778c5+Hxa1AY6LQtDRAoutOMgn19IefTkhnOQuVQY1Dx6 9DDrFTsxax6hVlH+2rgHTgVfdQ/UYRrWA4igRjw6+/v7e+EC4cI8vE2qL8yHNJIteod3 KULOxoaK8nRyVsbWHed1mVaZz9Y4OCVwzlLshTTZ0iVZMuUHhPuaN4x1FQHlMcLWOhu9 yJUrCDXGjRcKH424G7BT49yDyO/iI1bWfJyJNGyKgIkOQJSWjFLQdJb4KX16bTADhzH2 Bug6NYhbkq+lys20VOXHwPnTG8efqm1DlLqO7f7huMZauz19+XJ8kQx6Xk3b+KjywYP7 gd6w==
X-Gm-Message-State: AOAM530xwnRLTLbLswrfANIHpOTbp58JAh2tFLQ9XvMfwGDDugAF1yZ1 VR0ArB05rEUl3uuOKCKRckA=
X-Google-Smtp-Source: ABdhPJxi1kVgGbvUE4n/dAZ96P3dfZwx5rOGMpKJcADgg3T/quelb1LDRrqR7s7y+vM7VS7cQF1NeA==
X-Received: by 2002:a05:6512:2096:: with SMTP id t22mr702966lfr.272.1623267432069; Wed, 09 Jun 2021 12:37:12 -0700 (PDT)
Received: from jonathartonsmbp.lan (178-55-194-130.bb.dnainternet.fi. [178.55.194.130]) by smtp.gmail.com with ESMTPSA id s16sm71616ljh.139.2021.06.09.12.37.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jun 2021 12:37:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <AM9PR07MB7313E7797F850B210EC3A799B9369@AM9PR07MB7313.eurprd07.prod.outlook.com>
Date: Wed, 09 Jun 2021 22:37:09 +0300
Cc: Bob Briscoe <ietf@bobbriscoe.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Markku Kojo <kojo@cs.helsinki.fi>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3009F41B-1D79-4B2D-BC16-8F2049EA4976@gmail.com>
References: <MN2PR19MB40454BC50161943BC33AAAD783289@MN2PR19MB4045.namprd19.prod.outlook.com> <43e89761-d168-1eca-20ce-86aa574bd17a@bobbriscoe.net> <de8d355d-08b6-34fb-a6cc-56755c9a11ee@bobbriscoe.net> <MN2PR19MB4045DB9D2C45066AEB0762DB83259@MN2PR19MB4045.namprd19.prod.outlook.com> <alpine.DEB.2.21.2106021717300.4214@hp8x-60.cs.helsinki.fi> <290e1624-fa1e-21d7-95fb-90e284c27dd8@bobbriscoe.net> <C7509065-526C-4712-B6CD-E919910E280E@gmail.com> <AM9PR07MB7313E7797F850B210EC3A799B9369@AM9PR07MB7313.eurprd07.prod.outlook.com>
To: "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/lAh9_9pvfv4DH6ajQAU8l7QRy_E>
Subject: Re: [tsvwg] ECN encapsulation draft - proposed resolution
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2021 19:37:21 -0000

> On 9 Jun, 2021, at 7:07 pm, De Schepper, Koen (Nokia - BE/Antwerp) <koen.de_schepper@nokia-bell-labs.com> wrote:
> 
> So for me following simple algorithms would be ok to use:
> - only mark if the first (even partial) segment of the reassembled packet is marked (ignore marks on any other segments)

This would mean that any mark applied to a segment that covered only the middle or tail of a packet would reliably have no effect.  I firmly disagree with that approach, due to the possibility of accidentally triggering pathological conditions where a long series of marks is lost.

> - apply a random probability on the packet based on the ratio of marked bytes in the packet and full packet size

I can see where you're going with that, but I maintain - based on my analysis a couple of posts ago - that maintaining the number of marked bytes is simply the wrong approach.

The interval *between* marks, measured in either bytes or time, is the important property to preserve; this is actually easier to achieve and is natural to perform statelessly.  If the AQM device can rely on that behaviour, it can be designed to perform byte-mode or time-domain marking to match, which dovetails nicely with all existing transport implementations (whether with high-fidelity or conventional congestion control).

 - Jonathan Morton