- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 4 Apr 2008 16:56:07 +1100
- To: HTTP Working Group <ietf-http-wg@w3.org>
BTW -- in case it isn't obvious, I'm trying to pick off a selection of (hopefully) easy design issues to close soon (e.g., #23, #28, #70, #63, #111, and now #67). If any of them get too difficult, we can pause discussion on that one to clear the queue first. Cheers, On 04/04/2008, at 3:39 PM, Mark Nottingham wrote: > > > * Recently closed issues: > > - i41: Security Considerations > - i99: Pipelining > > * Moved to editorial status: > > - i39: ETag uniqueness > - i51: HTTP-date vs. rfc1123-date > - i61: Redirection vs. Location > - i64: WS in quoted-pair > - i94: Reason-Phrase BNF > > * Current issues being considered for closure: > > The following issues may be closed soon. Please review the proposals > and speak up (either in favour or against) soon. > > - i23: no-store invalidation > - i24: Requiring Allow in 405 responses (updated proposal) > - i70: cacheability of status 303 > > * Current issues being discussed: > > - i20: Default charsets for text media types > - i28: Connection closing > - i63: RFC2047 encoded words > - i109: Clarify entity / representation / variant terminology > - i111: Use of TEXT > > See also: <http://www3.tools.ietf.org/wg/httpbis/trac/wiki/WikiStart> > > > > -- > Mark Nottingham http://www.mnot.net/ > > -- Mark Nottingham http://www.mnot.net/
Received on Friday, 4 April 2008 05:56:42 UTC