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

Idempotent is not the standard for 0-RTT #4394

Merged
merged 7 commits into from
Dec 10, 2020
Merged

Idempotent is not the standard for 0-RTT #4394

Changes from 2 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
ba30582
Semicolon
martinthomson Nov 19, 2020
d490ef0
Rewrite replay section
martinthomson Nov 19, 2020
b5ce525
RESET_STREAM and CONNECTION_CLOSE too
martinthomson Nov 19, 2020
c2e040a
they do, not they can
martinthomson Nov 19, 2020
ee55b35
Remove one errant use of idempotent
martinthomson Nov 20, 2020
98239d6
RFC 8470 and HTTP/3 references added
martinthomson Nov 20, 2020
d1870b8
don't use unless requested
martinthomson Dec 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions draft-ietf-quic-tls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,8 @@ TLS provides two basic handshake modes of interest to QUIC:
* A 0-RTT handshake, in which the client uses information it has previously
learned about the server to send Application Data immediately. This
Application Data can be replayed by an attacker so 0-RTT is not suitable for
carrying instructions that might initiate any non-idempotent action.
carrying instructions that might initiate any action that could cause
unwanted effects if replayed.

A simplified TLS handshake with 0-RTT application data is shown in {{tls-full}}.

Expand Down Expand Up @@ -1288,7 +1289,8 @@ that is in use.
An application protocol that uses QUIC MUST include a profile that defines
acceptable use of 0-RTT; otherwise, 0-RTT can only be used to carry QUIC frames
that do not carry application data. For example, a profile for HTTP is
described in {{?HTTP-REPLAY=RFC8740}}.
described in {{?HTTP-REPLAY=RFC8470}} and used for HTTP/3; see Section 10.9 of
{{QUIC-HTTP}}.

Though replaying packets might result in additional connection attempts, the
effect of processing replayed frames that do not carry application data is
Expand Down