Re: Informational RFC to be: draft-nottingham-http-stale-

The IESG <> Mon, 08 March 2010 21:18 UTC

Return-Path: <>
Received: by (Postfix, from userid 30) id 2DE233A6AAA; Mon, 8 Mar 2010 13:18:01 -0800 (PST)
X-idtracker: yes
From: The IESG <>
To: RFC Editor <>
Subject: Re: Informational RFC to be: draft-nottingham-http-stale-
Message-Id: <>
Date: Mon, 08 Mar 2010 13:18:01 -0800
Cc:, The IESG <>,
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Mar 2010 21:18:02 -0000


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 
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:

The process for such documents is described at

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.