1414definitions and their metadata for the core QUIC protocol and selected
1515extensions.
1616 " name ="description ">
17- < meta content ="xml2rfc 3.30.2 " name ="generator ">
17+ < meta content ="xml2rfc 3.31.0 " name ="generator ">
1818< meta content ="Internet-Draft " name ="keyword ">
1919< meta content ="draft-ietf-quic-qlog-quic-events-latest " name ="ietf.draft ">
2020<!-- Generator version information:
21- xml2rfc 3.30.2
22- Python 3.12.11
21+ xml2rfc 3.31.0
22+ Python 3.12.12
2323 ConfigArgParse 1.7
2424 google-i18n-address 3.1.1
2525 intervaltree 3.1.0
2626 Jinja2 3.1.6
2727 lxml 5.3.1
28- platformdirs 4.4 .0
28+ platformdirs 4.5 .0
2929 pycountry 24.6.1
3030 PyYAML 6.0.2
3131 requests 2.32.5
32- setuptools 80.9.0
3332 wcwidth 0.2.14
3433-->
3534< link href ="draft-ietf-quic-qlog-quic-events.xml " rel ="alternate " type ="application/rfc+xml ">
10531052</ tr > </ thead >
10541053< tfoot > < tr >
10551054< td class ="left "> Marx, et al.</ td >
1056- < td class ="center "> Expires 17 April 2026</ td >
1055+ < td class ="center "> Expires 23 April 2026</ td >
10571056< td class ="right "> [Page]</ td >
10581057</ tr > </ tfoot >
10591058</ table >
10661065< dd class ="internet-draft "> draft-ietf-quic-qlog-quic-events-latest</ dd >
10671066< dt class ="label-published "> Published:</ dt >
10681067< dd class ="published ">
1069- < time datetime ="2025-10-14 " class ="published "> 14 October 2025</ time >
1068+ < time datetime ="2025-10-20 " class ="published "> 20 October 2025</ time >
10701069 </ dd >
10711070< dt class ="label-intended-status "> Intended Status:</ dt >
10721071< dd class ="intended-status "> Standards Track</ dd >
10731072< dt class ="label-expires "> Expires:</ dt >
1074- < dd class ="expires "> < time datetime ="2026-04-17 " > 17 April 2026</ time > </ dd >
1073+ < dd class ="expires "> < time datetime ="2026-04-23 " > 23 April 2026</ time > </ dd >
10751074< dt class ="label-authors "> Authors:</ dt >
10761075< dd class ="authors ">
10771076< div class ="author ">
@@ -1136,7 +1135,7 @@ <h2 id="name-status-of-this-memo">
11361135 time. It is inappropriate to use Internet-Drafts as reference
11371136 material or to cite them other than as "work in progress."< a href ="#section-boilerplate.1-3 " class ="pilcrow "> ¶</ a > </ p >
11381137< p id ="section-boilerplate.1-4 ">
1139- This Internet-Draft will expire on 17 April 2026.< a href ="#section-boilerplate.1-4 " class ="pilcrow "> ¶</ a > </ p >
1138+ This Internet-Draft will expire on 23 April 2026.< a href ="#section-boilerplate.1-4 " class ="pilcrow "> ¶</ a > </ p >
11401139</ section >
11411140</ div >
11421141< div id ="copyright ">
@@ -3960,15 +3959,26 @@ <h3 id="name-packetnumberspace">
39603959 < h3 id ="name-packetheader ">
39613960< a href ="#section-8.8 " class ="section-number selfRef "> 8.8. </ a > < a href ="#name-packetheader " class ="section-name selfRef "> PacketHeader</ a >
39623961 </ h3 >
3963- < p id ="section-8.8-1 "> If the fixed bit or the reserved bit has an invalid value, the raw value can
3964- be captured in the raw field of the event.< a href ="#section-8.8-1 " class ="pilcrow "> ¶</ a > </ p >
3962+ < p id ="section-8.8-1 "> If the < code > packet_type</ code > numerical value does not map to a known < code > $PacketType</ code >
3963+ string, the < code > packet_type</ code > value of "unknown" can be used and the raw value
3964+ captured in the < code > packet_type_bytes</ code > field; a numerical value without
3965+ variable-length integer encoding.< a href ="#section-8.8-1 " class ="pilcrow "> ¶</ a > </ p >
3966+ < p id ="section-8.8-2 "> The fixed and reserved bits are omitted here because they must be 0; see
3967+ < span > [< a href ="#QUIC-TRANSPORT " class ="cite xref "> QUIC-TRANSPORT</ a > ]</ span > . If these bits have an invalid value, the raw values can be
3968+ captured in the < code > raw.data</ code > field of the event logging the PacketHeader.< a href ="#section-8.8-2 " class ="pilcrow "> ¶</ a > </ p >
3969+ < p id ="section-8.8-3 "> QUIC extensions that do utilize these bits are expected to create new events
3970+ (analogous to < code > spin_bit_updated</ code > ) or use qlog extension mechanisms to reflect
3971+ that usage.< a href ="#section-8.8-3 " class ="pilcrow "> ¶</ a > </ p >
39653972< span id ="name-packetheader-definition "> </ span > < div id ="packetheader-def ">
39663973< figure id ="figure-46 ">
3967- < div class ="lang-cddl sourcecode " id ="section-8.8-2 .1 ">
3974+ < div class ="lang-cddl sourcecode " id ="section-8.8-4 .1 ">
39683975< pre >
39693976PacketHeader = {
39703977 packet_type: $PacketType
39713978
3979+ ; only if packet_type === "unknown"
3980+ ? packet_type_bytes: uint64
3981+
39723982 ; only if packet_type === "1RTT"
39733983 ? spin_bit: bool
39743984
@@ -3994,7 +4004,7 @@ <h3 id="name-packetheader">
39944004 ; Signifies length of the packet_number plus the payload
39954005 ? length: uint16
39964006
3997- ; only if present in the header
4007+ ; only if present in the header.
39984008 ; if correctly using transport:connection_id_updated events,
39994009 ; dcid can be skipped for 1RTT packets
40004010 ? version: QuicVersion
0 commit comments