Re: [tsvwg] New rev of docsis-q-protection draft related to L4S

Bob Briscoe <ietf@bobbriscoe.net> Wed, 11 May 2022 21:37 UTC

Return-Path: <ietf@bobbriscoe.net>
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 D076BC15E405 for <tsvwg@ietfa.amsl.com>; Wed, 11 May 2022 14:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.954
X-Spam-Level:
X-Spam-Status: No, score=-3.954 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_BLOCKED=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=bobbriscoe.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TVyip5eHs8e1 for <tsvwg@ietfa.amsl.com>; Wed, 11 May 2022 14:37:13 -0700 (PDT)
Received: from mail-ssdrsserver2.hostinginterface.eu (mail-ssdrsserver2.hostinginterface.eu [185.185.85.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCE7FC1595E5 for <tsvwg@ietf.org>; Wed, 11 May 2022 14:37:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=In-Reply-To:References:To:From:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To:Cc: Content-Transfer-Encoding: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=xgbOwI7J5IOIzHgLz3tX+X1KaaG9iiG8wfjCcl8pY18=; b=7vPxSzEF0b36KHc2OmWN/aSBas 9Qvux49syPbo+3hgICMRCliMevXfsNwn7x6Cg1ojuyfLnKHoRHurHrIOKwDTbMdb3KbhUo/jAte3O k7ANY6RXwJbyv3mIuzSqM8G8ZOibcgyiCpaFqsuCI8DDXmRB8v+Ln2HWYn5NXeDijVcsnbG4Y6geU czoh0EtGvucYcltwJjRia7QxgBQvq1ZLizz4Cw1oypaBPlXM3LutO2uTnWoK5OxHX9Ss2rbetdg7L Z6rQ+qXelMlf7lYlC524CY16CCUz5FKMz5N1Z5aDiW0IzYdhOfDxvWNF38SbI5yQD8joMRWm0uJpr ti00JdLg==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:42046 helo=[192.168.1.11]) by ssdrsserver2.hostinginterface.eu with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1nou1E-0005Gj-Ku for tsvwg@ietf.org; Wed, 11 May 2022 22:37:12 +0100
Content-Type: multipart/alternative; boundary="------------7xmwV75WxH59c05EVx0boz4o"
Message-ID: <fa3e4344-9afb-d768-2383-8d2dc085b360@bobbriscoe.net>
Date: Wed, 11 May 2022 22:37:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: en-GB
From: Bob Briscoe <ietf@bobbriscoe.net>
To: tsvwg IETF list <tsvwg@ietf.org>
References: <45cf3e38-60e1-1c01-bec0-6386d12acf05@bobbriscoe.net> <6d3d5b06-9a2e-d384-b8cc-bbb3e0563e79@bobbriscoe.net>
In-Reply-To: <6d3d5b06-9a2e-d384-b8cc-bbb3e0563e79@bobbriscoe.net>
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hostinginterface.eu
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: ssdrsserver2.hostinginterface.eu: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hostinginterface.eu: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/lp-TsvkX8pqcFI1hwXfm4YRgoek>
Subject: Re: [tsvwg] New rev of docsis-q-protection draft related to L4S
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.34
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, 11 May 2022 21:37:17 -0000

tsvwg,

This document is adjacent to the L4S work in TSVWG.
Apologies, another rev with 3 more nits fixed:
Pls see diff here if interested:
https://datatracker.ietf.org/doc/draft-briscoe-docsis-q-protection/history/
(A missing abbreviation expansion, excess white space removed and a 
full-stop where a comma was intended.)


Bob

On 10/05/2022 20:48, Bob Briscoe wrote:
> tsvwg,
>
> This document is adjacent to the L4S work in TSVWG.
> A new rev with a couple of minor edits has just been posted.
> See links and explanation of changes below, if interested.
>
>
> Bob
>
> -------- Forwarded Message --------
> Subject: 	Re: Martin Duke's Yes on 
> conflict-review-briscoe-docsis-q-protection-00: (with COMMENT)
> Date: 	Tue, 10 May 2022 20:45:21 +0100
> From: 	Bob Briscoe <ietf@bobbriscoe.net>
> To: 	Martin Duke <martin.h.duke@gmail.com>, Eliot Lear 
> <rfc-ise@rfc-editor.org>
> CC: 	draft-briscoe-docsis-q-protection@ietf.org
>
>
>
> Martin, Eliot,
>
> You may have seen the text I proposed to resolve your comment below 
> requesting a more understandable definition of congestion-rate.
> At the request of Eliot, as ISE, I've now posted a new rev containing 
> that text.
> https://datatracker.ietf.org/doc/html/draft-briscoe-docsis-q-protection-04
>
> The diff is here:
> https://www.ietf.org/rfcdiff?url2=draft-briscoe-docsis-q-protection-04.txt
> I also corrected a nit I noticed in the abstract (I'd added a 4th item 
> to the list in the last sentence without moving the 'and' before the 
> 3rd item).
>
>
> Bob
>
> On 08/04/2022 22:05, Martin Duke via Datatracker wrote:
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/conflict-review-briscoe-docsis-q-protection/
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> This document is adjacent to the L4S work in TSVWG.
>>
>> One nit:
>> In (1.2), a definition refers to "marking all the packet's bytes." 
>> I'm not sure
>> what the authors mean; perhaps s/bytes/ECN bits?
>>
>> Reviewing the pseudocode in detail was not necessary for the conflict 
>> review,
>> and I did not do so.
>>
>>
>>
>
> -- 
> ________________________________________________________________
> Bob Briscoehttp://bobbriscoe.net/
>

-- 
________________________________________________________________
Bob Briscoehttp://bobbriscoe.net/