HTTP Immutable Responses
draft-ietf-httpbis-immutable-03

[Ballot comment]
Presumably, the "Note to Readers" section should be removed prior to publication. Please either remove it, add a note to it that it should be removed, or add an RFC editor note to this effect.

Trivial nits that aren't worth re-spinning the document before, but which you may wish to consider if you have any other reasons to revise it:

- Put quotation marks around "immutable" in the abstract.

- Replace "assures" with "insures" in the abstract (or rephase along the lines of "...assures the client that it never...").

- In the third paragraph of the Introduction, replace "Users that..." with "Users who..."

- The cache control registry currently contains section numbers for every citation. Would update section 4 to indicate: "[this document, section 2]"

[Ballot comment]
Presumably, the "Note to Readers" section should be removed prior to publication. Please either remove it, add a note to it that it should be removed, or add an RFC editor note to this effect.

Trivial nits that aren't worth re-spinning the document before, but which you may wish to consider if you have any other reasons to revise it:
- Put quotation marks around "immutable" in the abstract.
- Replace "assures" with "insures" in the abstract (or rephase along the lines of "...assures the client that it never...").
- In the third paragraph of the Introduction, replace "Users that..." with "Users who..."
- The cache control registry currently contains section numbers for every citation. Would update section 4 to indicate: "[this document, section 2]"

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-httpbis-immutable-03.txt. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

First, in the Hypertext Transfer Protocol (HTTP) Cache Directive Registry located at:

https://www.iana.org/assignments/http-cache-directives/

a single, new entry will be registered as follows:

Cache Directive: immutable
Reference: [ RFC-to-be ]

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC: httpbis-chairs@ietf.org, draft-ietf-httpbis-immutable@ietf.org, Mark Nottingham , mnot@mnot.net, ietf-http-wg@w3.org, alexey.melnikov@isode.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (HTTP Immutable Responses) to Proposed Standard


The IESG has received a request from the Hypertext Transfer Protocol WG
(httpbis) to consider the following document: - 'HTTP Immutable Responses'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-07-18. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


  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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-immutable/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-httpbis-immutable/ballot/


No IPR declarations have been submitted directly on this I-D.

# Shepherd Writeup for draft-ietf-httpbis-immutable

## 1. Summary

Mark Nottingham is the document shepherd; Alexey Melnikov is the responsible Area Director.

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.

The requested publication type is Proposed Standard.


## 2. Review and Consensus

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.


## 3. Intellectual Property

The author has stated that their direct, personal knowledge of any IPR related to this document
has already been disclosed, in conformance with BCPs 78 and 79.


## 4. Other Points

No other points.