Re: [quicwg/base-drafts] Stronger migration handshake (#2370)

[Kazuho Oku <[e-mail]>]

kazuho commented on this pull request.



>  endpoints retaining a stable address for the duration of the handshake.
+An endpoint MUST NOT initiate connection migration before the handshake is
+finished for it and its peer and the endpoint has 1-RTT keys. This means
+that the server MUST NOT initiate connection migration before it has
+received at least one 1-RTT data from the client, and the client 
+MUST NOT initiate connection migration before receiving 
+acknowledgement by the server of at least one of its
+1-RTT messages.

@huitema 
> I really don't like the CRYPTO frames reference. There is no FIN mark on the crypto stream, and the QUIC engine proper does not know when "all crypto frames" have been received.  I was careful to use signals that the transport stack understand: obtaining keys, receiving packets, etc.

I am not sure if I agree with the observation. The requirement (i.e. "has both received and acknowledged all CRYPTO frames for that encryption level and when all CRYPTO frames for that encryption level have been acknowledged by its peer") can be implement as checking that 1-RTT read key is available and that the send buffer of CRYPTO frames in Handshake epoch is empty.

Anyways, I think using different events for starting the handshake key drop timer and permitting migration is an unnecessary complexity.

-- 
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/2370#discussion_r251274234