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 what to do with out-of-order early data #442

Closed
wants to merge 1 commit into from
Closed

Clarify what to do with out-of-order early data #442

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 5 additions & 4 deletions draft-ietf-httpbis-replay.md
View file
Open in desktop
Expand Up @@ -345,11 +345,12 @@ requests, which could result in increased load.

## Out of Order Delivery

In protocols that deliver data out of order (such as QUIC {{HQ}}) early data
can arrive after the handshake completes. This leads to potential ambiguity
about the status of requests and could lead to inconsistent treatment (see
In protocols that deliver data out of order (such as QUIC {{HQ}}) early data can
arrive after the handshake completes. This leads to potential ambiguity about
the status of requests and could lead to inconsistent treatment (see
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I wonder how we ended up with the gratuitous re-flowing. (Different editors using different thresholds for which column to wrap at?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I use both emacs and vim at different times, but both are configured with the same value. ¯\(ツ)/¯

{{be-consistent}}). Implementations MUST either ensure that any early data that
is delivered late is either discarded or consistently identified and processed.
is delivered after the TLS handshake completes is either discarded or
consistently identified as early and processed.


# IANA Considerations
Expand Down