I think the web archiving community as well as the content-addressable
file-system community will be very interested in this. I have shared this
in the IPFS forum already and now I am going to share with the web
archiving community.
https://discuss.ipfs.io/t/http-immutable-responses-proposed-standard/905
Best,
On Mon, Aug 7, 2017 at 2:02 PM The IESG <iesg-secretary@ietf.org> wrote:
> The IESG has approved the following document:
> - 'HTTP Immutable Responses'
> (draft-ietf-httpbis-immutable-03.txt) as Proposed Standard
>
> This document is the product of the Hypertext Transfer Protocol Working
> Group.
>
> The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.
>
> A URL of this Internet Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-httpbis-immutable/
>
>
>
>
> Technical Summary
>
> The immutable HTTP response Cache-Control extension allows servers to
> identify resources that will
> not be updated during their freshness lifetime. This assures that a client
> never needs to
> revalidate a cached fresh resource to be certain it has not been modified.
>
> Working Group Summary
>
> Nothing interesting to report here.
>
> Document Quality
>
> This document quickly gained broad interest within the Working Group, and
> then support. It has been
> reviewed by a substantial number of participants, and implemented by
> Mozilla in Firefox, and by
> Facebook and others on the server side. Microsoft and Squid have stated
> that they are in the
> process of implementing.
>
> Personnel
>
> Mark Nottingham is the document shepherd; Alexey Melnikov is the
> responsible Area Director.
>
> --
--
Sawood Alam
Department of Computer Science
Old Dominion University
Norfolk VA 23529