Changeset 1053

Timestamp:

Oct 23, 2010, 12:33:38 AM (9 years ago)

Author:

julian.reschke@…

Message:

Clarify trailer requirements (see #193)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (6 diffs)
• p1-messaging.xml (modified) (2 diffs)

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

@@ -404 +404 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2010-10-22">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-10-23">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.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.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 25, 2011</td>
+               <td class="left">Expires: April 26, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -488 +488 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 22, 2010</td>
+               <td class="right">October 23, 2010</td>
             </tr>
          </tbody>
@@ -516 +516 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 25, 2011.</p>
+      <p>This Internet-Draft will expire on April 26, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1635 +1635 @@
             described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section&nbsp;9.5</a>; or,
          </li>
-         <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient
-            could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin
-            server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
+         <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable
+            to the server where the field originated) without receiving it. In other words, the server that generated the header (often
+            but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded
+            along the path to the client.
          </li>
       </ol>
@@ -3469 +3470 @@
       </ul>
       <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p1-messaging-12</a></h2>
-      <p id="rfc.section.D.14.p.1">None yet.</p>
+      <p id="rfc.section.D.14.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>&gt;: "Trailer requirements"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> 

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

@@ -2086 +2086 @@
      acceptable in the transfer-coding of the  response, as described in
      <xref target="header.te"/>; or,</t>
-
-    <t>the server is the origin server for the response, the trailer
-     fields consist entirely of optional metadata, and the recipient
-     could use the message (in a manner acceptable to the origin server)
-     without receiving this metadata.  In other words, the origin server
-     is willing to accept the possibility that the trailer fields might
-     be silently discarded along the path to the client.</t>
+     
+    <t>the trailer fields consist entirely of optional metadata, and the
+    recipient could use the message (in a manner acceptable to the server where
+    the field originated) without receiving it. In other words, the server that
+    generated the header (often but not always the origin server) is willing to
+    accept the possibility that the trailer fields might be silently discarded
+    along the path to the client.</t>
   </list>
 </t>
@@ -5683 +5683 @@
 <section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols">
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>:
+      "Trailer requirements"
+    </t>
+  </list>
 </t>
 </section>