Re: [quicwg/base-drafts] Remove duplicated CONNECTION_CLOSE rules (#3295)

[Jana Iyengar <[e-mail]>]

janaiyengar commented on this pull request.



> @@ -2489,7 +2483,8 @@ least one of them is processable by the client.  Similarly, a peer might be
 unable to read 1-RTT packets, so an endpoint SHOULD send CONNECTION_CLOSE in
 Handshake and 1-RTT packets prior to confirming the handshake; see Section 4.1.2
 of {{QUIC-TLS}}.  These packets can be coalesced into a single UDP datagram; see
-{{packet-coalesce}}.
+{{packet-coalesce}}.  After the handshake is confirmed, an endpoint MUST send

```suggestion
{{packet-coalesce}}.

After the handshake is confirmed, an endpoint MUST send
```

> @@ -2489,7 +2483,8 @@ least one of them is processable by the client.  Similarly, a peer might be
 unable to read 1-RTT packets, so an endpoint SHOULD send CONNECTION_CLOSE in
 Handshake and 1-RTT packets prior to confirming the handshake; see Section 4.1.2
 of {{QUIC-TLS}}.  These packets can be coalesced into a single UDP datagram; see
-{{packet-coalesce}}.
+{{packet-coalesce}}.  After the handshake is confirmed, an endpoint MUST send

I would also suggest moving this up to the earlier para after the sentence "Generally, this means sending the frame in a packet with the highest level of packet protection to avoid the packet being discarded.". Then, change the beginning of the next sentence to "However, prior to handshake confirmation ...".

-- 
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/pull/3295#pullrequestreview-330279718