Script updating gh-pages from dfb10ac. [ci skip]

Author: ID Bot

index.html

@@ -385,12 +385,12 @@ <h2>Preview for branch <a href="packet-header">packet-header</a></h2>
       <tr>
         <td><a href="packet-header/draft-ietf-quic-qlog-h3-events.html" class="html draft-ietf-quic-qlog-h3-events" title="HTTP/3 qlog event definitions (HTML)">HTTP/3 qlog event definitions</a></td>
         <td><a href="packet-header/draft-ietf-quic-qlog-h3-events.txt" class="txt draft-ietf-quic-qlog-h3-events" title="HTTP/3 qlog event definitions (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://quicwg.github.io/qlog/draft-ietf-quic-qlog-h3-events.txt&amp;url_2=https://quicwg.github.io/qlog/packet-header/draft-ietf-quic-qlog-h3-events.txt" class="diff draft-ietf-quic-qlog-h3-events">diff with main</a></td>
+        <td>same as main</td>
       </tr>
       <tr>
         <td><a href="packet-header/draft-ietf-quic-qlog-main-schema.html" class="html draft-ietf-quic-qlog-main-schema" title="qlog: Structured Logging for Network Protocols (HTML)">qlog</a></td>
         <td><a href="packet-header/draft-ietf-quic-qlog-main-schema.txt" class="txt draft-ietf-quic-qlog-main-schema" title="qlog: Structured Logging for Network Protocols (Text)">plain text</a></td>
-        <td><a href="https://author-tools.ietf.org/api/iddiff?url_1=https://quicwg.github.io/qlog/draft-ietf-quic-qlog-main-schema.txt&amp;url_2=https://quicwg.github.io/qlog/packet-header/draft-ietf-quic-qlog-main-schema.txt" class="diff draft-ietf-quic-qlog-main-schema">diff with main</a></td>
+        <td>same as main</td>
       </tr>
       <tr>
         <td><a href="packet-header/draft-ietf-quic-qlog-quic-events.html" class="html draft-ietf-quic-qlog-quic-events" title="QUIC event definitions for qlog (HTML)">QUIC event definitions for qlog</a></td>

packet-header/draft-ietf-quic-qlog-h3-events.html

@@ -1217,7 +1217,7 @@ <h2 id="name-copyright-notice">
             <p id="section-toc.1-1.4.1"><a href="#section-4" class="auto internal xref">4</a>.  <a href="#name-http-3-data-type-definition" class="internal xref">HTTP/3 Data Type Definitions</a></p>
 <ul class="compact toc ulBare ulEmpty">
 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
-                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="auto internal xref">4.1</a>.  <a href="#name-owner" class="internal xref">Owner</a></p>
+                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="auto internal xref">4.1</a>.  <a href="#name-initiator" class="internal xref">Initiator</a></p>
 </li>
               <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
                 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="auto internal xref">4.2</a>.  <a href="#name-http3frame" class="internal xref">HTTP3Frame</a></p>
@@ -1543,15 +1543,15 @@ <h3 id="name-parameters_set">
 <p id="section-3.1-2">All these parameters are typically set once and never change. However, they
 might be set at different times during the connection, therefore a qlog can have
 multiple instances of <code>parameters_set</code> with different fields set.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
