Re: [quicwg/base-drafts] Add Advice and Rules for CONN_CLOSE in Initial and Handshake (#1786)

[Kazuho Oku <[e-mail]>]

@martinduke My point is that it is IMO meaningless to have a rule specific to processing  aCONNECTION_CLOSE frame when any other frame (or a malformed payload) can cause the handshake to fail.

OTOH, I am not against clarifying how an endpoint should send CONNECTION_CLOSE during the handshake. In fact, it is essential, because we allow the peer to drop it's keys at it's own discretion. Unless we describe the correct way of sending a CONNECTION_CLOSE frame, the peer might fail to decode the packet that contains CONNECTION_CLOSE.

Having that said, the most straightforward rule for sending CONNECTION_CLOSE would be to send the frame in *all* epochs for which the endpoint possesses the write keys. This is basically the contraposition of the receiver being allowed to drop the read keys at any point.

-- 
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/1786#issuecomment-425707186