Re: 8999?
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 05 May 2021 15:51 UTC
Return-Path: <spencerdawkins.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 90E2E3A14F5 for <quic@ietfa.amsl.com>; Wed, 5 May 2021 08:51:05 -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 yx6RgU-oBLky for <quic@ietfa.amsl.com>; Wed, 5 May 2021 08:51:00 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 013593A14FB for <quic@ietf.org>; Wed, 5 May 2021 08:50:59 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id z1so3277489ybf.6 for <quic@ietf.org>; Wed, 05 May 2021 08:50:59 -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=knO1U12MArCwyEdZD2SaA0B6tgon+3Q2b1P1REF4408=; b=sF+qplXA2LPwsSXyY/ViNvb5OOkg8s3WdCBRHur/WjZnVeR0nO8zFltQzpnMDY189i vwwNr6lxA5b0J0su9lY1YAQ1LTCd8/gyHZU0wV5N+WCFCyFcyqLVylh7/wT8zVfGabbs RWqsJvoSraufETlxjxsxquOFacOgqHW692ux7jhOidgaKNN4pCsqwiFQuBoWcvGsc+o4 oNXzQcTWe8QQJBnLAMn9k5HxSpm4jNeaN/0A5p9uoNiUMjFFedtMdtONwVDaKroMi/KZ LSFkMp2TUdxwXq6cEXREu9/7uu2xVoFklsh4Wj5M+MEJ07SdTdTQHa6mI4bqaG6Oa9Vx ZIuQ==
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=knO1U12MArCwyEdZD2SaA0B6tgon+3Q2b1P1REF4408=; b=FIBGVdgLiYZqVsXETudGm+ls85XiD4NvPZTadNK22XXXEQE6b91saRP8pZsbhec7bw /2Su9C/dPHiJws4rlCeX5hPDS4EsgPXytrRtXlT0H15fzPKNbdQPwvZOnr7nTxOHJ2gu nWrMAyjsPN4gyJsv2V5sU7AOV3UktuaVzPLSN7nkJIn21JBc9A3ebyEHtYiVBz+lkklv KuhK/ciKrcqDu5ygahjqZuDK/B9igF3RGgkhBzlFHZoV4ZBHChm8Jp5P3ZPyHX3k97DJ CLA55BmTd1de3YovElDh0GnF2YPNUfOLNEm6wgYzfqB1hsyyd9Wmss4GNgnOeqRnqXY2 d7cw==
X-Gm-Message-State: AOAM531mJYrKKW3cCO+BMu0BgmH3AhDKlUyc7e8hE0qw1gtw7oNU93Ue wqPV+YdI/Ua6NoWJQRNCmA7oWtZEiaI469VItV8=
X-Google-Smtp-Source: ABdhPJy7ntUyrrmWYxJpKU1M/ffk2xbVi4yjBFYvODW8EGsiSF2q8vIWfsUxQZurHl20cFSF1/Kekmh3Ru8qv08pVpg=
X-Received: by 2002:a25:7d42:: with SMTP id y63mr6048419ybc.389.1620229858463; Wed, 05 May 2021 08:50:58 -0700 (PDT)
MIME-Version: 1.0
References: <e692ad5c-5a1f-106a-a586-3c2573defdab@huitema.net> <56152de9-efb9-f8b0-bba4-b566bc8ef69a@huitema.net> <0fd7e332-67ec-4467-8887-92870cc01f75@www.fastmail.com> <CACpbDcdCw+-gT1N9qJsxwLqn+Pt+3H+u8JdCnPWYF8Uy8OLkFA@mail.gmail.com> <D2196636-03B0-4EA4-A4A4-2B6ECB89E35B@gmail.com>
In-Reply-To: <D2196636-03B0-4EA4-A4A4-2B6ECB89E35B@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 05 May 2021 10:50:32 -0500
Message-ID: <CAKKJt-dncJAHQbw1ay0DQcY4NZXUnEBLQrJBHr0n-GGZmx+O-w@mail.gmail.com>
Subject: Re: 8999?
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b130405c19729e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/l0VIQtcs9bn6sWnRQbvHUQwFknA>
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, 05 May 2021 15:51:06 -0000
Mikkel, On Wed, May 5, 2021 at 9:11 AM Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> wrote: > Is it too late to change the name QUIC to HAL ? > > Hidden Authenticated Link > Had we only known this would end up as RFC 9000, I would have LOVED to do this with the working group name, because we spent years explaining to people whether we were talking about Google QUIC, or IETF QUIC, and whether they were the same thing or not. But picking any new name only seemed smarter when we'd already chartered the working group and adopted drafts, by which time it seemed unhelpful. Hindsight is 20/20. Or, in this case, 9000/9000. Best, Spencer > On 5 May 2021, at 15.21, Jana Iyengar <jri.ietf@gmail.com> wrote: > > Yup, we’re almost there, but hold on to the champagne bottles .... > something about eggs and counting chickens. > > Though it is ok to get a bit excited :-) > > And clearly, that we were completely coincidentally assigned 9000 is a > sign that the gods are putting their power behind this. > > On Tue, May 4, 2021 at 11:41 PM Martin Thomson <mt@lowentropy.net> wrote: > >> These aren't formal; don't get too excited. Hold on for at least one >> more week, I'd say. >> >> We're just in the process of porting the changes from the RFC editor into >> our repository. We're doing that to verify that everything is good before >> we give the final approvals. >> >> On Wed, May 5, 2021, at 16:17, Christian Huitema wrote: >> > And of course: >> > >> > RFC 9000 -- QUIC: A UDP-Based Multiplexed and Secure Transport >> > >> > RFC 9001 -- Using TLS to Secure QUIC >> > >> > RFC 9002 -- QUIC Loss Detection and Congestion Control >> > >> > 9000! That's very cool. >> > >> > -- Christian Huitema >> > >> > >> > >> > >> > On 5/4/2021 8:14 PM, Christian Huitema wrote: >> > > Just looking at https://quicwg.org/base-drafts/rfc8999.html >> > > >> > > I see that: >> > > >> > > Stream: >> > > Internet Engineering Task Force (IETF) >> > > RFC: >> > > 8999 <https://datatracker.ietf.org/doc/html/rfc8999> >> > > Category: >> > > Standards Track >> > > Published: >> > > May 2021 ISSN: >> > > 2070-1721 >> > > Author: >> > > M. Thomson >> > > Mozilla >> > > >> > > Congratulations! >> > > >> > > -- Christian Huitema >> > > >> > > >> > >> > >> >> >
- 8999? Christian Huitema
- Re: 8999? Christian Huitema
- Re: 8999? Martin Thomson
- Re: 8999? Julian Reschke
- Re: 8999? Jana Iyengar
- Re: 8999? Mikkel Fahnøe Jørgensen
- Re: 8999? Carsten Bormann
- Re: 8999? Spencer Dawkins at IETF
- Re: 8999? Mikkel Fahnøe Jørgensen
- Re: 8999? Behcet Sarikaya
- Re: 8999? Magnus Westerlund
- Re: 8999? Robin MARX