Re: [quicwg/base-drafts] Rewrite text about Version Negotiation (#1039)

[martinduke <[e-mail]>]

martinduke commented on this pull request.



> +Clients SHOULD discard any packet that cannot be associated with an existing
+connection.  Discarded packets MAY be logged for diagnostic or security
+purposes.
+
+If a server receives a packet not associated with an existing connection, it
+executes the following steps, in order:
+
+1. The server MUST check if the packet uses a short form header, or is not
+long enough for the size required for the first packet of any QUIC version
+that the server supports. See {{packet-size}} for the definition of packet size
+and the minimum size of the first packet in this version of QUIC. If either
+condition is true, the packet cannot create a new connection. In this case, the
+server MUST either buffer the packet (see {{handshake-buffer}}), send a
+stateless reset ({{stateless-reset}}), or silently drop it.
+
+2. Otherwise, the server checks the version field in the long header. If the

I actually implemented this in the order listed. For writing this, I found other arrangements to have more cumbersome conditions to express in English:
1) if (long header) && (big enough) && (version not OK)
send VN
2) if (long header) && (big enough) && (version OK) - i.e. I have to write out the first two conditions twice consecutively, or nest the paragraphs somehow.
deliver payload to TLS, etc.
3) Drop/Buffer

but obviously this is a purely wordsmithing concern.


-- 
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/1039#discussion_r161669013