Get rid of "cacheable methods"

Fixes #54

draft-ietf-httpbis-cache-latest.xml

@@ -334,8 +334,7 @@
    A cache &MUST-NOT; store a response to any request, unless:
 </t>
 <ul>
-  <li><t>The request method is understood by the cache and defined as being
-  cacheable, and</t></li>
+  <li><t>The request method is understood by the cache, and</t></li>
   <li><t>the response status code is final (see <xref
   target="associating.response.to.request"/>), and</t></li>
   <li><t>the response status code is understood by the cache, and</t></li>
@@ -2297,6 +2296,7 @@
 <section title="Since draft-ietf-httpbis-cache-04" anchor="changes.since.04">
 <ul>
    <li>In <xref target="header.cache-control"/>, remove the registrations for stale-if-error and stale-while-revalidate which happened in RFC 7234 (<eref target="https://github.com/httpwg/http-core/issues/207"/>)</li>
+   <li>In <xref target="response.cacheability"/>, remove concept of "cacheable methods" in favor of prose (<eref target="https://github.com/httpwg/http-core/issues/54"/>)</li>
 </ul>
 </section>
 </section>

draft-ietf-httpbis-semantics-latest.xml

@@ -3927,16 +3927,18 @@ Content-Range: exampleunit 11.2-14.3/25
 </t>
 </section>
 
-<section title="Cacheable Methods" anchor="cacheable.methods">
-<iref item="cacheable" primary="true"/>
+<section title="Methods and Caching" anchor="cacheable.methods">
 <t>
-   Request methods can be defined as "<x:dfn
-   anchor="cacheable">cacheable</x:dfn>" to indicate that responses to them are
-   allowed to be stored for future reuse; for specific requirements see
-   <xref target="Caching"/>. In general, safe methods that do not depend on a current or
-   authoritative response are defined as cacheable; this specification defines
-   GET, HEAD, and POST as cacheable, although the overwhelming majority of 
-   cache implementations only support GET and HEAD.
+   For a cache to store and use a response, the associated method needs to
+   explicitly allow caching, and detail under what conditions a response can
+   be used to satisfy subsequent requests; a method definition which does not
+   do so cannot be cached. For additional requirements see <xref
+   target="Caching"/>.
+</t>
+<t>
+   This specification defines caching semantics for GET, HEAD, and POST,
+   although the overwhelming majority of cache implementations only support
+   GET and HEAD.
 </t>
 </section>
 </section>
@@ -11584,6 +11586,7 @@ Content-Encoding: gzip
   <li>In <xref target="header.content-type"/>, reference MIME Sniffing (<eref target="https://github.com/httpwg/http-core/issues/51"/>)</li>
   <li>In <xref target="abnf.extension"/>, simplify the #rule mapping for recipients (<eref target="https://github.com/httpwg/http-core/issues/164"/>, <eref target="https://www.rfc-editor.org/errata/eid5257"/>)</li>
   <li>In <xref target="OPTIONS"/>, remove misleading text about "extension" of HTTP is needed to define method payloads (<eref target="https://github.com/httpwg/http-core/issues/204"/>)</li>
+  <li>In <xref target="cacheable.methods"/>, remove concept of "cacheable methods" in favor of prose (<eref target="https://github.com/httpwg/http-core/issues/54"/>)</li>
 </ul>
 </section>
 </section>