Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518)

[Christian Huitema <[e-mail]>]

@davidben if I understand correctly, the main issue is then compatibility with the existing TLS implementations. They expect the EOED to be received before the first handshake message. 

For me the simplest way to achieve that without changing the TLS stack would be to carry the EOED data in the handshake packet rather than the 0-RTT packet, and then deliver it to the TLS stack while pretending that it was carried with 0-RTT encryption. The added cost is a new frame type, but then I could remove all the warts about retransmitting 0-RTT data sometimes as 1-RTT and sometimes as 0-RTT.

Even simpler of course would be a TLS API option to "not bother with EOED when running over a datagram transport". That would remove all the EOED warts in the QUIC code. It would add some of them back in the TLS code, but probably at a much lower cost. 

-- 
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/issues/1518#issuecomment-417874787