Re: [C430] RFC 9000 - Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)

Lynne Bartholomew <lbartholomew@amsl.com> Wed, 26 May 2021 16:47 UTC

Return-Path: <lbartholomew@amsl.com>
X-Original-To: c430@rfc-editor.org
Delivered-To: c430@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 589DBF407D5 for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -198.011
X-Spam-Level:
X-Spam-Status: No, score=-198.011 tagged_above=-999 required=5 tests=[RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=2, SPF_PASS=-0.001, SUBJECT_IN_WHITELIST=-100, URIBL_BLOCKED=0.001, USER_IN_WELCOMELIST=-0.01, USER_IN_WHITELIST=-100] autolearn=no autolearn_force=no
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AoZWgZ7TCGOy for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:03 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) by rfc-editor.org (Postfix) with ESMTPS id 350D4F40752 for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 206DC38A05E for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rc1iA_uMognh for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:15 -0700 (PDT)
Received: from [10.0.0.63] (c-71-198-140-71.hsd1.ca.comcast.net [71.198.140.71]) by c8a.amsl.com (Postfix) with ESMTPSA id 0451838A05D for <c430@rfc-editor.org>; Wed, 26 May 2021 09:47:14 -0700 (PDT)
From: Lynne Bartholomew <lbartholomew@amsl.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 26 May 2021 09:47:13 -0700
References: <RT-Ticket-1196209@icann.org> <RT-Ticket-1188362@icann.org> <161237263486.16375.16046346962390939039@ietfa.amsl.com> <rt-4.4.3-2459-1613104363-271.1188362-37-0@icann.org> <7357872F-30B2-47F5-BCF4-958913894591@amsl.com> <rt-4.4.3-12070-1619736994-745.1196209-37-0@icann.org> <rt-4.4.3-27769-1621353382-424.1196209-37-0@icann.org> <6E148B19-298A-4476-9A6F-8EE93B8F71DA@amsl.com> <6151fe4e-16ec-4585-b238-5bb3fcc5777a@www.fastmail.com> <3F942BA8-F4DB-4272-91BF-6013145818FE@amsl.com> <ef768958-63b8-4ea8-a61f-e579c461661a@www.fastmail.com> <7291f943-51de-456c-b8c6-a453c494725b@www.fastmail.com> <CAEE489E-9C98-4B60-AA45-30FB5DCE0F0B@amsl.com> <9074BE20-FD2A-4C36-99A6-F557F3DFABC6@amsl.com> <4cfba816-3cf8-4619-bf7c-ec8f555910b9@www.fastmail.com> <12AF4BBD-E681-4752-8AB8-53F65D349979@amsl.com> <CACpbDccjpjvdYSjVeVvWrCzP0EftUAy=QhTasA0Em9O30fKXBg@mail.gmail.com> <0C2956E1-E146-4655-8340-449CCAA45D0D@amsl.com> <70F34AC9-C14B-4A4E-9F11-22CC46CC4E32@amsl.com> <53beb18c-e6bb-4292-9dd7-2e1caa7901e0@www.fastmail.com> <AAE92C4B-E4DB-4B77-B6D9-94EEDA89ECBF@amsl.com> <CACpbDccVDCZAcwm=sOV4WkWkAqGWe-LwoFrS-mUPZkLKDddJnw@mail.gmail.com> <a6d08c9c-10ae-47dd-b919-008f2321cbd5@www.fastmail.com>
To: Martin Thomson via C430 <c430@rfc-editor.org>
In-Reply-To: <a6d08c9c-10ae-47dd-b919-008f2321cbd5@www.fastmail.com>
Message-Id: <63F8F483-9817-4FD9-BDB1-3FC7EAE49595@amsl.com>
X-Mailer: Apple Mail (2.3273)
Subject: Re: [C430] RFC 9000 - Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)
X-BeenThere: c430@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <c430.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/c430>, <mailto:c430-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/c430/>
List-Post: <mailto:c430@rfc-editor.org>
List-Help: <mailto:c430-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/c430>, <mailto:c430-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 16:47:07 -0000

