Re: [quicwg/base-drafts] Remove the explicit packet number gap in favor of one computed (#496)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> @@ -1296,6 +1291,22 @@ connection ID, it should expect packets on the new connection ID to start at 18.
 A packet with the new connection ID and a packet number of 17 is discarded as
 being in error.
 
+#### Packet Number Gap
+
+In order to avoid linkage, the packet number gap MUST be externally
+indistinguishable from random. The packet number gap for a connection
+ID with sequence number is computed by encoding the sequence number
+as a 32-bit integer in big-endian format, and then computing:
+
+~~~
+Gap = HKDF-Expand-Label(packet_number_secret,
+                        "QUIC packet sequence gap", sequence, 4)

I don't think you want that.  The API we agreed on previously was that TLS provides an exporter and the transport uses it.  If you want this to be in TLS, then we end up with a much tighter coupling than you would like.  (Me, I don't care, I don't see any point in disentangling these two parts, but we did have consensus to separate them.)

-- 
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/496#discussion_r114681126