QUIC and HTTP/3 Datagram event definitions for qlog

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 27 April 2023.¶

Copyright Notice

Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶

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.¶

Table of Contents

1. Introduction

This document describes qlog data type definitions for both the QUIC Datagram Frame defined in [RFC9221] and the HTTP/3 Datagram Frame defined in [RFC9297]. These data types are intended for use within event definitions defined in [QLOG-QUIC] and [QLOG-HTTP3].¶

This document extends the $QuicFrame extension point defined in [QLOG-QUIC] and the $HTTPFrame extension point defined in [QLOG-HTTP3]. 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.¶

2. 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.¶

The event and data structure definitions in ths document are expressed in the Concise Data Definition Language [CDDL] and its extensions described in [QLOG-MAIN].¶

The following fields from [QLOG-MAIN] are imported and used: data and RawInfo.¶

3. 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¶

TransportParametersSet = {
    ? max_datagram_frame_size: uint64
    * text => any
}

QUICDatagramFrame = {
    frame_type: "datagram"
    ? length: uint64
    ? raw: RawInfo
}

$QuicFrame /= QUICDatagramFrame

4. 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¶

HTTP3DatagramSetting = {
    name: "SETTINGS_H3_DATAGRAM"
    value: uint16
}

HTTPDatagramFrame = {
    frame_type: "datagram"
    quarter_stream_id: uint64
    ? raw: RawInfo
}

$HTTPFrame /= HTTPDatagramFrame

5. Security and Privacy Considerations

The security and privacy considerations discussed in [QLOG-MAIN] apply to this document as well.¶

6. IANA Considerations

This document has no IANA actions.¶

Acknowledgments

TODO acknowledge.¶

Author's Address