Accepting pre-existing errata resolutions

Prior to this WG starting up, there was an HTTP errata list  
maintained at <>.

The issues against RFC2616 listed there are reflected as i1 to i18 in  
the current list < 

We've all been looking at them a while, but please have one more look  
through and make sure you're comfortable with the resolutions  
proposed; if I don't hear anything in the next two weeks, I think  
we'll have consensus on those resolutions*, and can move on.


* I'm primarily talking about the resolutions of the "design" issues  
-- i.e., those requiring some interpretation of the spec. Some of  
them may be overridden by later updates (e.g., i11 is probably going  
to be blown away by an updated reference to RFC3986); my interest for  
now is getting these out of the way, so don't worry about that for now.

Mark Nottingham

Received on Monday, 12 November 2007 12:59:28 UTC