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.

Sign up for GitHub

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

Jump to bottom

Clarify Actions on nonzero Reserved Bits #2280

Closed
wants to merge 9 commits into from
Closed

Clarify Actions on nonzero Reserved Bits #2280

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
4226540
Get rid of DoS vulnerability in Reserved Bits
martinduke Dec 31, 2018
4ae9526
whitespace
martinduke Dec 31, 2018
f668691
Addressed MT's issue
martinduke Dec 31, 2018
f780ef4
Update draft-ietf-quic-transport.md
martinthomson Jan 9, 2019
3b36352
Merge branch 'master' into patch-32
martinduke Jan 9, 2019
74da042
Cleaned up after discussion in Tokyo
martinduke Feb 5, 2019
7d3489b
Added more explanatory text
martinduke Feb 5, 2019
d291c75
typos
martinduke Feb 5, 2019
a581cba
Fix failed check
martinduke Feb 5, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3481,7 +3481,7 @@ Reserved Bits (R):
packet types. These bits are protected using header protection (see Section
5.4 of {{QUIC-TLS}}). The value included prior to protection MUST be set to 0.
An endpoint MUST treat receipt of a packet that has a non-zero value for these
bits after removing both packet and header protection as a connection error of
bits, after removing both packet and header protection, as a connection error of
type PROTOCOL_VIOLATION. Discarding such a packet after only removing header
protection can expose the endpoint to attacks (see Section 9.3 of
{{QUIC-TLS}}).
Expand Down Expand Up @@ -3934,7 +3934,7 @@ Reserved Bits (R):
bits are protected using header protection (see Section 5.4 of
{{QUIC-TLS}}). The value included prior to protection MUST be set to 0. An
endpoint MUST treat receipt of a packet that has a non-zero value for these
bits after removing both packet and header protection as a connection error
bits, after removing both packet and header protection, as a connection error
of type PROTOCOL_VIOLATION. Discarding such a packet after only removing
header protection can expose the endpoint to attacks (see Section 9.3 of
{{QUIC-TLS}}).
Expand Down