05/08/13 22:30:50 (9 years ago)

remove a bit of transport-dependent cruft from p2 definition of Expect, and editorial rephrasing

1 edited


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

    r2339 r2344  
    449449  }
    450450  @bottom-center {
    451        content: "Expires February 2, 2014";
     451       content: "Expires February 6, 2014";
    452452  }
    453453  @bottom-right {
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-08-01">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-08-05">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">August 1, 2013</td>
     522               <td class="right">August 5, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: February 2, 2014</td>
     525               <td class="left">Expires: February 6, 2014</td>
    526526               <td class="right"></td>
    527527            </tr>
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on February 2, 2014.</p>
     553      <p>This Internet-Draft will expire on February 6, 2014.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    21142114         or the server.
    21152115      </p>
    2116       <p id="rfc.section.6.5.p.2">When a client or server wishes to time-out it <em class="bcp14">SHOULD</em> issue a graceful close on the transport connection. Clients and servers <em class="bcp14">SHOULD</em> both constantly watch for the other side of the transport close, and respond to it as appropriate. If a client or server does
    2117          not detect the other side's close promptly it could cause unnecessary resource drain on the network.
     2116      <p id="rfc.section.6.5.p.2">A client or server that wishes to time-out <em class="bcp14">SHOULD</em> issue a graceful close on the connection. Implementations <em class="bcp14">SHOULD</em> constantly monitor open connections for a received closure signal and respond to it as appropriate, since prompt closure of
     2117         both sides of a connection enables allocated system resources to be reclaimed.
    21182118      </p>
    21192119      <p id="rfc.section.6.5.p.3">A client, server, or proxy <em class="bcp14">MAY</em> close the transport connection at any time. For example, a client might have started to send a new request at the same time
Note: See TracChangeset for help on using the changeset viewer.