-<p id="section-3.1-3">The "owner" field reflects how Settings are exchanged on a connection. Sent
+<p id="section-3.1-3">The "initiator" field reflects how Settings are exchanged on a connection. Sent
 settings have the value "local" and received settings have the value
 "received".<a href="#section-3.1-3" class="pilcrow">¶</a></p>
 <span id="name-http3parametersset-definiti"></span><div id="h3-parametersset-def">
 <figure id="figure-2">
           <div class="lang-cddl sourcecode" id="section-3.1-4.1">
 <pre>
 HTTP3ParametersSet = {
-    ? owner: Owner
+    ? initiator: Initiator
 
     ; RFC9114
     ? max_field_section_size: uint64
@@ -1642,7 +1642,7 @@ <h3 id="name-stream_type_set">
           <div class="lang-cddl sourcecode" id="section-3.3-5.1">
 <pre>
 HTTP3StreamTypeSet = {
-    ? owner: Owner
+    ? initiator: Initiator
     stream_id: uint64
     stream_type: $HTTP3StreamType
 
@@ -1732,9 +1732,7 @@ <h3 id="name-frame_created">
 <pre>
 HTTP3FrameCreated = {
     stream_id: uint64
-    ? length: uint64
     frame: $HTTP3Frame
-    ? raw: RawInfo
 
     * $$http3-framecreated-extension
 }
@@ -1762,9 +1760,7 @@ <h3 id="name-frame_parsed">
 <pre>
 HTTP3FrameParsed = {
     stream_id: uint64
-    ? length: uint64
     frame: $HTTP3Frame
-    ? raw: RawInfo
 
     * $$h3-frameparsed-extension
 }
@@ -1876,21 +1872,21 @@ <h2 id="name-http-3-data-type-definition">
 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-http-3-data-type-definition" class="section-name selfRef">HTTP/3 Data Type Definitions</a>
       </h2>
 <p id="section-4-1">The following data type definitions can be used in HTTP/3 events.<a href="#section-4-1" class="pilcrow">¶</a></p>
-<div id="owner">
+<div id="initiator">
 <section id="section-4.1">
-        <h3 id="name-owner">
-<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-owner" class="section-name selfRef">Owner</a>
+        <h3 id="name-initiator">
+<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-initiator" class="section-name selfRef">Initiator</a>
         </h3>
-<span id="name-owner-definition"></span><div id="owner-def">
+<span id="name-initiator-definition"></span><div id="initiator-def">
 <figure id="figure-11">
           <div class="lang-cddl sourcecode" id="section-4.1-1.1">
 <pre>
-Owner = "local" /
-        "remote"
+Initiator = "local" /
+            "remote"
 </pre>
 </div>
 <figcaption><a href="#figure-11" class="selfRef">Figure 11</a>:
-<a href="#name-owner-definition" class="selfRef">Owner definition</a>
+<a href="#name-initiator-definition" class="selfRef">Initiator definition</a>
           </figcaption></figure>
 </div>
 </section>
@@ -2367,7 +2363,15 @@ <h2 id="name-iana-considerations">
         <dd class="break"></dd>
 <dt id="section-6-2.5">Event Types</dt>
         <dd style="margin-left: 1.5em" id="section-6-2.6">
-          <p id="section-6-2.6.1">parameters_set,parameters_restored,stream_type_set,priority_updated,frame_created,frame_parsed,datagram_created,datagram_parsed,push_resolved<a href="#section-6-2.6.1" class="pilcrow">¶</a></p>
+          <p id="section-6-2.6.1">parameters_set,
+parameters_restored,
+stream_type_set,
+priority_updated,
+frame_created,
+frame_parsed,
+datagram_created,
+datagram_parsed,
+push_resolved<a href="#section-6-2.6.1" class="pilcrow">¶</a></p>
 </dd>
         <dd class="break"></dd>
 <dt id="section-6-2.7">Description:</dt>
@@ -2449,8 +2453,8 @@ <h2 id="name-acknowledgements">
 Universities.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
 <p id="appendix-A-2">Thanks to Jana Iyengar, Brian Trammell, Dmitri Tikhonov, Stephen Petrides, Jari
 Arkko, Marcus Ihlar, Victor Vasiliev, Mirja Kühlewind, Jeremy Lainé, Kazu
-Yamamoto, Christian Huitema, Hugo Landau and Jonathan Lennox for their feedback
-and suggestions.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
+Yamamoto, Christian Huitema, Hugo Landau, Kazuho Oku, and Jonathan Lennox for
+their feedback and suggestions.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="change-log">

packet-header/draft-ietf-quic-qlog-h3-events.txt

@@ -79,7 +79,7 @@ Table of Contents
      3.8.  datagram_parsed
      3.9.  push_resolved
    4.  HTTP/3 Data Type Definitions
-     4.1.  Owner
+     4.1.  Initiator
      4.2.  HTTP3Frame
      4.3.  HTTP3Datagram
        4.3.1.  HTTP3DataFrame
@@ -267,12 +267,12 @@ Table of Contents
    therefore a qlog can have multiple instances of parameters_set with
    different fields set.
 
-   The "owner" field reflects how Settings are exchanged on a
+   The "initiator" field reflects how Settings are exchanged on a
    connection.  Sent settings have the value "local" and received
    settings have the value "received".
 
    HTTP3ParametersSet = {
-       ? owner: Owner
+       ? initiator: Initiator
 
        ; RFC9114
        ? max_field_section_size: uint64
@@ -350,7 +350,7 @@ Table of Contents
    stream types.
 
    HTTP3StreamTypeSet = {
-       ? owner: Owner
+       ? initiator: Initiator
        stream_id: uint64
        stream_type: $HTTP3StreamType
 
@@ -421,9 +421,7 @@ Table of Contents
 
    HTTP3FrameCreated = {
        stream_id: uint64
-       ? length: uint64
        frame: $HTTP3Frame
-       ? raw: RawInfo
 
        * $$http3-framecreated-extension
    }
@@ -441,9 +439,7 @@ Table of Contents
 
    HTTP3FrameParsed = {
        stream_id: uint64
-       ? length: uint64
        frame: $HTTP3Frame
-       ? raw: RawInfo
 
        * $$h3-frameparsed-extension
    }
@@ -517,12 +513,12 @@ Table of Contents
 
    The following data type definitions can be used in HTTP/3 events.
 
-4.1.  Owner
+4.1.  Initiator
 
-   Owner = "local" /
-           "remote"
+   Initiator = "local" /
+               "remote"
 
-                        Figure 11: Owner definition
+                      Figure 11: Initiator definition
 
 4.2.  HTTP3Frame
 
@@ -814,9 +810,9 @@ Table of Contents
 
    Namespace  http3
 
-   Event Types  parameters_set,parameters_restored,stream_type_set,prior
-      ity_updated,frame_created,frame_parsed,datagram_created,datagram_p
-      arsed,push_resolved
+   Event Types  parameters_set, parameters_restored, stream_type_set,
+      priority_updated, frame_created, frame_parsed, datagram_created,
+      datagram_parsed, push_resolved
 
    Description:  Event definitions related to the HTTP/3 application
       protocol.
@@ -893,8 +889,8 @@ Acknowledgements
 
    Thanks to Jana Iyengar, Brian Trammell, Dmitri Tikhonov, Stephen
    Petrides, Jari Arkko, Marcus Ihlar, Victor Vasiliev, Mirja Kühlewind,
-   Jeremy Lainé, Kazu Yamamoto, Christian Huitema, Hugo Landau and
-   Jonathan Lennox for their feedback and suggestions.
+   Jeremy Lainé, Kazu Yamamoto, Christian Huitema, Hugo Landau, Kazuho
+   Oku, and Jonathan Lennox for their feedback and suggestions.
 
 Change Log