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

Prohibit acknowledgement of packets with echoed packet numbers #727

Merged
merged 2 commits into from Aug 16, 2017
Merged

Prohibit acknowledgement of packets with echoed packet numbers #727

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7a168f9
Prohibit acknowledgement of packets with echoed packet numbers
martinthomson Aug 14, 2017
fcd10ff
Too many lines
martinthomson Aug 14, 2017
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
12 changes: 12 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -522,6 +522,10 @@ from the triggering client packet. This allows clients some assurance that the
server received the packet and that the Version Negotiation packet was not
carried in a packet with a spoofed source address.

A Version Negotiation packet is never explicitly acknowledged in an ACK frame by
a client. Receiving another Client Initial packet implicitly acknowledges a
Version Negotiation packet.

The payload of the Version Negotiation packet is a list of 32-bit versions which
the server supports, as shown below.

Expand Down Expand Up @@ -595,6 +599,10 @@ The packet number and connection ID fields echo the corresponding fields from
the triggering client packet. This allows a client to verify that the server
received its packet.

A Server Stateless Retry packet is never explicitly acknowledged in an ACK frame
by a client. Receiving another Client Initial packet implicitly acknowledges a
Server Stateless Retry packet.

After receiving a Server Stateless Retry packet, the client uses a new Client
Initial packet containing the next cryptographic handshake message. The client
retains the state of its cryptographic handshake, but discards all transport
Expand Down Expand Up @@ -1927,6 +1935,10 @@ Unlike TCP SACKs, QUIC ACK blocks are irrevocable. Once a packet has
been acknowledged, even if it does not appear in a future ACK frame,
it remains acknowledged.

A client MUST NOT acknowledge Version Negotiation or Server Stateless Retry
packets. These packet types contain packet numbers selected by the client, not
the server.

QUIC ACK frames contain a timestamp section with up to 255 timestamps.
Timestamps enable better congestion control, but are not required for correct
loss recovery, and old timestamps are less valuable, so it is not guaranteed
Expand Down