RE: RFC2616 errata: HTTP-Version should be case-sensitive

Perhaps there's some misunderstanding about the purpose of
the "errata" page. It doesn't really matter whether it's
a transcription error or a semantic change to the document,
we should document, in the HTTP "errata", ways in which the
spec is inconsistent with widely deployed HTTP implementations.

> To summarize, I think that the change you propose makes perfect sense,
> but I disagree that it is an errata. If the consensus is that changes
> to reflect todays interoperability problems are appropriate, a lot
> more similar changes should be done.

It's reasonable to document these, and not to worry too much about
whether they are "changes" in intent or "changes" in specification
to match what was actually the original intent.

When the HTTP spec is revised, we can figure out how to
word the change list.

In general, unless there's some strong design reason to do otherwise,
we should change the spec to match what's implemented.

Larry

Received on Wednesday, 18 September 2002 01:10:02 UTC