RFC 9312 on Manageability of the QUIC Transport Protocol
rfc-editor@rfc-editor.org Wed, 28 September 2022 00:01 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E764C159A3E; Tue, 27 Sep 2022 17:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.66
X-Spam-Level:
X-Spam-Status: No, score=-5.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3yQHpzcrZbN; Tue, 27 Sep 2022 17:01:02 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F3DC15E412; Tue, 27 Sep 2022 16:58:06 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id E70B4AB20E; Tue, 27 Sep 2022 16:58:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9312 on Manageability of the QUIC Transport Protocol
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: <20220927235806.E70B4AB20E@rfcpa.amsl.com>
Date: Tue, 27 Sep 2022 16:58:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/7DVKibjK_pXDUM0RtxdIPB4rcGo>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2022 00:01:07 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9312
Title: Manageability of the QUIC Transport Protocol
Author: M. Kühlewind,
B. Trammell
Status: Informational
Stream: IETF
Date: September 2022
Mailbox: mirja.kuehlewind@ericsson.com,
ietf@trammell.ch
Pages: 29
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-quic-manageability-18.txt
URL: https://www.rfc-editor.org/info/rfc9312
DOI: 10.17487/RFC9312
This document discusses manageability of the QUIC transport protocol
and focuses on the implications of QUIC's design and wire image on
network operations involving QUIC traffic. It is intended as a
"user's manual" for the wire image to provide guidance for network
operators and equipment vendors who rely on the use of
transport-aware network functions.
This document is a product of the QUIC Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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