Re: [tsvwg] Update to Position Statement on ECT(1)

"alex.burr@ealdwulf.org.uk" <alex.burr@ealdwulf.org.uk> Sat, 09 May 2020 01:24 UTC

Return-Path: <alex.burr@ealdwulf.org.uk>
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 605A13A05A7 for <tsvwg@ietfa.amsl.com>; Fri, 8 May 2020 18:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 9uZANVswMnNU for <tsvwg@ietfa.amsl.com>; Fri, 8 May 2020 18:24:32 -0700 (PDT)
Received: from sonic307-3.consmr.mail.bf2.yahoo.com (sonic307-3.consmr.mail.bf2.yahoo.com [74.6.134.42]) (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 51B093A0598 for <tsvwg@ietf.org>; Fri, 8 May 2020 18:24:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1588987470; bh=mpzERh8Cws2TFnLYzjWdZO1fbHvVWHSntf4Ei4s1noI=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=IPOt6NlrAhUVirisFf/DkSh6fv1yUe4tymtOU1OEWoVYOH1IKV0BtQQ9M0vsqTi9NA3JNq8nxiYlcAUW/g6b/Mq2PZ2oBlGgLkpCqVwg1ydwXXaRijVpkJiH5u+eJJe7khLDua/XJ2ARva4V32KlShI4yLYTWAu+xg1d2sOZsFgVNty3eVwB1U9dT6PfMUmYjwxITvzx2lDpBUCigB5O01fzVqbkNBL09E+G+JZURMSQoxrgnZbnQaIg+OW68ykwSSjh5n6suZJfWKt+4FmHtTlTFP2xxF0LtC4k8UsPBuYOgtaxZVwBemtUDvvLisD/BLD/1UKMwW2bL+k2fJkqKg==
X-YMail-OSG: znlpT00VM1kjhvx7NGUAbAPAP5rpu2wiA8.SVUIYx_yUyH1mU38.N5xk9VPWjxF odBshnTcr6XK3Mda9Y2ItzMyX0qwZ4qj.Ljk38IXWEAwOOc8UBjxoVm6UV4ldccJvIqsFC6c7W1R 8SUC4xpIC80DbMAhBxtyZq65P1DBMjV.4eZ1uF_.bfVBqWWaO4FEZvHW8fl9TrMjnBLiaiP_JoW4 0TqGj0hTJI9PCQ8n1dsTIK.mqZeH.8hnprGUPfcDvHhZ5RzRXpHlN7w5Aljdz9UOXoH7750xJMta 164cPGPIT1_zAt_TUOqFUHAwpx0qd6DtMKUIsxoPCaYrWLD8QJ.G938ZpxIkfPsEXg0g5sHAfZ0B FVXb59KMkX5_dCJmDDZorYNfqFZWSP_.p57hJyNprK1L8rGa4LDTdl46byShdQ1pg52A_boKsah9 hyBgcEn9.GptKCs5hGOwhckn4Vxc8odxeKqMjB6VMt7TqenyIr9EzEVELxuWMLaQ4dy6eKsocDDr urMaZ1C.SQ2M03B87DBtZRHzlnjyywGEGhgaJSSXCluHEhrVFMAOd_PUrcPqCZjXbWapyHwquZVi VsS3EiPyWRxDEXv7eN4BbTT7oj0lJx4FVlQeRdqyBYeJQBymLGTMWwf41mlEp0Xy3qScoz_Zvh1W t9rOXJJmZj9CR84GyvE77Co7zGavGU3ryX7aapaghGJruGBV6P5tAEaBO.ieQ5od8LcCqjroT3qv MInbYVFyK3F4MUcbhmbwyhRwIZ73VK_wnN28M43tu9z7pvYJwpd54i.82j07BkDF0k.2SbE7hKZ9 Vp3uSr9Qm7V0mLmH3hpSQSofFttd0atcWOsl5xr_hQi.MWq8QKpmqG2KdP7dyxGiGGv4Pp6TIu.J ES9dCpER6Pk19jIo.bKRvXtF8eJ_boGLQo_bx8HNGLCiFH1dqnNaaRkdphXpKNfX3lFwkcu24oPA 607XfjfiujKkaINOo1vElHhpUXJ5sIBJttHlGLU4O7T.AplaUIVoTnaavr68BOJNRTfL6w1giXp0 aZgsU4jr7IxLUj8Qo34ofufMC5d57AR11I_y6qnuq1gxsP0fQMHQNZuN5iZfOmFNuR5X3quhf4wx pOzb7OyLsPCd76avt_jQZKvRWDWdtJe3CSatmUxckONGBE2lbDHJzjfrDBdyCizbJkcMXMObeaHk yHgf2y4AM2xTpsig2lnGvKnUYOqMO4vYEvJ5rAWQfZrbFaNVAAOa0ghw20dgq6DUHWFyBQMPckBH AvOy_MwKddSxhxhkDEFM7mdVKaz.umfkCTiQcDKgMgzPtJGtemBewdSpT9Xuvp5siHrG.jNNuNKe ZXjuFGNYltoX7oTqz
Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Sat, 9 May 2020 01:24:30 +0000
Date: Sat, 09 May 2020 01:24:28 +0000
From: "alex.burr@ealdwulf.org.uk" <alex.burr@ealdwulf.org.uk>
Reply-To: "alex.burr@ealdwulf.org.uk" <alex.burr@ealdwulf.org.uk>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "Holland, Jake" <jholland@akamai.com>
Message-ID: <567224268.28656.1588987468089@mail.yahoo.com>
In-Reply-To: <DF860A44-5474-4258-BE8F-CEDECCC08114@akamai.com>
References: <BE44EAE9-5CFB-4F5D-85B8-05AFA516C151@akamai.com> <1523713490.286122.1588978733887@mail.yahoo.com> <DF860A44-5474-4258-BE8F-CEDECCC08114@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: WebService/1.1.15904 YMailNorrin Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/FHAbsdqrVSqYSsIu7X61geqz1vI>
Subject: Re: [tsvwg] Update to Position Statement on ECT(1)
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: Sat, 09 May 2020 01:24:36 -0000

Hi Jake,

replies inline (marked [AB]).

On Saturday, May 9, 2020, 1:34:29 AM GMT+1, Holland, Jake <jholland@akamai.com> wrote: 

Hi Alex,

On 5/8/20, 3:59 PM, "alex.burr@ealdwulf.org.uk" <alex.burr@ealdwulf.org.uk> wrote:
> However it occurs to me that the ECT(1) (and CE) could still be used as a classifier in the following way:
> Have the Prague sender premark 50% of packets with CE, in an order known to the receiver (eg, alternating).
> The L4S AQM and the RFC3168 would then only be able to mark different packets, so  the receiver can then determine with good confidence whether any CE marked packet was 'originally' ECT(1), and if so, it must have been marked by a RFC3168 
> AQM. (At this point the sender should revert to RFC3168 and stop sending premarked CE packets).
>
> This has the advantage of over A) that the classification signal is not lost after the first bottleneck. However it has the same problem with tunnels, and I can see some additional issues:

