[Technical Errata Reported] RFC9842 (9182)

The following errata report has been submitted for RFC9842,
"Compression Dictionary Transport"

--------------------------------------
You may review the report below and at:
https://errata.rfc-editor.org/eid9182/

--------------------------------------
Type: Technical
Reported by: Antun Jurkovikj <antunjurkovic@gmail.com>

Section 2.2.2, step 6 says:

Original Text
-------------
6.  Let PATTERN be a "URL pattern struct" created by running the
    steps to "create a URL pattern" by setting input=MATCH and
    baseURL=URL (see Section 1.4 of [URLPATTERN]).

Corrected Text
--------------
6.  Let PATTERN be a "URL pattern struct" created by running the
    steps to "create a URL pattern" by setting input=MATCH and
    baseURL=BASEURL (see Section 1.4 of [URLPATTERN]).

Notes
-----
Step 2 defines BASEURL as the dictionary request URL, while step 3
defines URL as the outbound request URL. Step 6 uses the latter as
the base for constructing the dictionary's match pattern. Relative
patterns therefore acquire a different meaning depending on the
outbound request.

For example, a dictionary at https://example.com/assets/dict.bin
with match="*" has pathname pattern /assets/* when constructed as
specified in Section 2.1.1. For an outbound request to
https://example.com/private/account, Section 2.2.2 instead constructs
/private/* and returns a match. Using BASEURL retains /assets/* and
does not match. Conversely, match="child/*" can fail to match the
intended /assets/child/page because the published operand constructs
/assets/child/child/*.

The correction restores the dictionary request URL as the base.
The outbound request URL remains the matching input in step 7.
The same-origin and destination checks remain unchanged. The
baseURL=URL expression in Section 2.1.1 is correct and is not changed:
URL there denotes the dictionary request URL.

This reports an algorithm error, not an observed deployed failure.

Instructions:
-------------
This erratum is currently posted as "Reported". Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9842 (draft-ietf-httpbis-compression-dictionary)
--------------------------------------
Title               : Compression Dictionary Transport
Publication Date    : September 2025
Author(s)           : P. Meenan, Ed., Y. Weiss, Ed.
Category            : Proposed Standard
Source              : httpbis (wit)
Stream              : IETF
Verifying Party     : IESG

Received on Friday, 18 September 2026 14:12:16 UTC