IETF Logo Mail Archive

Re: [Last-Call] Opsdir last call review of draft-ietf-quic-bit-grease-03

Scott Bradner <sob@sobco.com> Fri, 20 May 2022 11:02 UTC

Return-Path: <sob@sobco.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD2CC14F741; Fri, 20 May 2022 04:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.917
X-Spam-Level:
X-Spam-Status: No, score=-0.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 SVyKxQ7etoEl; Fri, 20 May 2022 04:01:58 -0700 (PDT)
Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id 596A3C14F73F; Fri, 20 May 2022 04:01:58 -0700 (PDT)
Received: from smtpclient.apple (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 57E0D5D4B74; Fri, 20 May 2022 07:01:57 -0400 (EDT)
From: Scott Bradner <sob@sobco.com>
Message-Id: <AB83A30B-69E7-42FE-98EB-21DE69AF816D@sobco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_386C7E07-FFE5-4C8B-8F44-C12A006D0909"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\))
Date: Fri, 20 May 2022 07:01:56 -0400
In-Reply-To: <00923c7f-3478-4397-a832-3e94d702bca0@beta.fastmail.com>
Cc: ops-dir@ietf.org, draft-ietf-quic-bit-grease.all@ietf.org, last-call@ietf.org, quic@ietf.org
To: Martin Thomson <mt@lowentropy.net>
References: <165300608176.45061.8788283452343771333@ietfa.amsl.com> <00923c7f-3478-4397-a832-3e94d702bca0@beta.fastmail.com>
X-Mailer: Apple Mail (2.3696.100.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/ZZaO2lkt7Duz21BCwgdJJ-AI8pQ>
Subject: Re: [Last-Call] Opsdir last call review of draft-ietf-quic-bit-grease-03
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2022 11:02:03 -0000


> On May 20, 2022, at 1:46 AM, Martin Thomson <mt@lowentropy.net> wrote:
> 
> 
>> Section 3
>> 
>> Current:
>> “The grease_quic_bit transport parameter (0x2ab2) can be sent by both
>>   client and server.  The transport parameter is sent with an empty
>>   value; an endpoint that understands this transport parameter MUST
>>   treat receipt of a non-empty value as a connection error of type
>>   TRANSPORT_PARAMETER_ERROR.”
>> 
>> I find the above wording confusing – “ receipt of a non-empty value” of what?
>> (the “grease_quic_bit” or something else?
> 
> I don't see an issue here.  Is it that this is missing the context that transport parameters have values?  That's pretty elementary stuff that I don't think needs to be contextualized.

maybe
The grease_quic_bit transport parameter (0x2ab2) can be sent by both
  client and server.  The transport parameter is sent with an empty
  value; an endpoint that understands this transport parameter MUST
  treat receipt of a non-empty value of the transport parameter as a connection error of type
  TRANSPORT_PARAMETER_ERROR.”

v2.23.0 | Report a Bug | By Email