Changeset 1562 for draft-ietf-httpbis/latest/p7-auth.html

Timestamp:

04/03/12 20:08:07 (11 years ago)

Author:

julian.reschke@…

Message:

Recommend to consider treatment of extension parameters in new scheme definitions (see #334)

File:

• draft-ietf-httpbis/latest/p7-auth.html (modified) (7 diffs)

draft-ietf-httpbis/latest/p7-auth.html

@@ -460 +460 @@
   } 
   @bottom-center {
-       content: "Expires September 4, 2012"; 
+       content: "Expires September 5, 2012"; 
   } 
   @bottom-right {
@@ -506 +506 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-03-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
       <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, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework.">
@@ -537 +537 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 4, 2012</td>
+               <td class="left">Expires: September 5, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -590 +590 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 3, 2012</td>
+               <td class="right">March 4, 2012</td>
             </tr>
          </tbody>
@@ -618 +618 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 4, 2012.</p>
+      <p>This Internet-Draft will expire on September 5, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -864 +864 @@
             <p> <b>Note:</b> the fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
                repeated for new parameters.
+            </p>
+         </li>
+         <li>
+            <p>Definitions of new schemes ought to define the treatment of unknown extension parameters. In general, a "must-ignore" rule
+               is preferable over "must-understand", because otherwise it will be hard to introduce new parameters in the presence of legacy
+               recipients. Furthermore, it's good to describe the policy for defining new parameters (such as "update the specification",
+               or "use this registry").
             </p>
          </li>
@@ -1328 +1335 @@
       <p id="rfc.section.C.20.p.1">Closed issues: </p>
       <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/334">http://tools.ietf.org/wg/httpbis/trac/ticket/334</a>&gt;: "recipient behavior for new auth parameters"
+         </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/342">http://tools.ietf.org/wg/httpbis/trac/ticket/342</a>&gt;: "WWW-Authenticate ABNF slightly ambiguous"
          </li>