Secure

QUIC is always secure. There is no clear-text version of the protocol so tonegotiate a QUIC connection means doing cryptography and security with TLS1.3. As mentioned above, this prevents ossification as well as other sorts ofblocks and special treatments, as well as making sure QUIC has all the secureproperties of HTTPS that web users have come to expect and want.

There are only a few initial handshake packets that are sent in the clearbefore the encryption protocols have been negotiated.