RFC9297-BootstrappingWebSocketswithHTTP/3_WebSocket over HTTP/3资源-CSDN下载

网络协议

websocket

187 浏览量 2024-08-02 13:14:50 上传评论收藏 561KB PDF 举报

资源推荐

资源详情

资源评论

Internet Engineering Task Force (IETF)

Request for Comments: 9297

Category: Standards Track

Published: August 2022

ISSN: 2070-1721

D. Schinazi

Google LLC

L. Pardue

Cloudflare

HTTP Datagrams and the Capsule Protocol

Abstract

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.

Status of This Memo

This is an Internet Standards Track document.

This document is a product of the Internet Engineering Task Force

(IETF). It represents the consensus of the IETF community. It has

received public review and has been approved for publication by the

Internet Engineering Steering Group (IESG). Further information on

Internet Standards is available in Section 2 of RFC 7841.

Information about the current status of this document, any errata,

and how to provide feedback on it may be obtained at

https://www.rfc-editor.org/info/rfc9297.

This document is subject to BCP 78 and the IETF Trust's Legal

Provisions Relating to IETF Documents

(https://trustee.ietf.org/license-info) in effect on the date of

publication of this document. Please review these documents

carefully, as they describe your rights and restrictions with respect

to this document. Code Components extracted from this document must

include Revised BSD License text as described in Section 4.e of the

Trust Legal Provisions and are provided without warranty as described

in the Revised BSD License.

21/05/2024, 17:27

RFC 9297 - HTTP Datagrams and the Capsule Protocol

https://datatracker.ietf.org/doc/html/rfc9297

1/14

Table of Contents
1.Introduction
1.1.Conventions and Definitions
2.HTTP Datagrams
2.1.HTTP/3 Datagrams
2.1.1.The SETTINGS_H3_DATAGRAM HTTP/3 Setting
2.2.HTTP Datagrams Using Capsules
3.Capsules
3.1.HTTP Data Streams
3.2.The Capsule Protocol
3.3.Error Handling
3.4.The Capsule-Protocol Header Field
3.5.The DATAGRAM Capsule
4.Security Considerations
5.IANA Considerations
5.1.HTTP/3 Setting
5.2.HTTP/3 Error Code
5.3.HTTP Header Field Name
5.4.Capsule Types
6.References
6.1.Normative References
6.2.Informative References
Acknowledgments
Authors' Addresses
1.  Introduction
HTTP extensions (as defined in Section 16 of [HTTP]) sometimes need
to access underlying transport protocol features such as unreliable
delivery (as offered by [QUIC-DGRAM]) to enable desirable features.
For example, this could allow for the introduction of an unreliable
version of the CONNECT method and the addition of unreliable delivery
to WebSockets [WEBSOCKET].
In Section 2, this document describes HTTP Datagrams, a convention
for conveying bidirectional and potentially unreliable datagrams
inside an HTTP connection, with multiplexing when possible. While
HTTP Datagrams are associated with HTTP requests, they are not a part
of message content. Instead, they are intended for use by HTTP
extensions (such as the CONNECT method) and are compatible with all
versions of HTTP.
When HTTP is running over a transport protocol that supports
unreliable delivery (such as when the QUIC DATAGRAM extension [QUIC-
DGRAM] is available to HTTP/3 [HTTP/3]), HTTP Datagrams can use that
capability.
In Section 3, this document describes the HTTP Capsule Protocol,
which allows the conveyance of HTTP Datagrams using reliable
delivery. This addresses HTTP/3 cases where use of the QUIC DATAGRAM
frame is unavailable or undesirable or where the transport protocol
¶
¶
¶
21/05/2024, 17:27
RFC 9297 - HTTP Datagrams and the Capsule Protocol
https://datatracker.ietf.org/doc/html/rfc9297
2/14

only provides reliable delivery, such as with HTTP/1.1 [HTTP/1.1] or

HTTP/2 [HTTP/2] over TCP [TCP].

1.1. Conventions and Definitions

The key words "

MUST

", "

MUST NOT

", "

REQUIRED

", "

SHALL

", "

SHALL NOT

SHOULD

", "

SHOULD NOT

", "

RECOMMENDED

", "

NOT RECOMMENDED

", "

MAY

", and

OPTIONAL

" in this document are to be interpreted as described in

BCP14 [RFC2119] [RFC8174] when, and only when, they appear in all

capitals, as shown here.

This document uses terminology from [QUIC].

Where this document defines protocol types, the definition format

uses the notation from Section 1.3 of [QUIC]. Where fields within

types are integers, they are encoded using the variable-length

integer encoding from Section 16 of [QUIC]. Integer values do not

need to be encoded on the minimum number of bytes necessary.

In this document, the term "intermediary" refers to an HTTP

intermediary as defined in Section 3.7 of [HTTP].

2. HTTP Datagrams

HTTP Datagrams are a convention for conveying bidirectional and

potentially unreliable datagrams inside an HTTP connection with

multiplexing when possible. All HTTP Datagrams are associated with an

HTTP request.

When HTTP Datagrams are conveyed on an HTTP/3 connection, the QUIC

DATAGRAM frame can be used to provide demultiplexing and unreliable

delivery; see Section 2.1. Negotiating the use of QUIC DATAGRAM

frames for HTTP Datagrams is achieved via the exchange of HTTP/3

settings; see Section 2.1.1.

When running over HTTP/2, demultiplexing is provided by the HTTP/2

framing layer, but unreliable delivery is unavailable. HTTP Datagrams

are negotiated and conveyed using the Capsule Protocol; see Section

3.5.

When running over HTTP/1.x, requests are strictly serialized in the

connection; therefore, demultiplexing is not available. Unreliable

delivery is likewise not available. HTTP Datagrams are negotiated and

conveyed using the Capsule Protocol; see Section 3.5.

HTTP Datagrams

MUST

only be sent with an association to an HTTP

request that explicitly supports them. For example, existing HTTP

methods GET and POST do not define semantics for associated HTTP

Datagrams; therefore, HTTP Datagrams associated with GET or POST

request streams cannot be sent.

If an HTTP Datagram is received and it is associated with a request

that has no known semantics for HTTP Datagrams, the receiver

MUST

21/05/2024, 17:27

RFC 9297 - HTTP Datagrams and the Capsule Protocol

https://datatracker.ietf.org/doc/html/rfc9297

3/14

剩余13页未读，继续阅读

评论收藏

内容反馈

FeelTouchLabs

粉丝: 2w+

RFC9297 - Bootstrapping WebSockets with HTTP/3

最新资源

RFC9297 - Bootstrapping WebSockets with HTTP/3

RFC2151 - 关于Internet和TCP/IP工具和应用程序的初级读本

中文版RFC文档

RFC1271-MIB

Hypertext Transfer Protocol Version 2

UPS-RFC1628-MIB.mib

RFC-2068(HTTP)

RFC 2616 - Hypertext Transfer Protocol -- HTTP 1.1协议详细参考文档

RFC1001 - RFC1960

中方RFC RFC3---RFC3093，chm文件,查找、学习、引用的好帮手

RFC1305-NTP协议

rfc1001-rfc1500

RFC2616-超文本传输协议 http1.1

RFC大全--中文翻译

RFC791中文文档

RFC10xx 内容,分析与详解

RFC9114 - HTTP/3

NW RFC SDK for Windows 7.50.15

RFC 2501-3000

RFC1939-POP3.rar_RFC1939_pop3_rfc pop

RFC中文文档全集【RFC1-3093】

英文全套RFC0001-0500

RFC 1187 - Bulk Table Retrieval with the SNMP

RFC2617-cn.pdf

前端开源库-rfc822-date

RFC 6749-OAuth 2.0授权框架(中文版).pdf

RFC 0001-0500

RTSP / RTP / RTMP / FLV / HLS / MPEG-TS / MPEG-PS / MPEG-DASH / MP4 / fMP4-C/C++开发

RFC4001-RFC5065

RFC-768-791-792-793-826-1122-6298

深入理解JVM（③）JVM运行时数据区域

探索5G NB-IoT技术的奥秘

最新资源