Changeset 1152 for draft-ietf-httpbis-content-disp/latest

Timestamp:

06/03/11 11:01:07 (11 years ago)

Author:

julian.reschke@…

Message:

use RFC2119 keywords when discussing handling the filename parameter (see #278)

Location:

draft-ietf-httpbis-content-disp/latest

Files:

• draft-ietf-httpbis-content-disp.html (modified) (7 diffs)
• draft-ietf-httpbis-content-disp.xml (modified) (3 diffs)

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

@@ -371 +371 @@
   } 
   @bottom-center {
-       content: "Expires September 2, 2011"; 
+       content: "Expires September 7, 2011"; 
   } 
   @bottom-right {
@@ -412 +412 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-content-disp-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-03-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-03-06">
       <meta name="dct.abstract" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
       <meta name="description" content="RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.">
@@ -430 +430 @@
                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
                </td>
-               <td class="right">March 1, 2011</td>
+               <td class="right">March 6, 2011</td>
             </tr>
             <tr>
@@ -437 +437 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 2, 2011</td>
+               <td class="left">Expires: September 7, 2011</td>
                <td class="right"></td>
             </tr>
@@ -466 +466 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 2, 2011.</p>
+      <p>This Internet-Draft will expire on September 7, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -638 +638 @@
          <li>
             <p>Many platforms do not use Internet Media Types (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>) to hold type information in the file system, but rely on filename extensions instead. Trusting the server-provided file
-               extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients need
-               to ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
+               extension could introduce a privilege escalation when the saved file is later opened (consider ".exe"). Thus, recipients <em class="bcp14">SHOULD</em> ensure that a file extension is used that is safe, optimally matching the media type of the received payload.
             </p>
          </li>
          <li>
-            <p>Recipients are advised to strip or replace character sequences that are known to cause confusion both in user interfaces and
-               in filenames, such as control characters and leading and trailing whitespace.
+            <p>Recipients <em class="bcp14">SHOULD</em> strip or replace character sequences that are known to cause confusion both in user interfaces and in filenames, such as control
+               characters and leading and trailing whitespace.
             </p>
          </li>
          <li>
             <p>Other aspects recipients need to be aware of are names that have a special meaning in the file system or in shell commands,
-               such as "." and "..", "~", "|", and also device names.
+               such as "." and "..", "~", "|", and also device names. Recipients <em class="bcp14">SHOULD</em> ignore or substitute names like these.
             </p>
          </li>
@@ -1019 +1018 @@
       <p id="rfc.section.E.10.p.2">Added appendix "Advice on Generating Content-Disposition Header Fields".</p>
       <h2 id="rfc.section.E.11"><a href="#rfc.section.E.11">E.11</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-content-disp-06</a></h2>
-      <p id="rfc.section.E.11.p.1">None yet.</p>
+      <p id="rfc.section.E.11.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278</a>&gt;: "conformance language"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.C">C</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.R">R</a> 

draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

@@ -262 +262 @@
       extensions instead. Trusting the server-provided file extension could
       introduce a privilege escalation when the saved file is later opened 
-      (consider ".exe"). Thus, recipients need to ensure that a file extension
+      (consider ".exe"). Thus, recipients &SHOULD; ensure that a file extension
       is used that is safe, optimally matching the media type of the received
       payload.
     </t></x:lt>
     <x:lt><t>
-      Recipients are advised to strip or replace character sequences that are
+      Recipients &SHOULD; strip or replace character sequences that are
       known to cause confusion both in user interfaces and in filenames, such as
       control characters and leading and trailing whitespace.
@@ -274 +274 @@
       Other aspects recipients need to be aware of are names that have a 
       special meaning in the file system or in shell commands, such as "." and "..",
-      "~", "|", and also device names.
+      "~", "|", and also device names. Recipients &SHOULD; ignore or substitute
+      names like these.
     </t></x:lt>
   </list>
@@ -1040 +1041 @@
 <section title="Since draft-ietf-httpbis-content-disp-06" anchor="changes.since.06">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols">
+     <t>
+      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/278"/>:
+      "conformance language"
+    </t>
+  </list>
 </t>
 </section>