Working Group Last Call: QUIC protocol drafts

Re:Working Group Last Call: QUIC protocol drafts by Avamander on Wednesday June 10, 2020 @11:54AM (#23478512)

Hm, I don't see any mention of ESNI (TLS ECH), is there a good reason it isn't recommended/mandated by the standards?

[ Parent | on HN ]

Re:Working Group Last Call: QUIC protocol drafts by tialaramex on Wednesday June 10, 2020 @12:00PM (#23478588)

eSNI isn't finished and time resolutely insists on moving in one direction, so a document which says "Use this thing that will exist in the future" isn't useful today.

[ Parent | on HN ]

Re:Working Group Last Call: QUIC protocol drafts by LunaSea on Wednesday June 10, 2020 @12:20PM (#23478866)

Hasn't it already been implemented in Firefox?

[ Parent | on HN ]

Re:Working Group Last Call: QUIC protocol drafts by dathinab on Wednesday June 10, 2020 @02:44PM (#23480602)

isn't finished => the standard of it isn't finished so implementations might not to change quite a bit over time and might not be compatible with each other

[ Parent | on HN ]

Re:Working Group Last Call: QUIC protocol drafts by detaro on Wednesday June 10, 2020 @12:27PM (#23478941)

there is an implementation in Firefox (although I don't know if it matches the current state of the spec draft) that unsurprisingly is gated behind an about:config flag.

[ Parent | on HN ]

Re:Working Group Last Call: QUIC protocol drafts by rrll22 on Wednesday June 10, 2020 @12:01PM (#23478606)

Currently up to draft-ietf-dnsop-svcb-httpssvc and draft-ietf-tls-esni They're designed more slowly than HTTP3.

[ Parent | on HN ]