W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: Submitted new I-D: Cache Digests for HTTP/2

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 18 Jan 2016 11:32:30 +0100
To: Stefan Eissing <stefan.eissing@greenbytes.de>, Martin Thomson <martin.thomson@gmail.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, Ilya Grigorik <ilya@igvita.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <569CBF3E.30509@gmx.de>
On 2016-01-18 11:19, Stefan Eissing wrote:
> +1 generic header parameter form.
>
> If I may make a proposal:
>
> Cache-Digest      = "Cache-Digest" ":" #digest-value
>    digest-value    = "<" base64url encoded digest ">" *( ";" digest-param )
>    digest-param    = ( ( "domain" "=" domain-value )
>                    | ( "path" "=" path-value )
>                    | ( "codec" "=" codec-value )
>                    | ( "update" ( "=" update-param ) )
>                    | ( digest-extension ) )
>
>   digest-extension = ( parmname [ "=" ( ptoken | quoted-string ) ] )
>
>   domain-value     =
>         authority              # defined in RFC3986
>         | wildcard-identifier  # defined in RFC 6125 6.4.3
>
>   path-value       = path-absolute    # defined in RFC3986 3.3
>
>   codec            = ( "GCS-SHA256" | ( ptoken | quoted-string ) )
> ...

I wouldn't use angle brackets here; let's leave them for use in places 
where the value is a URI (Link header field and several WebDAV header 
fields).

Just us token/quoted-sting here.

Also, do not wire parameter names into the ABNF; this mixes syntax with 
semantics.

Best regards, Julian
Received on Monday, 18 January 2016 10:33:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:10 UTC