[C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic-transport-34.txt> NOW AVAILABLE
rfc-editor@rfc-editor.org Tue, 27 April 2021 07:22 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: c430@rfc-editor.org
Delivered-To: c430@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 926AFF40794; Tue, 27 Apr 2021 00:22:19 -0700 (PDT)
To: jri.ietf@gmail.com, mt@lowentropy.net
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, quic-ads@ietf.org, quic-chairs@ietf.org, lars@eggert.org, c430@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210427072219.926AFF40794@rfc-editor.org>
Date: Tue, 27 Apr 2021 00:22:19 -0700
Subject: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic-transport-34.txt> NOW AVAILABLE
X-BeenThere: c430@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <c430.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/c430>, <mailto:c430-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/c430/>
List-Post: <mailto:c430@rfc-editor.org>
List-Help: <mailto:c430-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/c430>, <mailto:c430-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 07:22:19 -0000
*****IMPORTANT***** Updated 2021/04/27 RFC Author(s): -------------- Instructions for Completing AUTH48 Your document has now entered AUTH48. Once it has been reviewed and approved by you and all coauthors, it will be published as an RFC. If an author is no longer available, there are several remedies available as listed in the FAQ (https://www.rfc-editor.org/faq/). You and you coauthors are responsible for engaging other parties (e.g., Contributors or Working Group) as necessary before providing your approval. Planning your review --------------------- Please review the following aspects of your document: * RFC Editor questions Please review and resolve any questions raised by the RFC Editor that have been included in the XML file as comments marked as follows: <!-- [rfced] ... --> These questions will also be sent in a subsequent email. * Changes submitted by coauthors Please ensure that you review any changes submitted by your coauthors. We assume that if you do not speak up that you agree to changes submitted by your coauthors. * Content Please review the full content of the document, as this cannot change once the RFC is published. Please pay particular attention to: - IANA considerations updates (if applicable) - contact information - references * Copyright notices and legends Please review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP – https://trustee.ietf.org/license-info/). * Semantic markup Please review the markup in the XML file to ensure that elements of content are correctly tagged. For example, ensure that <sourcecode> and <artwork> are set correctly. See details at <https://xml2rfc.tools.ietf.org/xml2rfc-doc.html>. * Formatted output Please review the PDF, HTML, and TXT files to ensure that the formatted output, as generated from the markup in the XML file, is reasonable. Please note that the TXT will have formatting limitations compared to the PDF and HTML. Submitting changes ------------------ To submit changes, please reply to this email with one of the following, using ‘REPLY ALL’ as all the parties CC’ed on this message need to see your changes: An update to the provided XML file — OR — An explicit list of changes in this format Section # (or indicate Global) OLD: old text NEW: new text You do not need to reply with both an updated XML file and an explicit list of changes, as either form is sufficient. We will ask a stream manager to review and approve any changes that seem beyond editorial in nature, e.g., addition of new text, deletion of text, and technical changes. Information about stream managers can be found in the FAQ. Editorial changes do not require approval from a stream manager. Approving for publication -------------------------- To approve your RFC for publication, please reply to this email s tating that you approve this RFC for publication. Please use ‘REPLY ALL’ as all the parties CC’ed on this message need to see your approval. Files ----- The files are available here: https://www.rfc-editor.org/authors/rfc9000.xml https://www.rfc-editor.org/authors/rfc9000.html https://www.rfc-editor.org/authors/rfc9000.pdf https://www.rfc-editor.org/authors/rfc9000.txt Diff file of the text: https://www.rfc-editor.org/authors/rfc9000-diff.html Diff of the XML: https://www.rfc-editor.org/authors/rfc9000-xmldiff1.html The following file is provided to facilitate creation of your own diff files of the XML. This file is a best effort to capture v3-related format updates only: https://www.rfc-editor.org/authors/rfc9000.form.xml Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://www.rfc-editor.org/auth48/rfc9000 Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9000 (draft-ietf-quic-transport-34) Title : QUIC: A UDP-Based Multiplexed and Secure Transport Author(s) : J. Iyengar, Ed., M. Thomson, Ed. WG Chair(s) : Lars Eggert, Lucas Pardue, Matt Joras Area Director(s) : Martin Duke, Zaheduzzaman Sarker
- [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic-tra… rfc-editor
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… rfc-editor
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Lynne Bartholomew
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Martin Thomson
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Martin Thomson
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Lynne Bartholomew
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Lynne Bartholomew
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Martin Thomson
- Re: [C430] AUTH48 [LB]: RFC 9000 <draft-ietf-quic… Lynne Bartholomew