Changeset 1043 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

22/10/10 02:18:34 (12 years ago)

Author:

mnot@…

Message:

Remove RFC2119 from status code considerations; for #229.

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -660 +660 @@
 </t>
 <t>
-   New HTTP status codes &MUST; be defined in one of the categories defined
-   in <xref target="status.codes"/>. They &MUST-NOT; disallow a response body,
-   although they &MAY; mandate a zero-length response body. They &MAY; require
-   the presence of one or more particular HTTP response header(s).
-</t>
-<t>
-   Likewise, their definitions &MAY; specify that caches are allowed to use
+   HTTP status codes are generic; that is, they are potentially applicable to
+   any resource, not just one particular media type, "type" of resource, or
+   application. As such, it is preferred that new HTTP status codes be
+   registered in a document that isn't specific to a single application, so
+   that this is clear.
+</t>
+<t>
+   Definitions of new HTTP status codes typically explain the request
+   conditions that produce a response containing the status code (e.g.,
+   combinations of request headers and/or method(s)), along with any 
+   interactions with response headers (e.g., those that are required, those
+   that modify the semantics of the response).
+</t>
+<t>
+   New HTTP status codes are required to fall under one of the categories
+   defined in <xref target="status.codes"/>. To allow existing parsers to
+   properly handle them, new status codes cannot disallow a response body,
+   although they can mandate a zero-length response body. They can require the
+   presence of one or more particular HTTP response header(s).
+</t>
+<t>
+   Likewise, their definitions can specify that caches are allowed to use
    heuristics to determine their freshness (see &caching;; by default, it is
-   not allowed), and &MAY; define how to determine the resource which they
+   not allowed), and can define how to determine the resource which they
    carry a representation for (see <xref
    target="identifying.response.associated.with.representation"/>; by default,
    it is anonymous).
-</t>
-<t>
-   If there are particular request conditions that produce a response
-   containing the status code (e.g., request headers and/or method(s)), they
-   &SHOULD; be described in detail.
-</t>
-<t>
-   New HTTP status codes &SHOULD; be registered in a document that isn't
-   specific to a single application or other use of HTTP, so that it's clear that
-   they are not specific to that application or extension.
 </t>
 </section>