Merge pull request #354 from httpwg/mnot-144

Remove H1-specific connection-related requirements

draft-ietf-httpbis-semantics-latest.xml

@@ -382,7 +382,7 @@
 <t>
    HTTP is a stateless request/response protocol that operates by exchanging
    <x:dfn>messages</x:dfn> across a reliable transport- or session-layer
-   "<x:dfn>connection</x:dfn>" (<xref target="connection.management"/>).
+   "<x:dfn>connection</x:dfn>".
    An HTTP "<x:dfn>client</x:dfn>" is a program that establishes a connection
    to a server for the purpose of sending one or more HTTP requests.
    An HTTP "<x:dfn>server</x:dfn>" is a program that accepts connections
@@ -2206,10 +2206,6 @@ deployed and not likely to be registered in a timely manner otherwise.</t>
    access for resolution of the "http" (<xref target="http.uri"/>) and
    "https" (<xref target="https.uri"/>) schemes.
 </t>
-<t>
-   HTTP requirements regarding connection management are defined in
-   <xref target="connection.management"/>.
-</t>
 </section>
 
 <section title="Direct Authoritative Access" anchor="authoritative.access">
@@ -7743,14 +7739,6 @@ Expect: 100-continue
 <t>
    Since the 205 status code implies that no additional content will be
    provided, a server &MUST-NOT; generate a payload in a 205 response.
-   In other words, a server &MUST; do one of the following for a 205 response:
-   a) indicate a zero-length body for the response by including a
-   <x:ref>Content-Length</x:ref> header field with a value of 0;
-   b) indicate a zero-length payload for the response by including a
-   <x:ref>Transfer-Encoding</x:ref> header field with a value of chunked and
-   a message body consisting of a single chunk of zero-length; or,
-   c) close the connection immediately after sending the blank line
-   terminating the header section.
 </t>
 </section>
 
@@ -8444,9 +8432,6 @@ Content-Range: bytes 7000-7999/8000
    The <x:dfn>408 (Request Timeout)</x:dfn> status code indicates
    that the server did not receive a complete request message within the time
    that it was prepared to wait.
-   A server &SHOULD; send the "<x:ref>close</x:ref>" connection option
-   (<xref target="header.connection"/>) in the response, since 408 implies that the server
-   has decided to close the connection rather than continue waiting.
    If the client has an outstanding request in transit,
    the client &MAY; repeat that request on a new connection.
 </t>
@@ -8535,8 +8520,8 @@ Content-Range: bytes 7000-7999/8000
    The <x:dfn>413 (Payload Too Large)</x:dfn> status code indicates
    that the server is refusing to process a request because the request
    payload is larger than the server is willing or able to process.
-   The server &MAY; close the connection to prevent the client from continuing
-   the request.
+   The server &MAY; terminate the request, if the protocol version in use
+   allows it; otherwise, the server &MAY; close the connection.
 </t>
 <t>
    If the condition is temporary, the server &SHOULD; generate a
@@ -12454,6 +12439,7 @@ Content-Encoding: gzip
   <li>In <xref target="http.uri"/>, <xref target="https.uri"/>, <xref target="origin"/>, and <xref target="authoritative.access"/>, refactored schemes to define origin and authoritative access to an origin server for both "http" and "https" URIs to account for alternative services and secured connections that are not necessarily based on TCP (<eref target="https://github.com/httpwg/http-core/issues/237"/>)</li>
   <li>In <xref target="intro.requirements"/>, reference RFC 8174 as well (<eref target="https://github.com/httpwg/http-core/issues/303"/>)</li>
   <li>In <xref target="representations"/>, explicitly reference 206 as one of the status codes that provide representation data (<eref target="https://github.com/httpwg/http-core/issues/325"/>)</li>
+  <li>In <xref target="status.205"/>, <xref target="status.408"/>, and <xref target="status.413"/>, remove HTTP/1-specific, connection-related requirements (<eref target="https://github.com/httpwg/http-core/issues/144"/>)</li>
 </ul>
 </section>