Re: [quicwg/base-drafts] Reset the handshake timer on Retry and VN (#2024)

[Marten Seemann <[e-mail]>]

@ianswett That's a good question. We say 

> Once the Version Negotiation packet is determined to be valid, the client then selects an acceptable protocol version from the list provided by the server. The client then attempts to create a connection using that version. Though the content of the Initial packet the client sends might not change in response to version negotiation, a client MUST increase the packet number it uses on every packet it sends.

I'm not sure why we changed this from initiating a completely new connection (including a new destination connection ID). I assume we want to ensure stable routing, if the server routes Initials based on the connection ID?

For Retry, we say 
> The client responds to a Retry packet with an Initial packet that includes the provided Retry Token to continue connection establishment.
> A client sets the Destination Connection ID field of this Initial packet to the value from the Source Connection ID in the Retry packet. Changing Destination Connection ID also results in a change to the keys used to protect the Initial packet. It also sets the Token field to the token provided in the Retry. The client MUST NOT change the Source Connection ID because the server could include the connection ID as part of its token validation logic

I can't find anything about resetting all connection state (except connection IDs and the packet number, and the RTT estimate) in the transport document. I think this is where this belongs, and this would include all state accumulated for recovery.

-- 
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/pull/2024#issuecomment-440527254