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

Allow most frames in 0-RTT #2355

Merged
merged 13 commits into from Mar 11, 2019
7 changes: 7 additions & 0 deletions draft-ietf-quic-http.md
Expand Up @@ -1482,6 +1482,13 @@ The use of 0-RTT with HTTP/3 creates an exposure to replay attack. The
anti-replay mitigations in {{!HTTP-REPLAY=RFC8470}} MUST be applied when using
HTTP/3 with 0-RTT.

Certain HTTP implementations use the client address for logging or
access-control purposes. Since a QUIC client's address might change during a
connection (and future versions might support simultaneous use of multiple
addresses), such implementations will need to either actively retrieve the
client's current address or addresses when they are relevant or explicitly
accept that the original address might change.


# IANA Considerations

Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.