quicwg / multipath

In-progress version of draft-ietf-quic-multipath
Other
49 stars 17 forks source link

CID allocation strategy #325

Closed Yanmei-Liu closed 1 month ago

Yanmei-Liu commented 3 months ago

We need to specify CID allocation strategy in case endpoints doesn't have available CIDs with same unused Path ID to initialize a new path.

Also need to take security into consideration.

Comments from PR#292:

marten-seemann 4 days ago

This seems backwards. Connection IDs are issues for paths, not the other way around. Also, if I allow you to open 1 million paths, you're probably wise to not issue me 1 million CIDs.

mirjak commented 2 months ago

What do you want to say here @Yanmei-Liu?

I think it simply the case if you don't have a CIDs for an unused path ID, you can't open a new path. However, the other end might purposefully not provide more path IDs. I think you just have to accept it.

If you have CIDs for an unused path ID from the peer but did not provide CIDs for the the same path ID to your peer, you need to do that before opening the path. #315 discusses that already.

What else do we need? or what else would we even be able to say?

mirjak commented 1 month ago

@Yanmei-Liu can we close this issue and move the discussion to #338 instead?

mirjak commented 1 month ago

Closing please discuss in #338. (Or reopen if that doesn't work)