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

rfc-editor@rfc-editor.org Thu, 27 May 2021 21:37 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 575713A143E; Thu, 27 May 2021 14:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 UBahGNLZz3BZ; Thu, 27 May 2021 14:37:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 395A53A13F6; Thu, 27 May 2021 14:37:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5B9ACF4072C; Thu, 27 May 2021 14:37:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9000 on QUIC: A UDP-Based Multiplexed and Secure Transport
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, quic@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210527213724.5B9ACF4072C@rfc-editor.org>
Date: Thu, 27 May 2021 14:37:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sjXBzygnbqx6UjOysh9YR8-VK_8>
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: Thu, 27 May 2021 21:37:50 -0000

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://www.rfc-editor.org/info/rfc9000

        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://www.rfc-editor.org/standards) 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://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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