Re: [quicwg/base-drafts] Compatible version upgrade (#1901)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



> -
-Version negotiation packets have no cryptographic protection. The result of the
-negotiation MUST be revalidated as part of the cryptographic handshake (see
-{{version-validation}}).
+Version Negotiation packet from the server, or if the server picks a different,
+but compatible version (see {{version-upgrade}}).  Once a client receives a
+packet from the server which is not a Version Negotiation packet, it MUST
+discard other Version Negotiation packets on the same connection.  Similarly, a
+client MUST ignore a Version Negotiation packet if it has already received and
+acted on a Version Negotiation packet.
+
+A client MAY attempt 0-RTT after receiving a Version Negotiation packet.
+
+The format of the packet that a client sends might be different in the new
+version.  In this case, the client generates a new packet that conforms to the
+selected version.  Though different versions might convey information about

Aren't we requiring the client to always regenerate a packet, now that `unsupported_versions` change from an empty list to a non-empty list when receiving a VN?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/1901#pullrequestreview-168654354