Enabling QUIC in tip-of-tree

[Dharani Govindan]

Hello Fellow Chrome Developers,

 

QUIC has been enabled in Google Chrome for 90% of users via a multi-year field trial, and default enabled in a number of popular mobile apps including Google Search and YouTube, for several years. As our various blog posts and SIGCOMM 2017 paper have detailed, this has been a huge win for performance and user experience and we are confident that our QUIC support is robust and solid.

 

As a result, we will be changing the way QUIC is enabled in M82. Instead of explicitly enabling QUIC when the network stack is configured, QUIC will be enabled by default. This means that QUIC will be implicitly enabled for embedders who accept the default options. An embedder will need to explicitly disable QUIC if they do not wish to support it. This can be done by setting the "enable_quic" member of URLRequestContextConfig to false.

 

If you have any questions please feel free to contact net...@chromium.org

Thanks

QUIC Team

[Dharani Govindan]

Hello everyone,

Update: This change will be enabled in M83 instead of M82 giving enough time to address all the concerns.

Thanks

Dharani

[Krishna Govind]

+Craig Tumblison & +Ernest Cabrera (gTech POCs), +Chrome Product TPgM , +clank-te & +chrome-te as FYI

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAD9fJvzjSG91cxd0nJ%3DNjByAMYpUrgteevBjbUp-tVNEokY8TA%40mail.gmail.com.

[David Schinazi]

Hi Eric,

To clarify what I meant earlier: the effort discussed in the email that started this thread is about enabling QUIC by default.

Enabling QUIC by default just means that the default config will have a list of supported QUIC versions that isn't empty.

Today, the great majority of Chrome users end up being configured with the supported version list { Q046 }, so that's the version that we're the most likely to embed by default at first.

However, that list isn't static. We already have experiments going with version Q050, and we're hoping to make that the default version in the near future.

We also have concurrent experiments with draft-25 today, and soon draft-27. If those go well, we're hoping to potentially make draft-27 the default version soon thereafter.

So, to answer your question, initially embedders will default to a "Google QUIC" version (Q046 or Q050) but we're hoping to replace that with an "IETF QUIC" version like draft-27 ASAP.

There's no important conceptual difference between "Google QUIC" versions and "IETF QUIC" versions, as both have influenced the other over the course of the past several years, and all of those will be replaced by "IETF QUIC v1" and deprecated once that RFC is published.

David

On Wed, Mar 11, 2020 at 12:45 PM ericlaw via net-dev <net...@chromium.org> wrote:

Howdy, all. 

A few questions from the Microsoft Edge team:

With regard to David's statement: "We are default-enabling QUIC, and that means all versions of QUIC" -- does this encompass all available versions or is the claim just meant to say that on-by-default encompasses both "gQUIC" and some versions of ietfQUIC? 

In particular, we on the Edge team are interested in understanding whether the plan includes enabling IETF Draft25 and Draft27?

With regard to Ryan's specific concern about special case behavior, I've weighed in on the https://crbug.com/1060290 issue.

thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to chromi...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAD9fJvzjSG91cxd0nJ%3DNjByAMYpUrgteevBjbUp-tVNEokY8TA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "net-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/5f9e18f8-3f24-4d59-849a-3fa5a95aa109%40chromium.org.

[David Schinazi]

[ other lists to BCC, keeping net-dev only ]

Hi Brandon,

Our implementation of draft-25 and draft-27 is currently missing some features such as 0-RTT.

I don't expect us to make one of them the default version until we have that implemented, due to the negative performance impact.

I can't commit to specific dates or milestones but I'll share that we are actively working on this.

We want to enable IETF drafts as soon as we can, specifically to allow testing with other providers.

David

On Wed, Mar 11, 2020 at 4:32 PM 'Brandon Maslen' via net-dev <net...@chromium.org> wrote:

Thanks for helping clarify David. Are you able to share your experiment details regarding draft-25 and any plans for draft-27? When I took a look I only saw some small (2-11% buckets) of h3-Q048/49/50 and h3-T050 but didn't find the instances of h3-25 or h3-27 being offered.

With properties like Cloudflare (https://developers.cloudflare.com/http3/intro/release/ - h3-23,24,25) and IIS(http.sys)/OWA (h3-25/27) experimenting with H3 offerings based on the IETF drafts it would be great to better understand the roadmap for these versions and ideally get broader usage outside of users who opt to manually add a version target when launching their browser. Do you have any planned milestones or time frames you plan to enable these in?

Thanks,

Brandon

To unsubscribe from this group and stop receiving emails from it, send an email to net...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/5f9e18f8-3f24-4d59-849a-3fa5a95aa109%40chromium.org.

--
You received this message because you are subscribed to the Google Groups "net-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-dev+u...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/net-dev/914fb090-36c6-4687-98af-844083915c36%40chromium.org.

[Dharani Govindan]

Update: We are about to land the change to enable QUIC by default in M84. If you are interested, you can star this change. 

Thanks!

QUIC Team

On Mon, Mar 9, 2020 at 10:31 AM Dharani Govindan <dha...@google.com> wrote:

[Dharani Govindan]

Update: QUIC is now enabled by default. Please reach out to net...@chromium.org if you are facing any issues.

On Mon, Mar 9, 2020 at 10:31 AM Dharani Govindan <dha...@google.com> wrote: