Re: [tsvwg] Review comments on a careful read of the L4S ID

Tom Henderson <tomh@tomh.org> Thu, 06 May 2021 23:53 UTC

Return-Path: <tomh@tomh.org>
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 B4A473A11C4 for <tsvwg@ietfa.amsl.com>; Thu, 6 May 2021 16:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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=tomh.org
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 BbhHiJm3mFdE for <tsvwg@ietfa.amsl.com>; Thu, 6 May 2021 16:53:42 -0700 (PDT)
Received: from gateway32.websitewelcome.com (gateway32.websitewelcome.com [192.185.145.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D94C3A11BF for <tsvwg@ietf.org>; Thu, 6 May 2021 16:53:41 -0700 (PDT)
Received: from cm11.websitewelcome.com (cm11.websitewelcome.com [100.42.49.5]) by gateway32.websitewelcome.com (Postfix) with ESMTP id 63340150D85 for <tsvwg@ietf.org>; Thu, 6 May 2021 18:53:41 -0500 (CDT)
Received: from box5867.bluehost.com ([162.241.24.113]) by cmsmtp with SMTP id enoLlOPD0PkftenoLlQ0w9; Thu, 06 May 2021 18:53:41 -0500
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tomh.org; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version: Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=p2hb92RXSnEi7qwMUdJx0OKZfc3wyOeAEd7JlkJ4Oo8=; b=oSyrHhtQQxFYbHPTLiwAEtk6VV P8K+f0gL3Wkm5aoRtbxY86nkWvLrN0Dl/gipVJT627/H1u3r7OA3FQVg145HHL9Cy8kduojv9c/Ls m084VQZvlsegzyP60UaCi1Ly3H2vlhukJzr80PDG5DDkwGwJLpNZp6OBSVeGYMxFYrBsGY9uL2hq1 tQxrVKfJOrU4zUHyl1gqGhFUnL1TQUU12LhoS7/HIiT6nbZl8FeONgqUNQmtjev2XdM2hjT6eo1ZE TiXlPJMViCmF2vcUHif2TFxCJbx29DShBwEgHzGviyHcRwOa48P1ilvU6xcVGnda+msF4kpWapAke xXwJ+Rzw==;
Received: from c-73-35-161-107.hsd1.wa.comcast.net ([73.35.161.107]:59274 helo=[192.168.168.110]) by box5867.bluehost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <tomh@tomh.org>) id 1lenoL-000U1F-1D; Thu, 06 May 2021 17:53:41 -0600
To: "Black, David" <David.Black@dell.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <634676ca-272d-d616-c352-b38446cf7aab@erg.abdn.ac.uk> <a97fa9fd-3721-af32-a486-7c966d7d108c@tomh.org> <MN2PR19MB40458998C271D5227886866183589@MN2PR19MB4045.namprd19.prod.outlook.com>
From: Tom Henderson <tomh@tomh.org>
Message-ID: <8b19a681-c9ad-32af-3995-519fcdc5c606@tomh.org>
Date: Thu, 06 May 2021 16:53:39 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <MN2PR19MB40458998C271D5227886866183589@MN2PR19MB4045.namprd19.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box5867.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tomh.org
X-BWhitelist: no
X-Source-IP: 73.35.161.107
X-Source-L: No
X-Exim-ID: 1lenoL-000U1F-1D
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: c-73-35-161-107.hsd1.wa.comcast.net ([192.168.168.110]) [73.35.161.107]:59274
X-Source-Auth: tomhorg
X-Email-Count: 3
X-Source-Cap: dG9taG9yZzt0b21ob3JnO2JveDU4NjcuYmx1ZWhvc3QuY29t
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/thvgh403O0SlA9EYE_B5YCsLUBg>
Subject: Re: [tsvwg] Review comments on a careful read of the L4S ID
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: Thu, 06 May 2021 23:53:47 -0000

On 5/6/21 1:30 PM, Black, David wrote:
> Tom,
> 
> I'm the source of pushback here.  In my view, L4S is an interesting mix, as the L4S ID draft does not define a complete protocol - rather, it specifies the ECN marking mechanism and places requirements on the endpoint congestion control response without specifying that response in detail (e.g., to implement TCP Prague congestion control based on L4S, one also needs to also go look at a TCP Prague spec).
> 
> I'd be happy with "mechanism" or "functionality" but I don't see a fully implementable "protocol" here.  What do you think?

David,
While I agree that congestion control is not specified in detail, the 
title doesn't currently claim that it does.  It seems to me that 
sections 4 and 5 define the protocol rules for the use of ECN.  My 
earlier email suggested what more I thought could be included in those 
sections, but I'm not sure whether the authors intend to pick up those 
comments.

- Tom