Re: [quicwg/base-drafts] The number of Connection ID is unbounded to NEW_CONNECTION_ID sender (#2403)

[erickinnear <[e-mail]>]

@kazuho Yeah, I don't think that endpoints should necessarily do that, but I'm not sure we need more text or at least that specific recommendation. The issuer is in control of how much it's willing to give out and how much state it's willing to maintain. A consumer that wants to rotate through CIDs that quickly might try regardless of what we recommend, and if the issuer isn't willing to maintain that much state, then at some point it will stop issuing new ones. 

Since we can no longer retire the last CID, then that just means that the consumer ends up stuck on a single CID. That seems like a reasonable outcome to me. If any new text were necessary, it seems like it would be to expand "only issue how *much* you're willing to maintain" to be "only issue how *much* you're willing to maintain however *often* you're willing to issue it".

In other words, it seems like it could be nice to avoid adding more recommendations for consumers that take into account the tuple as well. Folks should be free to change their CID whenever they want, with the understanding that doing excessive things in any direction (requesting too many now that we have a TP, retiring too often, etc.) is gated upon whatever the issuer is willing to support.  

-- 
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/issues/2403#issuecomment-460412266