From nobody Tue Mar 30 18:44:49 2021 Return-Path: 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 92AAF3A1009 for ; Tue, 30 Mar 2021 18:44:47 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 BtLPhgNtJsbK for ; Tue, 30 Mar 2021 18:44:42 -0700 (PDT) Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 B4A8F3A100A for ; Tue, 30 Mar 2021 18:44:42 -0700 (PDT) Received: by mail-oi1-x22d.google.com with SMTP id x207so18513268oif.1 for ; Tue, 30 Mar 2021 18:44:42 -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=0ypti/09fxe5yKmPm8dFnjUcInUahbVLzH49ff/vziY=; b=WMf80wUrdbIAS5XvHVtzXU4zBW6bt8JhSX25Rys4TGaCd/qTvlCnZDhDtYHcP39chN U+z06jhkEEkq1i/hZXbP4alXViO24jx+aUT8Rx7LuKlCSjZk+DJX420E0ZzBuOAMMzJh KJUnz39qMkci9QzdtLklb8JGoOf6fl2ewd6TInWWRwer8XaTTslxe7ELYhDoDHJSbuy6 ye6fBwoCPdgH1/2J+f8GlnipWC/LDDSubkYKlv4Omydma8903nAYoB8b+6hrhxwkKfZR BK4wg0WZCW6jUo3N+ec+JBok/tiXmBATbDFu11rzpbkCfBG0ejjLzJ0e3Mg9DPeMxLVi yiNw== 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=0ypti/09fxe5yKmPm8dFnjUcInUahbVLzH49ff/vziY=; b=W/SlSE5JhPpv2pWgBStCU/Tu4gWH13LnhElF6DD2lVjaI7MR8reELDthWSjpeKAw/i gNJzTdDaHeWxBzP10YrweILsPoQ8Q487qis6xfER/SgUozyfV97sApsF5JeRodeiFwXK cmMummv17vFeKDPaLd/AUgEQBElnbaxmGEkCUteDd9whAD7qXpT9rq43fs8a4/N5gPQT CkpNRWtpe2i3i0L/8uLACLNbYuO+A/yG3vG0MBScugL+q4TZghVRW5swtLJ7AHw/3Asu jszXfA86GTuNKuxz61xYqjJBwP7RBAp24Il7VbjCKa/Zfi7/KgXVz3GPISE5HuKKgvok psdA== X-Gm-Message-State: AOAM533JTvLpv97ahmpw69tyZ5zyC/ygbgypum5ytxXg1lYJZalIlzAZ dWEuABnCN2Tm0et3bGS/S96+o2mNBMUx/N77u2WOidKCTzf1fw== X-Google-Smtp-Source: ABdhPJybgIgBVkXrw780+gNKNqvqDO8GjU+5sHGM/LsA//MUUFX3MbRB4xMAUwVF5qjSwIWFRyIri7PQFMxdBoZBwNw= X-Received: by 2002:a05:6808:94:: with SMTP id s20mr555172oic.25.1617155081280; Tue, 30 Mar 2021 18:44:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marten Seemann Date: Wed, 31 Mar 2021 08:44:29 +0700 Message-ID: Subject: Re: Call for adoption QUIC: QUIC bit grease To: Martin Thomson Cc: QUIC WG Content-Type: multipart/alternative; boundary="0000000000002a9f4c05becb42dc" Archived-At: X-BeenThere: quic@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Main mailing list of the IETF QUIC working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Mar 2021 01:44:48 -0000 --0000000000002a9f4c05becb42dc Content-Type: text/plain; charset="UTF-8" I haven't implemented it yet in quic-go, but it's on my list. I support adoption. On Wed, Mar 31, 2021 at 7:08 AM Martin Thomson wrote: > Obviously I think this is a good idea. I've implemented it and Firefox > plans to deploy with it enabled for HTTP. > > On Wed, Mar 31, 2021, at 06:41, Matt Joras wrote: > > Hello all, > > > > As with the other mail we are looking at moving candidates for > > adoption forward. It is the opinion of the chairs that the QUIC bit > > grease draft[1] has sufficient interest from and relevance to the WG > > to be formally adopted. This email is the call to do so. There are > > already several interoperating implementations of the current draft. > > Please reply to this email with any comments, the call will run > > through April 6th. > > > > Thanks, > > QUIC Chairs > > > > [1] https://datatracker.ietf.org/doc/draft-thomson-quic-bit-grease/ > > > > > > --0000000000002a9f4c05becb42dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I haven't implemented it yet in quic-go, but it&#= 39;s on my list. I support adoption.

On Wed, Mar 31, 2021 at 7:08 = AM Martin Thomson <mt@lowentropy.ne= t> wrote:
Obviously I think this is a good idea.=C2=A0 I've implemented it and F= irefox plans to deploy with it enabled for HTTP.

On Wed, Mar 31, 2021, at 06:41, Matt Joras wrote:
> Hello all,
>
> As with the other mail we are looking at moving candidates for
> adoption forward. It is the opinion of the chairs that the QUIC bit > grease draft[1] has sufficient interest from and relevance to the WG > to be formally adopted. This email is the call to do so. There are
> already several interoperating implementations of the current draft. > Please reply to this email with any comments, the call will run
> through April 6th.
>
> Thanks,
> QUIC Chairs
>
> [1] https://datatracker.ietf.org= /doc/draft-thomson-quic-bit-grease/
>
>

--0000000000002a9f4c05becb42dc--