Re: [quicwg/base-drafts] First byte changes (#2006)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



>  
-: The fourth bit (0x10) of byte 0 is set to 1.
+: The next two bits (those with a mask of 0x18) of byte 0 are reserved.  These
+  bits are protected using header protection (see Section 5.4 of
+  {{QUIC-TLS}}).  The value included prior to protection MUST be set to 0.  An

@igorlord I think @marten-seemann is correct here.

If we say that the bits on the wire is hard-coded to zero, the bits face ossification.
If we say that the bits can be anything, it could be used by an endpoint for any purpose without peer's consent (which is a privacy risk as Marten points out).

By saying that the bits will be set to zero (before encryption) and then encrypted, we prevent ossification and also require peer's consent when an endpoint want to use the bit for other purposes.

-- 
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/2006#discussion_r234806010