IETF Logo Mail Archive

Re: An Update about Chrome and IETF QUIC

Martin Duke <martin.h.duke@gmail.com> Wed, 07 October 2020 21:42 UTC

Return-Path: <martin.h.duke@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 A34B03A1412 for <quic@ietfa.amsl.com>; Wed, 7 Oct 2020 14:42:27 -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 f-J-BHqUe3Mz for <quic@ietfa.amsl.com>; Wed, 7 Oct 2020 14:42:23 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 1DCDD3A10CE for <quic@ietf.org>; Wed, 7 Oct 2020 14:42:23 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id d20so4086010iop.10 for <quic@ietf.org>; Wed, 07 Oct 2020 14:42:23 -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=QgdDTs8JR60o1VFUDRZGjePKJ3q/Ky9PQi7hYaeiEdc=; b=r0Avwy4gcMaK7dNBZ9Lhds+XgB0ZybixSWOSFSVzxtz6EAg0oDgBLDKRKfx4P80ZSr vnRRRbsw5ZnSaeEiFoH/yx0AQb5FC5xJ2tYfKvspNBYMjmJNNuSx3PCuXZIIWjBZm8bS U/y0aDV6PcKpcDGy3/f1MVX9Ytjr6z+uIJ4ckZqxoxKU5zvJZSFk7jNzlXfnOVR+idtr /v1uQEpYgf3samtcjxOhjKEJIcfXNXyucq6VB0EDFNB+nFZ/hyACATYl/rxxnN588eGd XrrGxY14RtTXYMiLBnJhWuM1m88Z7mhu08brO+fOLu936UdDDNlKNOTC3cN1wg/mmtOW sDgg==
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=QgdDTs8JR60o1VFUDRZGjePKJ3q/Ky9PQi7hYaeiEdc=; b=W8bZOe2IZQK8woo5atKYbBQQgaEo1+Z+FNbrwtyNH+KraCDFQRCTUnqGP24xf3g2/P 3YfDSG2AbB85NrF/V20R6GYZmhYGKYV9PHFU6z7h7XdWcJvwoVhqLwpVxW09+DXofHNF DX9NdqO7hmG8xIf5If+YyR5qDSmQED42ip0F/4X8E/8rDMuqBACAs64DkanfQ5Fx8z4h wBO3eRiRTBbfTrfCj+K415HapUfD5mezmtkMRvhIuzwGo6z2yJjABvEosCIN83b8o2R1 JHs1PbEJ87e7CZFYLJoINTKjeVEAql89fDRu17EbdQPBSlxnRny9flw9kVKhFJFuqwtp neig==
X-Gm-Message-State: AOAM533AJ7zCZCFjPtjrHs4CAMlGrigNSD6jRGSjSllZoOzDAkErqJEJ gjmrDMFK6pxbrbK8RVV9TmKnv7fjO0+j9HaVDhTv3psuiLc=
X-Google-Smtp-Source: ABdhPJwKxneEDa0TJM04oT7hng61rGwrM+HRHL9Q2rMW00MJTGTdfYy0suWATmR5OYzy72bjpLP9Ekd0pDJS5PCWuTo=
X-Received: by 2002:a05:6602:2d90:: with SMTP id k16mr3806278iow.19.1602106942363; Wed, 07 Oct 2020 14:42:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAPDSy+7jKFSLPiw9=iGijT5E-A+GYSisfaL9-pLbFZQ8NfeAFg@mail.gmail.com>
In-Reply-To: <CAPDSy+7jKFSLPiw9=iGijT5E-A+GYSisfaL9-pLbFZQ8NfeAFg@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 07 Oct 2020 14:42:12 -0700
Message-ID: <CAM4esxRJ9kmG52YSEeBCq-4P3f8AdMYM5xUyUuXV_gNWsLVodw@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="000000000000311e1405b11b97f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JatSBqxH03R4-P3_IQq0w8UnXww>
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: Wed, 07 Oct 2020 21:42:28 -0000

Thanks David. I'm intrigued by your performance numbers. You say there's no
0RTT and I've always thought of you guys running a pretty state-of-the-art
TCP stack. Is this just HOL blocking, or is there something else?

On Wed, Oct 7, 2020 at 9:50 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