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

require ACKs and allow PADDING in the Server Stateless Retry packet #882

Merged
merged 6 commits into from
Mar 15, 2018
Merged
Changes from all commits
Commits
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
9 changes: 5 additions & 4 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -627,10 +627,11 @@ any version negotiation that occurred (see {{version-negotiation}}). The client
MAY also retain any observed RTT or congestion state that it has accumulated for
the flow, but other transport state MUST be discarded.

The payload of the Retry packet contains a single STREAM frame
on stream 0 with offset 0 containing the server's cryptographic stateless retry
material. It MUST NOT contain any other frames. The next STREAM frame sent by
the server will also start at stream offset 0.
The payload of the Retry packet contains at least two frames. It MUST include a
STREAM frame on stream 0 with offset 0 containing the server's cryptographic
stateless retry material. It MUST also include an ACK frame to acknowledge the
client's Initial packet. It MAY additionally include PADDING frames. The next
STREAM frame sent by the server will also start at stream offset 0.


### Handshake Packet {#packet-handshake}
Expand Down