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
>> val
...and, as the comment was about Parameters, my examples should look like:
Example-Header: X; parm="1234" // sf-string
Example-Header: X; parm=1234// sf-integer
Example-Header: X; parm="foo123"// sf-string
Example-Header: X; parm=foo123 // sf-token
Example-Header: X; parm="
Hi Russ,
thank you for this review.
Two comments:
> Minor Concerns:
>
> Section 3: A reference to ABNF is needed. Since %s is being used,
> I believe that a reference to RFC 7405 is required. Alternatively,
> the paragraph in Section 1.1 could be moved to Section 3.
We generally write IETF d
