change log (#33)

draft-ietf-httpbis-semantics-latest.xml

@@ -12860,6 +12860,11 @@ transfer-coding = &lt;transfer-coding, see <xref target="Messaging" x:fmt="," x:
    line's value, use "field line value".
    (<xref target="header.and.trailer.fields"/>)
 </t>
+<t>
+   Parameters in media type, media range, and expectation can be empty via
+   one or more trailing semicolons.
+   (<xref target="parameter"/>)
+</t>
 <t>
    Trailer field semantics now transcend the specifics of chunked encoding.
    Use of trailer fields has been further limited to only allow generation
@@ -12952,11 +12957,6 @@ transfer-coding = &lt;transfer-coding, see <xref target="Messaging" x:fmt="," x:
    values are present was clarified.
    (<xref target="field.vary"/>)
 </t>
-<t>
-   Parameters in media type, media range, and expectation can be empty via
-   one or more trailing semicolons.
-   (<xref target="parameter"/>)
-</t>
 </section>
 
 <section title="Changes from RFC 7232" anchor="changes.from.rfc.7232">
@@ -13212,6 +13212,7 @@ transfer-coding = &lt;transfer-coding, see <xref target="Messaging" x:fmt="," x:
 <section title="Since draft-ietf-httpbis-semantics-10" anchor="changes.since.10">
 <ul x:when-empty="None yet.">
   <li>In <xref target="content.coding.registry"/>, advise to make new content codings self-descriptive (<eref target="https://github.com/httpwg/http-core/issues/21"/>)</li>
+  <li>In <xref target="parameter"/>, introduced the "parameters" ABNF rule, allowing empty parameters and trailing semicolons within media type, media range, and expectation (<eref target="https://github.com/httpwg/http-core/issues/33"/>)</li>
   <li>In <xref target="introduction"/>, revise the introduction and introduce HTTP/2 and HTTP/3 (<eref target="https://github.com/httpwg/http-core/issues/64"/>)</li>
   <li>Moved requirements specific to HTTP/1.1 from <xref target="field.host"/> to <xref target="Messaging"/> (<eref target="https://github.com/httpwg/http-core/issues/182"/>)</li>
   <li>In <xref target="field.values"/>, introduce the terms "singleton field" and "list-based field" (also  - in various places - discuss what to do when a singleton field is received as a list) (<eref target="https://github.com/httpwg/http-core/issues/193"/>)</li>
@@ -13233,7 +13234,6 @@ transfer-coding = &lt;transfer-coding, see <xref target="Messaging" x:fmt="," x:
   <li>In <xref target="field.expect"/>, change the ABNF back to be a list of expectations, as defined in RFC 2616 (<eref target="https://github.com/httpwg/http-core/issues/203"/>)</li>
   <li>Moved definitions of "TE" and "Upgrade" from <xref target="Messaging"/> (<eref target="https://github.com/httpwg/http-core/issues/392"/>)</li>
   <li>Moved definition of "Connection" from <xref target="Messaging"/> (<eref target="https://github.com/httpwg/http-core/issues/407"/>)</li>
-  <li>In <xref target="parameter"/>, introduced the "parameters" ABNF rule, allowing empty parameters and trailing semicolons within media type, media range, and expectation (<eref target="https://github.com/httpwg/http-core/issues/33"/>)</li>
 </ul>
 </section>
 </section>