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

Some minor editorial tweaks for s6.1. #321

Merged
merged 1 commit into from Feb 17, 2017
Merged

Some minor editorial tweaks for s6.1. #321

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
10 changes: 5 additions & 5 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -644,10 +644,10 @@ When the server receives a packet from a client with the VERSION flag set, it
compares the client's version to the versions it supports.

If the version selected by the client is not acceptable to the server, the
server discards the incoming packet and responds with a version negotiation
server discards the incoming packet and responds with a Version Negotiation
packet ({{version-negotiation-packet}}). This includes the VERSION flag and a
list of versions that the server will accept. A server MUST send a version
negotiation packet for every packet that it receives with an unacceptable
list of versions that the server will accept. A server MUST send a Version
Negotiation packet for every packet that it receives with an unacceptable
version.

If the packet contains a version that is acceptable to the server, the server
Expand All @@ -666,10 +666,10 @@ set and MUST include the new negotiated protocol version.
The client MUST set the VERSION flag and include its selected version on all
packets until it has 1-RTT keys and it has received a packet from the server
that does not have the VERSION flag set. With TLS, this means that unprotected
packets and 0-RTT protected packets all include a version field.
packets and 0-RTT protected packets all include a VERSION flag.
Copy link
Contributor

Choose a reason for hiding this comment

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

The earlier form was actually more accurate. There's a VERSION flag that indicates (i) the presence of a version field in packets from client to server, and (ii) the packet is a version negotiation packet when the packet is server -> client.


A client MUST NOT change the version it uses unless it is in response to a
version negotiation packet from the server. Once a client receives a packet
Version Negotiation packet from the server. Once a client receives a packet
from the server with the VERSION flag unset, it MUST ignore the flag in
subsequently received packets.

Expand Down