W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 07 May 2010 16:24:47 +0200
Message-ID: <4BE422AF.9070701@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
On 06.05.2010 15:11, Julian Reschke wrote:
> (FYI)
>
> ...this reminded me that we haven't got an IANA registry for cache
> control directives -- so I just opened
> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/208>.
>
> Best regards, Julian
> ...

OK, I have added (1) registry requirements, and (2) IANA considerations:

(1), added to 3.2.3:

3.2.3.  Cache Control Extensions

    ...

    The HTTP Cache Directive Registry defines the name space for the
    cache directives.

    Registrations MUST include the following fields:

    o  Cache Directive Name

    o  Pointer to specification text

    Values to be added to this name space are subject to IETF review
    ([RFC5226], Section 4.1).

    The registry itself is maintained at
    <http://www.iana.org/assignments/http-cache-directives>.

(2)

5.1.  Cache Directive Registry

    The registration procedure for HTTP Cache Directives is defined by
    Section 3.2.3 of this document.

    The HTTP Cache Directive Registry should be created at
    <http://www.iana.org/assignments/http-cache-directives> and be
    populated with the registrations below:

    +------------------+------------------------------+
    | Cache Directive  | Reference                    |
    +------------------+------------------------------+
    | max-age          | Section 3.2.1, Section 3.2.2 |
    | max-stale        | Section 3.2.1                |
    | min-fresh        | Section 3.2.1                |
    | must-revalidate  | Section 3.2.2                |
    | no-cache         | Section 3.2.1, Section 3.2.2 |
    | no-store         | Section 3.2.1, Section 3.2.2 |
    | no-transform     | Section 3.2.1, Section 3.2.2 |
    | only-if-cached   | Section 3.2.1                |
    | private          | Section 3.2.2                |
    | proxy-revalidate | Section 3.2.2                |
    | public           | Section 3.2.2                |
    | s-maxage         | Section 3.2.2                |
    +------------------+------------------------------+


See: <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/817>

(We still need to figure out how to get RFC 5861's extensions into the 
registry.)

Feedback appreciated, Julian
Received on Friday, 7 May 2010 14:25:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:18 GMT