Working group "nearly last call" on draft-ietf-http-v11-spec-03.txt

We're looking to finish HTTP/1.1 and have it approved as a Proposed
Standard before the Montreal meeting. To this end, the editorial group
has been working hard.

If you've been putting off reviewing the HTTP specification until
things settled down, now is the time: comments that come in after next
week will be very difficult to address.

What we'd really like is a careful reading and review, with
specific suggestions for improvements or clarifications. Consider this
"working group last call" with the following provisos:

We know in general a couple of things:

a) the HTTP 1.1 specification should describe the operation of the
protocol, not the implementation or administration policy of caches or
individual protocol elements. On the other hand, the specification
should be sufficiently self-contained to guide implementors on how
some piece of protocol *might* be implemented. Getting this kind of
wording right is hard.

b) there's still some issue that the editorial group was thinking of
as "terminology" having to do with resource/plain resource/negotiated
resource that turns out to really be a cache replacement policy issue
in the face of negotiated resources. Don't spend too much time on the
terminology section.

A subset of the editorial group meet at the WWW5 conference last week
a couple of times, and there'll be some more meetings to do group
editing later.

Section by section proposed revisions or deletions would be most
useful at this point, especially if they arrive before next Monday.

I expect there will be one or two more revisions before we declare
we're done, but it's time now to close out any issues for which there
are serious problems.

If you've raised some issues in the past that you don't think have
been either acknowledged or addressed and must be dealt with before
HTTP/1.1 becomes a Proposed Standard please say so ASAP.

Thanks,

Larry

Received on Monday, 13 May 1996 04:24:10 UTC