News for hackers. Stuff that matters.

A comment on The Maturing of QUIC.

Re:The Maturing of QUIC by sempron64 on Monday November 11, 2019 @12:45PM (#21506878)
Does the QUIC proposal do anything to address encrypting SNI?
[ Parent | on HN ]
Re:The Maturing of QUIC by rrll22 on Monday November 11, 2019 @01:11PM (#21507150)
> HTTP/3 relies on QUIC as the underlying transport. The QUIC version

> being used MUST use TLS version 1.3 or greater as its handshake

> protocol. HTTP/3 clients MUST indicate the target domain name during

> the TLS handshake. This may be done using the Server Name Indication

> (SNI) [RFC6066] extension to TLS or using some other mechanism.

So if TLS 2.0 starts using ESNI (either draft-ietf-tls-esni or draft-ietf-tls-sni-encryption) QUIC will benefit from that too. Otherwise, QUIC is neutral.

[ Parent | on HN ]
Re:The Maturing of QUIC by jedisct1 on Monday November 11, 2019 @08:03PM (#21510548)
No.
[ Parent | on HN ]