- From: Keith Moore <moore@cs.utk.edu>
- Date: Fri, 01 Jun 2007 10:42:57 -0400
- To: Robert Sayre <sayrer@gmail.com>
- CC: "Roy T. Fielding" <fielding@gbiv.com>, Apps Discuss <discuss@apps.ietf.org>, Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
>> 2616 doesn't *need* to be revised at all. > > Disagree. The document is losing usefulness as a reference because it > is poorly structured, crawling with inaccuracies, and the net is full > of things that claim to be HTTP but aren't. is this because implementors tried to read the existing HTTP spec and failed to grasp it, or because they didn't even bother trying to read the spec? (seriously, at least for SMTP it's pretty obvious that a lot of authors of bad implementations never bothered to read the spec, they just copied what they saw someone else do. ) revising 2616 will help the implementors who are actually trying to get it right, and for that reason it is probably a worthwhile effort. but it won't do anything for the remainder of the implementations.
Received on Friday, 1 June 2007 14:43:33 UTC