Re: draft-ietf-httpbis-header-structure-15, 2. Defining New Structured Headers

[Mark Nottingham <[e-mail]>]

Hi Kari,

Good catch; we recently updated the example to match the ABNF, but missed the prose. 

I wonder, however, if it's better to leave the disparity, to emphasise that keys are lc-only.

Cheers,


> On 30 Jan 2020, at 6:34 am, Kari Hurtta <[e-mail]> wrote:
> 
> 2.  Defining New Structured Headers
> https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-15#section-2
> 
> 
> |   The following parameters are defined:
> |   * A parameter whose name is "fooUrl", and whose value is a string
> |     (Section Y.Y of [RFCxxxx]), conveying the Foo URLs
> |     for the message. See below for processing requirements.
> |
> |   "fooUrl" contains a URI-reference (Section 4.1 of
> |   [RFC3986], Section 4.1). If its value is not a valid URI-reference,
> |   that URL MUST be ignored. If its value is a relative reference
> |   (Section 4.2 of [RFC3986]), it MUST be resolved (Section 5 of
> |   [RFC3986]) before being used.
> |
> |   For example:
> |
> |     Foo-Example: 2; foourl="https://foo.example.com/"
> 
> 
> Example is fixed to use foourl, but text still uses "fooUrl" (uppercase letter).
> 
> 3.1.2.  Parameters
> https://tools.ietf.org/html/draft-ietf-httpbis-header-structure-15#section-3.1.2
> 
> says that parameter name is lcalpha  -- therefore foourl
> 
> | The ABNF for parameters in HTTP headers is:
> |
> |   parameter     = ";" *SP param-name [ "=" param-value ]
> |   param-name    = key
> |   key           = lcalpha *( lcalpha / DIGIT / "_" / "-" / "." / "*" )
> |   lcalpha       = %x61-7A ; a-z
> |   param-value   = bare-item
> 
> / Kari Hurtta
> 
> 
> 
> 

--
Mark Nottingham   https://www.mnot.net/