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

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

1 edited


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

    r1555 r1562  
    460460  }
    461461  @bottom-center {
    462        content: "Expires September 4, 2012";
     462       content: "Expires September 5, 2012";
    463463  }
    464464  @bottom-right {
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2012-03-03">
     508      <meta name="dct.issued" scheme="ISO8601" content="2012-03-04">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <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.">
    537537            </tr>
    538538            <tr>
    539                <td class="left">Expires: September 4, 2012</td>
     539               <td class="left">Expires: September 5, 2012</td>
    540540               <td class="right">HP</td>
    541541            </tr>
    590590            <tr>
    591591               <td class="left"></td>
    592                <td class="right">March 3, 2012</td>
     592               <td class="right">March 4, 2012</td>
    593593            </tr>
    594594         </tbody>
    618618         in progress”.
    619619      </p>
    620       <p>This Internet-Draft will expire on September 4, 2012.</p>
     620      <p>This Internet-Draft will expire on September 5, 2012.</p>
    621621      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    622622      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    864864            <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
    865865               repeated for new parameters.
     866            </p>
     867         </li>
     868         <li>
     869            <p>Definitions of new schemes ought to define the treatment of unknown extension parameters. In general, a "must-ignore" rule
     870               is preferable over "must-understand", because otherwise it will be hard to introduce new parameters in the presence of legacy
     871               recipients. Furthermore, it's good to describe the policy for defining new parameters (such as "update the specification",
     872               or "use this registry").
    866873            </p>
    867874         </li>
    13281335      <p id="rfc.section.C.20.p.1">Closed issues: </p>
    13291336      <ul>
     1337         <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"
     1338         </li>
    13301339         <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"
    13311340         </li>
Note: See TracChangeset for help on using the changeset viewer.