Re: RFC 9000 on QUIC: A UDP-Based Multiplexed and Secure Transport

Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com> Fri, 28 May 2021 08:00 UTC

Return-Path: <mikkelfj@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 D5C083A1F51 for <quic@ietfa.amsl.com>; Fri, 28 May 2021 01:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level:
X-Spam-Status: No, score=-1.098 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, FREEMAIL_REPLY=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 AffzRogXPMaJ for <quic@ietfa.amsl.com>; Fri, 28 May 2021 00:59:59 -0700 (PDT)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 F09F13A1F4B for <quic@ietf.org>; Fri, 28 May 2021 00:59:58 -0700 (PDT)
Received: by mail-wm1-x329.google.com with SMTP id r13so1096168wmq.1 for <quic@ietf.org>; Fri, 28 May 2021 00:59:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GiNIbrW5o4xlcBU5d5m2XTN4plAZhU7rEg49aG5A4r8=; b=BS1tcWqEvtY25urATjwqo0IxQ16RB/m/4654OjVMeLEukswj7CXTSdoJ9cuHXdw8wB 47+ulc14RggwXZZ3CW+khR/nC01Vj8xb/rDj+kwtf5IA1hXMmuLiD6hx97/Pj1VBwL9N /vb37P3X6+hTucc1G63rZg670D2B6AYHpif9Uy+QR2EOAQIonDiD7ELJzFRfOiE0XPCV HoEFX+xWaQdFoyhmKlkEyVBlsMnmnyqqk/nPZBNJJp0+ig73AJdkM4L9RyQsMM71WjHL PYIL6+lf3ffgLtSCPEHQOYcTI1LCCxToX6N/4EvXP/SC5RIzOlzJhexTIhtaJhrbSAyL /oWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GiNIbrW5o4xlcBU5d5m2XTN4plAZhU7rEg49aG5A4r8=; b=dz/MorTSGKfrPDHyH2eOVg1EHrGy7DCBPH7jBrP3qlw5JqPWvQVkBjSCnLXh8EzktU MlJFKj0x47E5WStDPH3pvCZTOO2Yn2eHxyGKSK7gq2KtXNFnqbqEPa+sOhqoVuXsbk8z AoVKJz5sAHtXa5mK6XBOexU6ntyK5xW7lJyr15OkiI5jLjGK6WuM6z46lDh3bXewclzC iVpNZv0U9SPatixkUT+4zcEys4sDMbn3p+y65/i5FVSITpdZb0G7XzIos7uIENs0c9cN B43kejRKNCiP3KSj4OiDCWjE9+LgJhJ6kO7mq9dmkHdtoWFeOI7aYkngj3okJJlekPPt FTKg==
X-Gm-Message-State: AOAM530aR0ZQEF76r4PhZou5JMI/UfnPFBDIHNQRxv5kkggaQFjeDlEM bH8QC4gXLIho2NfK1e1PH462y0atlKyQUA==
X-Google-Smtp-Source: ABdhPJxtC+fzdaTtynbchSrodKYO9QSIpuU8C3mr4BDk09Azdp81LqzIJ/lhzGifvGmUj0qlDNew0w==
X-Received: by 2002:a1c:638b:: with SMTP id x133mr12249250wmb.182.1622188796708; Fri, 28 May 2021 00:59:56 -0700 (PDT)
Received: from [192.168.1.3] ([87.72.40.193]) by smtp.gmail.com with ESMTPSA id h13sm6093801wml.26.2021.05.28.00.59.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 May 2021 00:59:56 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: RFC 9000 on QUIC: A UDP-Based Multiplexed and Secure Transport
From: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
In-Reply-To: <337530D1-D275-43AC-879F-2393713F292F@ericsson.com>
Date: Fri, 28 May 2021 09:59:55 +0200
Cc: "quic@ietf.org" <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7441C0A1-C13F-49E2-98A3-8E665F6903D4@gmail.com>
References: <20210527213724.5B9ACF4072C@rfc-editor.org> <337530D1-D275-43AC-879F-2393713F292F@ericsson.com>
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/p69jbIo6Q-V5dmeU3bVg6EB-SXk>
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: Fri, 28 May 2021 08:00:04 -0000

