IETF Logo Mail Archive

Re: An Update about Chrome and IETF QUIC

Behcet Sarikaya <sarikaya2012@gmail.com> Wed, 21 October 2020 15:03 UTC

Return-Path: <sarikaya2012@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 B97933A09E7 for <quic@ietfa.amsl.com>; Wed, 21 Oct 2020 08:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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_ENVFROM_END_DIGIT=0.25, 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 31EJoJEBj5V4 for <quic@ietfa.amsl.com>; Wed, 21 Oct 2020 08:03:26 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 111213A00DB for <quic@ietf.org>; Wed, 21 Oct 2020 08:03:26 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id h6so2024163ybi.11 for <quic@ietf.org>; Wed, 21 Oct 2020 08:03:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=bX5eMtgwF/jv1FB9TDUW2QUoeX/sxfmlNvioHQnSV7U=; b=o2U/84DNqrcehw/1pvfWvzPCVGYwOiaox3Y4zb5gUrYqHOzgw7n7P6/wXBcAhuSNT4 xpQR5u+PXCYC/eiPhCn/1njUMUbi2lfWkZCDpq+31KLqBeDwW2Jg1oNPlUZdmxA3fhT8 cMviy+kWsaDxWt+4DU4VJxCoGrQm9zEprf771YOqERvEx6sIPDwZXKSOBy6INxl151LW 4RVyN4oVRmoRFf3JhTwUoIimEsgLCfSuWXXBTgiI7VO4mC1MAdfy5bVmOyAhdPaTvXsn n4rWJtmWIdL4+ZU85Py5b0Wh3aBf2xmkLfyz4mxPVpAeBEstZQPAn+rDNfzAKISOl48v RFKw==
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:reply-to :from:date:message-id:subject:to:cc; bh=bX5eMtgwF/jv1FB9TDUW2QUoeX/sxfmlNvioHQnSV7U=; b=bEL2n6YRptZEFlZFnlBCXADi0vQuQ8+gEvHhK8VY/H95KivKLpCKqbKapPPMMth+i1 H0Hj9gwsprVB0SSkxjfVl9ZCvfzZcfuT8l9LYj9zSNDeTnR/15Gq95LaqtfgULKSNwOj 663JV3Wwxj+3gyJIf8ioCwFBa3NtRklpazHjRWS3nVN7D4GfEbwpY3oJq5yqkcYTbFlM Ux7ZjhqPag9SgyZfZkABTG3t9r5DLTzxbpZNeoUaa73klqJe9U/jSiHguhb2YF6m+Mv8 MScDA7pXsCUCeYXXK2/cq6dViu1AJZvPY9KG916PIIt6dtUshRlD6ZItg234AnX+u4u8 3bMg==
X-Gm-Message-State: AOAM533CTG9mFOS2Gva7OxSm52KV5AGyXr2nRtnpfErux7tJvnx+dw7s HGSzMoSoheD4umo3ikMYHw64ypDZJYRKG7RQAok=
X-Google-Smtp-Source: ABdhPJxfYzIL5NE22IPQym4g526Bdmy/f4Bdx2rTTNEfMte6bC+fhm/d1UE3K5wKw9oH/vFUatlZBlc4d1rRVmy4mtU=
X-Received: by 2002:a25:6d83:: with SMTP id i125mr5325720ybc.423.1603292604383; Wed, 21 Oct 2020 08:03:24 -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>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Wed, 21 Oct 2020 10:03:13 -0500
Message-ID: <CAC8QAcdoM99yFpbRZGjtn06wiEcsF3uhkpCcj-q1A4X57pL9+A@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="00000000000027c72905b22fa698"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ce7DaE5Iu4org06qMqKdsqgVGFw>
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, 21 Oct 2020 15:03:28 -0000

On Tue, Oct 20, 2020 at 12:40 PM 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.)
>
>
Good. So no interoperability issues?
Maybe because both receiver and sender software from the same manufacturer?

Behcet

> 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