- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Tue, 27 Aug 1996 15:41:55 PDT
- To: dwm@shell.portal.com
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Writing MUST instead of SHOULD in the specification is not any way to force some vendor to either implement or not implement something. The spec should say what makes sense, not what is politically expedient. We should write "MUST" if non-compliance causes systems to break. I think there are too many "MUST"s in HTTP/1.1, but agreed to wait until the review for "Proposed" -> "Draft" to review them. I don't see any reason to add one here, though. Larry
Received on Tuesday, 27 August 1996 15:43:59 UTC