Yes, great to see this being released!

> On 28 May 2021, at 09.45, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> wrote:
> 
> Yeah!!!! Great work everybody! And a huge thanks to the editors (of all RFCs)!
> 
> 
> 
> On 27.05.21, 23:40, "QUIC on behalf of rfc-editor@rfc-editor.org" <quic-bounces@ietf.org on behalf of rfc-editor@rfc-editor.org> wrote:
> 
>    A new Request for Comments is now available in online RFC libraries.
> 
> 
>            RFC 9000
> 
>            Title:      QUIC: A UDP-Based Multiplexed and
>                        Secure Transport 
>            Author:     J. Iyengar, Ed.,
>                        M. Thomson, Ed.
>            Status:     Standards Track
>            Stream:     IETF
>            Date:       May 2021
>            Mailbox:    jri.ietf@gmail.com,
>                        mt@lowentropy.net
>            Pages:      151
>            Updates/Obsoletes/SeeAlso:   None
> 
>            I-D Tag:    draft-ietf-quic-transport-34.txt
> 
>            URL:        https://protect2.fireeye.com/v1/url?k=4c0971e3-13924931-4c093178-866132fe445e-64ad4b752e91f559&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Finfo%2Frfc9000
> 
>            DOI:        10.17487/RFC9000
> 
>    This document defines the core of the QUIC transport protocol.  QUIC
>    provides applications with flow-controlled streams for structured
>    communication, low-latency connection establishment, and network path
>    migration. QUIC includes security measures that ensure
>    confidentiality, integrity, and availability in a range of deployment
>    circumstances.  Accompanying documents describe the integration of
>    TLS for key negotiation, loss detection, and an exemplary congestion
>    control algorithm.
> 
>    This document is a product of the QUIC Working Group of the IETF.
> 
>    This is now a Proposed Standard.
> 
>    STANDARDS TRACK: This document specifies an Internet Standards Track
>    protocol for the Internet community, and requests discussion and suggestions
>    for improvements.  Please refer to the current edition of the Official
>    Internet Protocol Standards (https://protect2.fireeye.com/v1/url?k=5c4fe193-03d4d941-5c4fa108-866132fe445e-b39c82f53e2846e7&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fstandards) for the 
>    standardization state and status of this protocol.  Distribution of this 
>    memo is unlimited.
> 
>    This announcement is sent to the IETF-Announce and rfc-dist lists.
>    To subscribe or unsubscribe, see
>      https://www.ietf.org/mailman/listinfo/ietf-announce
>      https://protect2.fireeye.com/v1/url?k=395fb930-66c481e2-395ff9ab-866132fe445e-30c0a739d8510073&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fmailman.rfc-editor.org%2Fmailman%2Flistinfo%2Frfc-dist
> 
>    For searching the RFC series, see https://protect2.fireeye.com/v1/url?k=f14f1c76-aed424a4-f14f5ced-866132fe445e-b8d7bba3e57c13ec&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fsearch
>    For downloading RFCs, see https://protect2.fireeye.com/v1/url?k=d150b7d0-8ecb8f02-d150f74b-866132fe445e-b1b5007dd32a3d05&q=1&e=e195985b-1bc7-46ba-924b-ec887dde4103&u=https%3A%2F%2Fwww.rfc-editor.org%2Fretrieve%2Fbulk
> 
>    Requests for special distribution should be addressed to either the
>    author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>    specifically noted otherwise on the RFC itself, all RFCs are for
>    unlimited distribution.
> 
> 
>    The RFC Editor Team
>    Association Management Solutions, LLC
> 
>