You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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...
The text was updated successfully, but these errors were encountered: