Re: [quicwg/base-drafts] Endpoint MAY discard CIDs (#1992)

[Marten Seemann <[e-mail]>]

marten-seemann requested changes on this pull request.

Issuing too many connection IDs doesn't hurt in the case where the server uses a deterministic routing scheme to associate connection IDs to connections (except for the obviously wasted bandwidth). However, there's a different approach (which I chose in my implementation). I'm keeping a mapping connection ID => connection around for every single connection ID I issue. This allows me to use very short (4 bytes) connection IDs. If an implementation like this issues too many connection IDs, and the peer starts dropping them, it will have to keep state for every dropped connection ID until the end of the connection.

This is trivially solved if each peer declares the number of connection IDs it is willing to store in a transport parameter. Based on @dtikhonov's thread on the mailing list, I was planning to contribute a PR for this.



-- 
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/1992#pullrequestreview-173829561