WG members, On Thu, May 6, 2021 at 7:30 PM David Schinazi <[email protected]> wrote:
> My personal opinion is that once we open the floodgates we can't close > them. More specifically, if someone ships an implementation to production > in a way that they cannot guarantee that it can be updated, then the > version used is now immutable. In practice, that means that if you ship a > client device that uses software updates, because some users do not update, > then that would lock us in. In that regards, I could see a world where: > > 1) Deploying on your server today is OK as long as you can guarantee that > if the protocol changes you'll be able to disable h3 or deploy a fix in > under 14 days > 2) Deploying a client-side experiment today is OK as long as that > experiment will automatically stop after 14 days if the client device stops > hearing confirmation that the protocol is still OK to use > 3) Once -invariants, -transport, -tls, and -recovery have all been > published as RFCs, then deploying everywhere is OK > 4) Lack of Alt-Svc doesn't change points 1-3 > > Thoughts? > Does anyone have any additional thoughts wrt to David's posits? Cheers Lucas
