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

[Christian Huitema <[e-mail]>]

The TLS spec seems to imply that the End Of Early Data (EOED) message, if required, should be protected and transmitted as 0-RTT data.  I found that when implementing the draft-13 spec, and it was somewhat of a surprise. I understand the willingness to exactly parallel TLS 1.3 behavior of TCP, but it is weird when packets are sent as UDP datagrams.

The weirdest part is probably the retransmission behavior. 0-RTT packets are only acked by 1-RTT packets. Stream frames in 0-RTT packets are resent in 1-RTT packets. For correct behavior, we must guarantee that it is received before the Client Finished message. What are implementers supposed to do? Put a huge wart in the retransmission control?

It would be much simpler to not require an EOED message for Quic. EOED is not really functional, since 0-RTT packets are not processed through the TLS stack. 0-RTT and 1-RTT packets are in the same sequence space, there is no need for a demarcation. It is just one of those hazing things that are imposed on developers.

-- 
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