Re: [quicwg/base-drafts] Compatible version upgrade (#1901)

[David Schinazi <[e-mail]>]

I agree with @martinduke. Making downgrade prevention more secure is important to QUICv1. However, I'm not yet convinced that "compatible version upgrade" makes sense as part of QUICv1. I think there are two use-cases for it:
1) Upgrade from QUICv1-draft to QUICv1-RFC
In this scenario we can safely assume that the relevant QUIC versions are compatible. However, we can also safely assume that the only deployments of QUIC will be HTTP. Therefore we can rely on Alt-Svc, and have no strong motivation for this mechanism.
2) Upgrade from QUICv1 to QUICv2
In this scenario we're not sure the versions will be compatible, and we also don't have a need to add this to QUICv1. If during design of QUICv2 we want this feature (and I personally believe we will), then we can add a QUICv1 extension indicating support for seamless upgrade to v2, and have browsers try v1 first.

To be clear, I really like this solution - I think it's elegant and efficient. However, it also adds complexity - do we really need it in v1?

-- 
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/1901#issuecomment-434919277