[quicwg/base-drafts] QUIC Transport: Reading NiTs - set 1 (#3720)

Gorry Fairhurst <notifications@github.com> Thu, 04 June 2020 11:15 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C43E3A0870 for <quic-issues@ietfa.amsl.com>; Thu, 4 Jun 2020 04:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.101
X-Spam-Level:
X-Spam-Status: No, score=-3.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 IMcyvpnUGzTv for <quic-issues@ietfa.amsl.com>; Thu, 4 Jun 2020 04:15:55 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC2203A0859 for <quic-issues@ietf.org>; Thu, 4 Jun 2020 04:15:55 -0700 (PDT)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [10.52.16.66]) by smtp.github.com (Postfix) with ESMTP id 282881210C3 for <quic-issues@ietf.org>; Thu, 4 Jun 2020 04:15:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1591269355; bh=Ejo1lXxnV6RhB4kmjBC3Lysog2cC9Bqh4ukxBq9h4SU=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=qUfRkxxuoLg7SpA3abmvcJAua+Y7Q4Z/h4J/DDwvD06xUq0U/JkZYy2ufv/AE8un6 Ti4S0020rS9cb2cdeOdA7sGnnfo3f+V0b2pBI5bJ0afKMJ0KfnM5BsvJb3o8d9Lecd nlskkdQIqeaj/WCSZrx84iTw4oDkH0LFzrIiQzmc=
Date: Thu, 04 Jun 2020 04:15:54 -0700
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2WSX6DK4SZYWBB2U544S4OVEVBNHHCLGBYCI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3720@github.com>
Subject: [quicwg/base-drafts] QUIC Transport: Reading NiTs - set 1 (#3720)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ed8d7ead748d_6f853fcf038cd9643341b8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/k96dksxdM4BMVuWirrJcFVRaXnI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 11:15:57 -0000

The following NiTs are from a careful read of QUIC transport. I expect all are editorial and that the editors may be able to perform suitable changes to improve reading.

- to which
/deciding which streams to dedicate resources to/deciding the stream to which resources should be dedicated/

- that
/operations which an application MUST/operations that an application MUST/

- avoid sides … causes.. 
/because the opening of either send or receive sides causes the stream to open in both directions./because the opening of either the send or receive side causes the stream to be open in both directions./

- add /a/
/The sending part of stream/The sending part of a stream/

- Other sentences include /frame/
/is created when the first STREAM, STREAM_DATA_BLOCKED, or RESET_STREAM is received for that stream./is created when the first STREAM, STREAM_DATA_BLOCKED, or RESET_STREAM frame is received for that stream./

- This did not parse for me, is this better?
- /A sender MUST NOT send STREAM or STREAM_DATA_BLOCKED after sending a RESET_STREAM; that is, in the terminal states and in the "Reset Sent" state. /A sender MUST NOT send a STREAM or STREAM_DATA_BLOCKED frame that is in the terminal states and in the "Reset Sent" state (after sending a RESET_STREAM frame)./

- is this /can/MAY/  - because MUST is used for illegal frames?
/A receiver can send STOP_SENDING in any state /

- include word frame to be consistent with other text?
/STREAM frames received after sending STOP_SENDING are/STREAM frames received after sending a STOP_SENDING frame are/

- include word frame to be consistent with other text?
/can terminate one direction by sending a RESET_STREAM/can terminate one direction by sending a RESET_STREAM frame/

- /which/that/,  add /to be/
/method which will allow packets with that connection ID to be routed back to the endpoint and identified by the endpoint upon receipt/method that allows packets with that connection ID to be routed back to the endpoint and to be identified by the endpoint upon receipt/

- rate control?
/Servers MAY rate control these packets to avoid storms of Version Negotiation packets./
- perhaps /rate limit/ or /control the rate of/

The words appear to depend on the wrong previous sentence:
/Servers MAY rate control these packets to avoid storms of Version Negotiation packets. Otherwise, servers MUST drop packets that specify unsupported versions./
- appear to be an “otherwise” to rate control, but is this actually intended as an “otherwise” to “SHOULD send a Version Negotiation packet”?

-/which/that/, 
/There are certain operations which an application MUST/There are certain operations that an application MUST/

- or any number more permitted by initial cwnd and initial_max_stream_data_uni, the current text needs to not suggest this is unlimited!
/As a result, this handshake may consist of as few as 4 UDP datagrams, or any number more./

- are required to comply with implied …
/Endpoints are required to comply with the restrictions implied by these parameters;/
- change /implied/ to /defined/ or perhaps remove the word?

- is this the same, I wasn’t sure what the original ordering was?
/Implementations MUST support buffering at least 4096 bytes of data received in CRYPTO frames out of order. /Implementations MUST support buffering at least 4096 bytes of data received in out of order CRYPTO frames./ 

- awkward multiple use of /used/? perhaps:
/Address validation is used by QUIC to avoid being used for a traffic amplification attack./Address validation in QUIC avoids QUIC being used for a traffic amplification attack./

- I did not understand this, please add something to explain:
- /Sending padded datagrams ensures that the server is not overly constrained by the amplification restriction./

- please be careful about the layer at which s size is expressed.
/in a UDP datagram of at least 1200 bytes/
- Is this actually a UDP datagram or size 1200 or a payload of 1200B (as previously stated in the section) or something different?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3720