quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
51 stars 18 forks source link

What should an endpoint do if it receives a PATH_CHALLENGE for an path ID that it doesn't have CIDs for? #340

Closed mirjak closed 3 months ago

mirjak commented 4 months ago

This is the discussion from PR #315:

mirjak 2 weeks ago I think the client should only try to open a path if it had send CIDs for that path ID (and the reception has been ack'ed). Then if the server received a path challenges for a path ID it doesn't have a CID for, it should either be an error or it should send a path abandon on another path.

@qdeconinck qdeconinck last week

I think the client should only try to open a path if it had send CIDs for that path ID (and the reception has been ack'ed).

We could be in the situation where the server has sent MP_NEW_CONNECTION_ID frames to the client, and the client wants to open a new path by sending a PATH_CHALLENGE along with a MP_NEW_CONNECTION_ID frame with the associated Path ID.

@mirjak mirjak last week Yes sending it in the same packet is fine as well because than it cannot be lost or reordered separately.

@mirjak mirjak yesterday Actually this issue is not resolved because if you send it in the same packet, it's "just" a matter of processing it the right order. However, otherwise I don't think it's a good idea to save the path challenge for later because then you also have to specify how long to wait.

mirjak commented 3 months ago

addressed by PR #341