]> Akamai

rmarx@akamai.com

Transport QUIC qlog datagram This document describes qlog data type definitions for both the QUIC Datagram Frame defined in and the HTTP/3 Datagram Frame defined in . These data types are intended for use within event definitions defined in and . About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the QUIC Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction This document describes qlog data type definitions for both the QUIC Datagram Frame defined in and the HTTP/3 Datagram Frame defined in . These data types are intended for use within event definitions defined in and . This document extends the $QuicFrame extension point defined in and the $HTTPFrame extension point defined in . It also defines how to log a QUIC transport parameter for indicating QUIC datagram support, as well as an HTTP/3 setting to indicate HTTP/3 datagram support.

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 when, and only when, they appear in all capitals, as shown here. The event and data structure definitions in ths document are expressed in the Concise Data Definition Language and its extensions described in . The following fields from are imported and used: data and RawInfo.

QUIC Datagrams qlog support for QUIC Datagram frames consists of two aspects:

• support for logging the max_datagram_frame_size QUIC transport parameter
• support for logging the type, length and contents of the DATAGRAM frame itself

max_datagram_frame_size transport parameter Support for the QUIC Datagram extension defined in is signaled using the max_datagram_frame_size transport parameter, defined in . If utilized, this transport parameter MUST be logged as a field of the transport:parameters_set event defined in , more specifically:

TransportParametersSet extended with the max_datagram_frame_size parameter any } ]]>

QUICDatagramFrame Definition This section describes a qlog data type that can be used to log the contents of the QUIC DATAGRAM frame defined in . The $QuicFrame extension point defined in is utilized to link the QUICDatagramFrame type to the existing qlog data types.

QUICDatagramFrame definition

HTTP/3 Datagrams qlog support for HTTP/3 Datagram frames consists of two aspects:

• support for logging the SETTINGS_H3_DATAGRAM HTTP/3 setting
• support for logging the type and contents of the HTTP/3 DATAGRAM frame itself

SETTINGS_H3_DATAGRAM setting Support for the HTTP/3 Datagram extension defined in is signaled using the SETTINGS_H3_DATAGRAM setting, defined in . If utilized, this setting MUST be logged as a field of the HTTPSetting data type defined in , more specifically:

HTTPSetting instance for SETTINGS_H3_DATAGRAM

HTTPDatagramFrame Definition This section describes a qlog data type that can be used to log the contents of the HTTP/3 DATAGRAM frame defined in . The $HTTPFrame extension point defined in is utilized to link the HTTPDatagramFrame type to the existing qlog data types.

HTTPDatagramFrame definition

Security and Privacy Considerations The security and privacy considerations discussed in apply to this document as well.

IANA Considerations This document has no IANA actions.

Normative References KU Leuven Facebook Protocol Labs This document describes a high-level schema for a standardized logging format called qlog. This format allows easy sharing of data and the creation of reusable visualization and debugging tools. The high-level schema in this document is intended to be protocol- agnostic. Separate documents specify how the format should be used for specific protocol data. The schema is also format-agnostic, and can be represented in for example JSON, csv or protobuf. KU Leuven Facebook Protocol Labs This document describes concrete qlog event definitions and their metadata for QUIC events. These events can then be embedded in the higher level schema defined in [QLOG-MAIN]. KU Leuven Facebook Protocol Labs This document describes concrete qlog event definitions and their metadata for HTTP/3 and QPACK-related events. These events can then be embedded in the higher level schema defined in [QLOG-MAIN]. This document defines an extension to the QUIC transport protocol to add support for sending and receiving unreliable datagrams over a QUIC connection. 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. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.

Acknowledgments TODO acknowledge.