[rfc-dist] RFC 9297 on HTTP Datagrams and the Capsule Protocol
rfc-editor@rfc-editor.org Wed, 24 August 2022 18:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6539C1522D4; Wed, 24 Aug 2022 11:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.958
X-Spam-Level:
X-Spam-Status: No, score=-3.958 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, 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 VrBaHLedDAJp; Wed, 24 Aug 2022 11:38:20 -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 06D51C15790B; Wed, 24 Aug 2022 11:38:19 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B0EEE55A4B; Wed, 24 Aug 2022 11:38:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: [rfc-dist] RFC 9297 on HTTP Datagrams and the Capsule Protocol
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, masque@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220824183819.B0EEE55A4B@rfcpa.amsl.com>
Date: Wed, 24 Aug 2022 11:38:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/cG7oyD4GB_mp6Q6FEKtNnQBQ0fg>
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2022 18:38:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9297
Title: HTTP Datagrams and the Capsule Protocol
Author: D. Schinazi,
L. Pardue
Status: Standards Track
Stream: IETF
Date: August 2022
Mailbox: dschinazi.ietf@gmail.com,
lucaspardue.24.7@gmail.com
Pages: 14
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-masque-h3-datagram-11.txt
URL: https://www.rfc-editor.org/info/rfc9297
DOI: 10.17487/RFC9297
This document describes HTTP Datagrams, a convention for conveying
multiplexed, potentially unreliable datagrams inside an HTTP
connection.
In HTTP/3, HTTP Datagrams can be sent unreliably using the QUIC
DATAGRAM extension. When the QUIC DATAGRAM frame is unavailable or
undesirable, HTTP Datagrams can be sent using the Capsule Protocol,
which is a more general convention for conveying data in HTTP
connections.
HTTP Datagrams and the Capsule Protocol are intended for use by HTTP
extensions, not applications.
This document is a product of the Multiplexed Application Substrate over QUIC Encryption 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