Re: [quicwg/base-drafts] active_connection_id_limit defaults to 0 (#3197)

[Kazuho Oku <[e-mail]>]

@MikeBishop 
> The implication, of course, is that 0 => infinite, but we don't actually say that anywhere. (This part might be editorial; it omits to say what we all know it means.)
> 
> 1 is also a mostly-invalid value, since you can't avoid exceeding that limit without the peer dropping to zero CIDs in the interim and therefore stalling the connection for an RTT + any recovery time needed.

I am literally not sure if this is the case.

As I've pointed out in https://github.com/quicwg/base-drafts/issues/3200, the normative language suggests that active_connection_id_limit actually means the number of "spare" CIDs that should be available, though the definition of "active connection ID" is defined differently.

_If_ we are to consider the normative language as being correct, it would be totally valid to set active_connection_id_limit to 1 (i.e. I want one spare CID!), or 0 (i.e. I do not want any).

-- 
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/3197#issuecomment-550591900