Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Section 2.1 (comment 3) #527

Open
LPardue opened this issue Sep 13, 2022 · 1 comment
Open

Section 2.1 (comment 3) #527

LPardue opened this issue Sep 13, 2022 · 1 comment

Comments

@LPardue
Copy link
Member

LPardue commented Sep 13, 2022

Section 2.1: We do not see "version number field" in Section 17.2.1 of RFC 9000. Is "Version field" meant?

Current:
During Version
Negotiation (see Section 17.2.1 of [QUIC-TRANSPORT] and
Section 2.8), the version number field has a special value
(0x00000000)...

If so, should "version number field" be "Version field" in Section 2.8?:

Current:
Use of the version number field for
traffic recognition will therefore behave differently than with these
protocols. Using a particular version number to recognize valid QUIC
traffic is likely to persistently miss a fraction of QUIC flows and
completely fail in the near future. Reliance on the version number
field for the purposes of admission control...

@mirjak
Copy link
Contributor

mirjak commented Sep 19, 2022

Yes, using "Version field" in both sections is more clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants