Issue 152: range unit in Range header for custom ranges, was: issue 85 - range unit extensions from Julian Reschke on 2009-03-31 (ietf-http-wg@w3.org from January to March 2009)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 31 Mar 2009 13:36:35 +0200
To: HTTP Working Group <ietf-http-wg@w3.org>
CC: Mark Nottingham <mnot@mnot.net>
Message-ID: <49D20043.3060307@gmx.de>

Julian Reschke wrote:
> - Finally, in 
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-06.html#rfc.section.5.4.2>, 
> we have:
> 
>   Range   = "Range" ":" OWS Range-v
>   Range-v = byte-ranges-specifier
>           / other-ranges-specifier
>   other-ranges-specifier = 1*CHAR
> 
> Shouldn't other-ranges-specifier be something like:
> 
>   other-ranges-specifier = other-range-unit "=" 1*CHAR
> 
> ...so that a recipient can parse the unit name out of the header in a 
> generic way? (unless I'm missing something obvious, this should be 
> tracked as a separate issue)

Raised as <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/152>.

BR, Julian

Received on Tuesday, 31 March 2009 11:37:19 UTC