HTTP Cache-Control Extensions for Stale Content
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: RFC Editor <firstname.lastname@example.org> Cc: The IESG <email@example.com>, <firstname.lastname@example.org>, email@example.com Subject: Re: Informational RFC to be: draft-nottingham-http-stale- controls-00.txt The IESG has no problem with the publication of 'HTTP Cache-Control Extensions for Stale Content' <draft-nottingham-http-stale-controls-00.txt> as an Informational RFC. The IESG would also like the RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18029&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Lisa Dusseault. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-nottingham-http-stale-controls-00.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
This is a submission to the RFC Editor. The HTTPBIS WG is aware of and has no problems with the publication of these HTTP Cache-Control header extensions in the independent stream. Recommendation is to let the RFC Editor publish this as it likes with no IESG note.