Changeset 911 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

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

Author:

julian.reschke@…

Message:

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

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -598 +598 @@
    ranges), these are transmitted as a multipart message. The multipart
    media type used for this purpose is "multipart/byteranges" as defined
-   in <xref target="internet.media.type.multipart.byteranges"/>. See <xref target="changes.from.rfc.2068"/> for a compatibility issue.
+   in <xref target="internet.media.type.multipart.byteranges"/>.
 </t>
 <t>
@@ -1302 +1302 @@
 
 <section title="Compatibility with Previous Versions" anchor="compatibility">
-<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
-<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 may not be self delimiting); it was important
-   to straighten out exactly how message lengths are computed.
-   (<xref target="header.content-range"/>,
-   see also <xref target="Part1"/>)
-</t>
-<t>
-   There are situations where a server (especially a proxy) does not
-   know the full length of a response but is capable of serving a
-   byterange request. We therefore need a mechanism to allow byteranges
-   with a content-range not indicating the full length of the message.
-   (<xref target="header.content-range"/>)
-</t>
-<t>
-   Range request responses would become very verbose if all meta-data
-   were always returned; by allowing the server to only send needed
-   headers in a 206 response, this problem can be avoided.
-   (Section <xref target="status.206" format="counter"/>
-   and <xref target="header.if-range" format="counter"/>)
-</t>
-<t>
-   Fix problem with unsatisfiable range requests; there are two cases:
-   syntactic problems, and range doesn't exist in the document. The 416
-   status code was needed to resolve this ambiguity needed to indicate
-   an error for a byte range request that falls outside of the actual
-   contents of a document. (Section <xref target="status.416" format="counter"/>, <xref target="header.content-range" format="counter"/>)
-</t>
-</section>
-
 <section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
 <t>
@@ -1594 +1562 @@
       "Clarify entity / representation / variant terminology"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
+      "Clarify entity / representation / variant terminology"
+    </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
+      "consider removing the 'changes from 2068' sections"
+    </t>
   </list>
 </t>