Hi Mark,
Q2_2: The text says "Parameter values MUST be Strings."
It is unclear what "Strings" means. Does it mean that parameter
values must be encoded as quoted-strings? If so, why? RFC8288 says
that parameter values can be encoded both as token and quoted-string.
>>>
Hi Christer,
Thanks, see responses below.
> On 19 May 2023, at 1:13 pm, Christer Holmberg
> wrote:
>
> Hi Mark,
>
> Please see inline.
>
>>> Q2_1: There is no ABNF for the header field. There are examples using
>>> both quotes ("/{username}") and angle brackets
>>> (), so please include the
Hi Mark,
Please see inline.
>> Q2_1: There is no ABNF for the header field. There are examples using
>> both quotes ("/{username}") and angle brackets
>> (), so please include the ABNF.
>
> This is a Structured Field; in the HTTP community, we've agreed that
> documenting them with ABNF is not
