Changeset 669 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

07/08/09 05:52:56 (13 years ago)

Author:

julian.reschke@…

Message:

Remove mentions of character encoding and language in description of Warning header (see #187)

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -1420 +1420 @@
 <t>
   Multiple warnings can be attached to a response (either by the origin server or by
-  a cache), including multiple warnings with the same code number. For example, a server
-  might provide the same warning with texts in both English and Basque.
+  a cache), including multiple warnings with the same code number, only differing
+  in warn-text.
 </t>
 <t>
   When this occurs, the user agent &SHOULD; inform the user of as many of them as
-  possible, in the order that they appear in the response. If it is not possible to inform
-  the user of all of the warnings, the user agent &SHOULD; follow these heuristics:
-  <list style="symbols">
-    <t>Warnings that appear early in the response take priority over those appearing later
-      in the response.</t>
-    <t>Warnings in the user's preferred character set take priority over warnings in other
-      character sets but with identical warn-codes and warn-agents.</t>
-  </list>
+  possible, in the order that they appear in the response.
 </t>
 <t>
@@ -1451 +1444 @@
       returned, in which case they &MUST; be.</t>
   </list>
-</t>
-<t>
-  The warn-text &SHOULD; be in a natural language and character set that is most likely
-  to be intelligible to the human user receiving the response. This decision can be based on
-  any available knowledge, such as the location of the cache or user, the Accept-Language
-  field in a request, the Content-Language field in a response, etc. The default language is
-  English and the default character set is ISO-8859-1 (<xref target="ISO-8859-1" />).
-</t>
-<t>
-  If a character set other than ISO-8859-1 is used, it &MUST; be encoded in the
-  warn-text using the method described in <xref target="RFC2047" />.
 </t>
 <t>
@@ -1662 +1644 @@
 <references title="Normative References">
 
-  <reference anchor="ISO-8859-1">
-    <front>
-      <title> Information technology -- 8-bit single-byte coded graphic character sets -- Part
-        1: Latin alphabet No. 1 </title>
-      <author>
-        <organization>International Organization for Standardization</organization>
-      </author>
-      <date year="1998" />
-    </front>
-    <seriesInfo name="ISO/IEC" value="8859-1:1998" />
-  </reference>
-
   <reference anchor="Part1">
     <front>
@@ -1942 +1912 @@
     <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
     <x:source basename="p7-auth" href="p7-auth.xml" />
-  </reference>
-
-  <reference anchor="RFC2047">
-    <front>
-      <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions)
-        Part Three: Message Header Extensions for Non-ASCII Text</title>
-      <author fullname="Keith Moore" initials="K." surname="Moore">
-        <organization>University of Tennessee</organization>
-        <address><email>moore@cs.utk.edu</email></address>
-      </author>
-      <date month="November" year="1996" />
-    </front>
-    <seriesInfo name="RFC" value="2047" />
   </reference>
 
@@ -2119 +2076 @@
   Clarify denial of service attack avoidance requirement.
   (<xref target="invalidation.after.updates.or.deletions" />)
+</t>
+<t>
+  Do not mention RFC 2047 encoding and multiple languages in Warning headers
+  anymore, as these aspects never were implemented. 
+  (<xref target="header.warning" />)
 </t>
 </section>
@@ -2346 +2308 @@
 <section anchor="changes.since.07" title="Since draft-ietf-httpbis-p6-cache-07">
 <t>
-  None.
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/187"/>:
+      "RFC2047 and warn-text"
+    </t>
+  </list>
 </t>
 </section>