IETF Logo Mail Archive

Re: An Update about Chrome and IETF QUIC

Jana Iyengar <jri.ietf@gmail.com> Tue, 20 October 2020 17:44 UTC

Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62F8F3A121F for <quic@ietfa.amsl.com>; Tue, 20 Oct 2020 10:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKpFo7hhc5cx for <quic@ietfa.amsl.com>; Tue, 20 Oct 2020 10:44:28 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7436C3A121B for <quic@ietf.org>; Tue, 20 Oct 2020 10:44:28 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id x16so2960402ljh.2 for <quic@ietf.org>; Tue, 20 Oct 2020 10:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n9LKqkefoQgLr54PwdWz1bw2iMxXOq46zfcBocIxbgU=; b=qOjYw7Qic1Px8YQk5UjN9VuueeW7lq1gHAjtlevU2ILwxk/rUH4QiMLXjgsyx/wLQd T6ViXwpJvRTFShC35vhAZwZGTCJkeQBrZqy7/WwSUM43697HCp40NxWapMSFnRZxdpr4 N4iWfmd2c/EpZ/JwAkwfd2uyS8ToFBlSeG4kNUTFdnHpbAnkX5wucjv27aZNctklVjEK vsGQmvJk1q/98UienrixnJgE4xzrFpJa0heAHW4FXoI1BIz4AGZsAnho1Bod6dvZP2Rl TDZjFYdnjczoMk0Kki93XpmM8U2pMfkbIXkHQc6AnORsizDpiItkgIe1ssjk8qnBdHRC unGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n9LKqkefoQgLr54PwdWz1bw2iMxXOq46zfcBocIxbgU=; b=VHTEccVk86UmeM/8eheUeES70v/UGDftU/GKqSv27KHm0BvD9SrlMVuZ3uJfaiFFH2 cPR9rQZWrReQBo8BZ98eMUlhvi7a/sLutw16NfMHjwTkW1D5WH/G+/ezlvEKNVUUWlU1 hHOT0lF6py0u9GaCbytGTHxInUbHvirtXL/1mQ/u6b488mnGlY/oivEZjawIjNdTjcVu osCD2gJbEwKe1KnaX3KDP88gXiFbGbtN11MaIOFwwAfzm2KJ34pH6R125Sa017b1IJ5X FodTD8jxSJwaRui7KylXxt5r52sX4ZOJrbRzFQzYUCnN/TOcp2vCREwPs0NnMYZBhjuu 2zeA==
X-Gm-Message-State: AOAM533d3O4vYtRheYq5DaqvQdmowUzQG466K2Vja/6QE02ZPdfuXLOI V3m5j2v/CGlziiEkSa014vjQdB2yNnd8reDe1GI+v4RC
X-Google-Smtp-Source: ABdhPJy5jkBZ0C26ashvwCvblmQLvJUGvAY+WVt6Ix+mJQTQ6URfCnNJ0v8HbAUMw4txgiNuvVAvWtFVexoRW4b8png=
X-Received: by 2002:a2e:5c83:: with SMTP id q125mr1533211ljb.387.1603215866622; Tue, 20 Oct 2020 10:44:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAPDSy+7jKFSLPiw9=iGijT5E-A+GYSisfaL9-pLbFZQ8NfeAFg@mail.gmail.com> <CAPDSy+4f4K8bMp0zuMOQyc+JOad6OR6moHaPj79-c9JZFazWtQ@mail.gmail.com>
In-Reply-To: <CAPDSy+4f4K8bMp0zuMOQyc+JOad6OR6moHaPj79-c9JZFazWtQ@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 20 Oct 2020 10:44:15 -0700
Message-ID: <CACpbDcfNamb5aHyshm=6nVo7H1KJX5FzKUYmMWadQW7fAs4YNg@mail.gmail.com>
Subject: Re: An Update about Chrome and IETF QUIC
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a76fd05b21dc86c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jGhExUezMHTouVLiJyWfjI-H89c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 17:44:30 -0000

This is excellent news -- thanks for sharing, David!

On Tue, Oct 20, 2020 at 10:40 AM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi everyone,
>
> To follow up on my previous email, I just wanted to let everyone
> know that we've now ramped up h3-29 to over 90% of Chrome
> users. (We always keep a few percent of users running other
> versions of QUIC or TCP to compare performance.)
>
> Cheers,
> David
>
> On Wed, Oct 7, 2020 at 9:49 AM David Schinazi <dschinazi.ietf@gmail.com>
> wrote:
>
>> Hi QUIC WG,
>>
>> We would like to share an important announcement from Chrome:
>>
>> https://blog.chromium.org/2020/10/chrome-is-deploying-http3-and-ietf-quic.html
>>
>> In particular, we'd like to highlight two points of interest to the WG:
>>
>> 1) Chrome now supports IETF QUIC by default (h3-29).
>>
>> 2) Since the subsequent IETF drafts 30 and 31 do not have
>> compatibility-breaking
>> changes, we currently are not planning to change the over-the-wire
>> identifier. What
>> this means is that while we'll keep tracking changes in the IETF
>> specification, we
>> will be deploying them under the h3-29/0xff00001d name. We therefore
>> recommend
>> that servers keep support for h3-29 until the final RFCs are complete if
>> they wish to
>> interoperate with Chrome. However, if the IETF were to make
>> compatibility-breaking
>> changes in a future draft, Chrome will revisit this decision.
>>
>> Full details in the link above.
>>
>> Cheers
>> David
>>
>

v2.23.0 | Report a Bug | By Email