Hi, Martin and Jana.

We have made the three updates per your notes below.

We will now move this document forward for publication.

Many thanks for the quick turnaround!

RFC Editor/lb


> On May 25, 2021, at 6:47 PM, Martin Thomson via C430 <c430@rfc-editor.org> wrote:
> 
> OK, Jana and I have had a chat and concluded:
> 
> 1.
> The three ECN counts; see ...
> 
> 2.
> ECN counts are only present when ...
> 
> 3.
> The ECN count fields are:
> 
> (We dropped the word "three" here as it is redundant.)
> 
> 
> On Wed, May 26, 2021, at 11:34, Jana Iyengar via C430 wrote:
>> Thanks for the catch, Lynne!
>> 
>> I agree with Martin, except for the last two corrections. There are 3 
>> fields (ECT0 Count, ECT1 Count, ECN-CE Count), grouped together in the 
>> text as the ECN counts. I don't think we should say ECN Counts field, 
>> since that isn't actually a field... we can say "ECN counts" or "ECN 
>> counts fields", but not "ECN Counts field".
>> 
>>>>> 2.  In Section 19.3.2:  ... ECN Counts are only present ...
>>>> 
>>>> Instead:
>>>> The ECN Counts field is only present ...
>> 
>> I propose changing this to "ECN counts are"
>> 
>>>>> 3.  Just after Figure 27:  The three ECN Counts are: ...
>>>> 
>>>> Instead:
>>>> The three fields in ECN Counts are: ...
>> 
>> I would propose here "The three ECN counts fields are: ..."
>> I'm fine with "The three ECN counts are: ..." as well, but I think 
>> "fields" is appropriate here.
>> 
>> Martin -- WDYT?
>> 
>> - jana
>> -- 
>> C430 mailing list
>> C430@rfc-editor.org <mailto:C430%40rfc-editor.org>
>> https://www.rfc-editor.org/mailman/listinfo/c430
>> 
> -- 
> C430 mailing list
> C430@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/c430
> 

> From: Lynne Bartholomew via C430 <c430@rfc-editor.org>
> Subject: Re: [C430] RFC 9000 - Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)
> Date: May 25, 2021 at 5:28:57 PM PDT
> To: Martin Thomson via C430 <c430@rfc-editor.org>
> 
> Hi, Martin.  Thanks for the quick reply!  And no apology needed -- the issue was on our end.
> 
> We'll wait to hear from Jana before making any updates and moving forward.
> 
> Thanks again!
> 
> RFC Editor/lb
> 
>> On May 25, 2021, at 5:07 PM, Martin Thomson via C430 <c430@rfc-editor.org> wrote:
>> 
>> Thanks Lynne,
>> 
>> Sorry for missing that.
>> 
>> On Wed, May 26, 2021, at 09:48, Lynne Bartholomew via C430 wrote:
>>> Hi, Martin and Jana.
>>> 
>>> We are preparing this document for publication.
>>> 
>>> Apologies, but one of our questions from earlier in the process fell 
>>> through the cracks:
>>> 
>>> ECN count / ECN Count (in text, e.g., "3 ECN counts", "three ECN
>>>  Counts")
>>> 
>>> This document has 22 instances of "ECN count", appearing between 
>>> Section 7 and Appendix A.4.  There are three instances of "ECN Count" 
>>> in text that we suggest changing to "ECN count":
>> 
>> I agree that this is the right answer (consistent with others we've made).
>> 
>>> 1.  At the end of Section 19.3:  ... The three ECN Counts; ...
>> 
>> Yes.
>> 
>>> 2.  In Section 19.3.2:  ... ECN Counts are only present ...
>> 
>> Instead:
>> The ECN Counts field is only present ...
>> 
>>> 3.  Just after Figure 27:  The three ECN Counts are: ...
>> 
>> Instead:
>> The three fields in ECN Counts are: ...
>> 
>> I should get Jana to check my work though.
>> -- 
>> C430 mailing list
>> C430@rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/c430
>> 
> 
> -- 
> C430 mailing list
> C430@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/c430
>