I'm not sure I follow the specifics here--neither a L4S AQM nor a classic
queue would re-mark anything that's CE.  Did you mean that there would be
ECT(0) in a known part of the packet stream that would be used as an active
probe for classic queue-marking?

[AB] Not exactly. The existing L4S scheme mark congestion with an ECT(1) to CE transition. In the scheme C in my previous mail, an L4S AQM would be defined to  mark it instead with the opposite, a CE to ECT(1) transition, while the RFC3168 AQM continues to mark using the ECT(1) to CE transition.

[AB] Hence, the scheme requires 50% of packets to be pre-marked with CE by the sender, since otherwise there are unlikely to be enough CE marked packets to allow the 1/p signal to be sent.  This allows 1/p and RFC3168 signals to be distinguished by the receiver - which is assumed to know which packets were premarked CE -  albeit with some degradation to each. 50% of RFC3168 marks would be unobservable to the receiver initially, but as soon as it observed one, the receiver would signal the sender to stop premarking packets with CE, allowing all marks to be observed. Probably the receiver should count all RFC3168 double until then.  

An ongoing active probe is a potentially interesting idea I haven't seen
considered.  I think there are a lot of potential complications there, but
I can see that it might be possible to get a better signal on presence of a
classic queue at a bottleneck than from a purely heuristic detection algorithm.

[AB] Probing with ECT(0) is mentioned in Bob's paper, I'm afraid I didn't read the test results closely enough to remember if 
it was included in the method tested.

> Although the classification would be preserved across L4S AQMs, conditions of an L4S AQM followed by an RFC3168 AQM (or vice versa) could cause some congestion marks to be "undone". However this could only occur until the RFC3168 AQM was detected. IT woudl not be caused my multiple AQMS of the same type.

Are you imagining an ongoing probe that permanently cuts over to a classic
marking style as soon as a classic queue is detected?

[AB] Yes, except as described above, not using additional ECT(0) packets.

> CE has up till now been a fixed point (no transitions away from CE) so there may be other network elements which are surprised by transitions away from it.

Yes, if something transitions away from CE, it seems incompatible with
RFC 3168 queue markings.  I'm not sure offhand what the pathologies would
look like, but I'd be similarly skeptical it could end well.

[AB] Indeed, I am not able to foresee clearly what difficulties it could encounter.  I mention it largely for the sake of completeness.

> Anyway, hope that is of interest.

Thanks for the comment, I think there's maybe an interesting idea in there,
though I'm not sure I quite grasped how it would work.

[AB] Thanks, hopefully I have made it a bit clearer.

Alex