Re: [quicwg/base-drafts] Early CONNECTION_CLOSE fixes (#3440)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.

LGTM modulo the editorial concern below (sorry to report things one by one).

>  
-Some frames are prohibited in different encryption levels, others cannot be
-sent. The rules here generalize those of TLS, in that frames associated with
-establishing the connection can usually appear at any encryption level, whereas
-those associated with transferring data can only appear in the 0-RTT and 1-RTT
-encryption levels:
+Some frames are prohibited in different packet number spaces. The rules here
+generalize those of TLS, in that frames associated with establishing the
+connection can usually appear in packets in any packet number space, whereas
+those associated with transferring data can only appear in the application
+packet number space:

Looking at [section 12.3 of the transport draft](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#section-12.3), I think the term we use is "application data (packet number) space"?

This comment applies to "application packet number space" used elsewhere in this PR too.

-- 
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/3440#pullrequestreview-368453839