Changeset 911 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

24/07/10 09:23:44 (11 years ago)

Author:

julian.reschke@…

Message:

Remove "Changes from RFC 2068" sections (see #220)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (2 diffs)

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

@@ -4884 +4884 @@
 </section>
 
-<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
-<t>
-   This specification has been carefully audited to correct and
-   disambiguate key word usage; RFC 2068 had many problems in respect to
-   the conventions laid out in <xref target="RFC2119"/>.
-</t>
-<t>
-   Transfer-coding and message lengths all interact in ways that
-   required fixing exactly when chunked encoding is used (to allow for
-   transfer encoding that might not be self delimiting); it was important
-   to straighten out exactly how message lengths are computed. (Sections
-   <xref target="transfer.codings" format="counter"/>, <xref target="message.body" format="counter"/>,
-   <xref target="header.content-length" format="counter"/>,
-   see also <xref target="Part5"/>)
-</t>
-<t>
-   The use and interpretation of HTTP version numbers has been clarified
-   by <xref target="RFC2145"/>. Require proxies to upgrade requests to highest protocol
-   version they support to deal with problems discovered in HTTP/1.0
-   implementations (<xref target="http.version"/>)
-</t>
-<t>
-   Quality Values of zero should indicate that "I don't want something"
-   to allow clients to refuse a representation. (<xref target="quality.values"/>)
-</t>
-<t>
-   Transfer-coding had significant problems, particularly with
-   interactions with chunked encoding. The solution is that transfer-codings
-   become as full fledged as content-codings. This involves
-   adding an IANA registry for transfer-codings (separate from content
-   codings), a new header field (TE) and enabling trailer headers in the
-   future. Transfer encoding is a major performance benefit, so it was
-   worth fixing <xref target="Nie1997"/>. TE also solves another, obscure, downward
-   interoperability problem that could have occurred due to interactions
-   between authentication trailers, chunked encoding and HTTP/1.0
-   clients.(Section
-   <xref target="transfer.codings" format="counter"/>,
-   <xref target="chunked.encoding" format="counter"/>,
-   <xref target="non-modifiable.headers" format="counter"/>,
-   and <xref target="header.te" format="counter"/>)
-</t>
-<t>
-  Proxies should be able to add Content-Length when appropriate.
-  (<xref target="non-modifiable.headers"/>)
-</t>
-</section>
-
 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
 <t>
@@ -5716 +5669 @@
       "HTTP(s) URI scheme definitions"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
+      "consider removing the 'changes from 2068' sections"
+    </t>
   </list>
 </t>