Changeset 715 for draft-ietf-httpbis/latest/p1-messaging.html

Timestamp:

21/10/09 15:52:21 (13 years ago)

Author:

julian.reschke@…

Message:

Remove hard limit of two connections per server (see #131)

File:

• draft-ietf-httpbis/latest/p1-messaging.html (modified) (7 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -400 +400 @@
       <meta name="DC.Creator" content="Reschke, J. F.">
       <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-11">
+      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-10-21">
       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
       <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
@@ -437 +437 @@
          </tr>
          <tr>
-            <td class="header left">Expires: April 14, 2010</td>
+            <td class="header left">Expires: April 24, 2010</td>
             <td class="header right">H. Frystyk</td>
          </tr>
@@ -486 +486 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">October 11, 2009</td>
+            <td class="header right">October 21, 2009</td>
          </tr>
       </table>
@@ -510 +510 @@
       <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
       </p>
-      <p>This Internet-Draft will expire in April 14, 2010.</p>
+      <p>This Internet-Draft will expire in April 24, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1706 +1706 @@
       <p id="rfc.section.7.1.4.p.5">Servers <em class="bcp14">SHOULD</em> always respond to at least one request per connection, if at all possible. Servers <em class="bcp14">SHOULD NOT</em> close a connection in the middle of transmitting a response, unless a network or client failure is suspected.
       </p>
-      <p id="rfc.section.7.1.4.p.6">Clients that use persistent connections <em class="bcp14">SHOULD</em> limit the number of simultaneous connections that they maintain to a given server. A single-user client <em class="bcp14">SHOULD NOT</em> maintain more than 2 connections with any server or proxy. A proxy <em class="bcp14">SHOULD</em> use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines
-         are intended to improve HTTP response times and avoid congestion.
-      </p>
+      <p id="rfc.section.7.1.4.p.6">Clients (including proxies) <em class="bcp14">SHOULD</em> limit the number of simultaneous connections that they maintain to a given server (including proxies).
+      </p>
+      <p id="rfc.section.7.1.4.p.7">Previous revisions of HTTP gave a specific number of connections as a ceiling, but this was found to be impractical for many
+         applications. As a result, this specification does not mandate a particular maximum number of connections, but instead encourages
+         clients to be conservative when opening multiple connections.
+      </p>
+      <p id="rfc.section.7.1.4.p.8">In particular, while using multiple connections avoids the "head-of-line blocking" problem (whereby a request that takes significant
+         server-side processing and/or has a large payload can block subsequent requests on the same connection), each connection used
+         consumes server resources (sometimes significantly), and furthermore using multiple connections can cause undesirable side
+         effects in congested networks.
+      </p>
+      <p id="rfc.section.7.1.4.p.9">Note that servers might reject traffic that they deem abusive, including an excessive number of connections from a client.</p>
       <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a id="message.transmission.requirements" href="#message.transmission.requirements">Message Transmission Requirements</a></h2>
       <h3 id="rfc.section.7.2.1"><a href="#rfc.section.7.2.1">7.2.1</a>&nbsp;<a id="persistent.flow" href="#persistent.flow">Persistent Connections and Flow Control</a></h3>
@@ -2821 +2830 @@
          disallowed line folding in chunk extensions. (<a href="#chunked.encoding" title="Chunked Transfer Coding">Section&nbsp;6.2.1</a>)
       </p>
-      <p id="rfc.section.B.4.p.8">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;9.1</a>)
+      <p id="rfc.section.B.4.p.8">Remove hard limit of two connections per server. (<a href="#persistent.practical" title="Practical Considerations">Section&nbsp;7.1.4</a>)
+      </p>
+      <p id="rfc.section.B.4.p.9">Clarify exactly when close connection options must be sent. (<a href="#header.connection" id="rfc.xref.header.connection.8" title="Connection">Section&nbsp;9.1</a>)
       </p>
       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
@@ -3220 +3231 @@
       <ul>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/93">http://tools.ietf.org/wg/httpbis/trac/ticket/93</a>&gt;: "Repeating single-value headers"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/131">http://tools.ietf.org/wg/httpbis/trac/ticket/131</a>&gt;: "increase connection limit"
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/157">http://tools.ietf.org/wg/httpbis/trac/ticket/157</a>&gt;: "IP addresses in URLs"