Hi Martin, On Mon, Jan 11, 2021 at 01:40:41PM -0800, Martin Duke wrote: > Ian proposed a radical new plaintext CID algorithm for for quic-lb. I > already merged it into the draft alongside the current one, to make things > clearer. See Section 4.2 of the draft > <https://quicwg.org/load-balancers/draft-ietf-quic-load-balancers.html#name-ecmp-cid-algorithm>. > I suspect this may not be the final result, but this is another one of > those value judgments I'd like input on.
This is the correct link: https://quicwg.org/load-balancers/draft-ietf-quic-load-balancers.html#name-low-config-cid-algorithm > As a practical matter, Ian's proposal is also an easier transition path for > Google's load balancers, and presumably others as well. Their > implementation experience suggests that the memory load is manageable. Well, then it looks like they are going to do it anyway, so you might as well put it into the draft! > *So we have three options*: > 1) Stick with PCID and ditch this. > 2) Replace PCID with this proposal. > 3) Have two standard unencrypted algorithms to capture the tradeoff -- I > would prefer not to complicate things in this way unless there is real > disagreement about how to resolve the tradeoffs. In a bit of synchronicity (may the force be with you!), I was reading the LB I-D just as your email arrived. I vote for option (3): the two PCID can coexist in the document. - Dmitri.
