al Message-
From: Gen-art On Behalf Of Christer Holmberg
Sent: Monday, 22 May 2023 10.48
To: Mark Nottingham
Cc: gen-art@ietf.org; HTTP APIs Working Group ; Last Call
Subject: Re: [Gen-art] Genart last call review of
draft-ietf-httpapi-link-template-02
Hi Mark,
>>> Ah. The reason
Hi Mark,
>>> Ah. The reason is that allowing any type would require creating a
>>> mapping of current values to SF types, and there are just too many
>>> potential (and undocumented) values already in use to do this.
>>
>> I don't think that is true. Just because the Parameter syntax allows
>>
Hi Christer,
> On 20 May 2023, at 2:58 am, Christer Holmberg
> wrote:
[...]
>> Ah. The reason is that allowing any type would require creating a mapping of
>> current values to SF types, and there
>> are just too many potential (and undocumented) values already in use to do
>> this.
>
> I
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
Hi Christer,
Thanks for the review; responses below.
> On 16 May 2023, at 1:37 pm, Christer Holmberg via Datatracker
> wrote:
[...]
> 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
Reviewer: Christer Holmberg
Review result: Ready with Issues
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
