* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 2211


Ignore:
Timestamp:
2013-03-19 08:16:02 (19 months ago)
Author:
julian.reschke@gmx.de
Message:

tune terminology (see #439)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.html

    r2206 r2211  
    449449  }  
    450450  @bottom-center { 
    451        content: "Expires September 19, 2013";  
     451       content: "Expires September 20, 2013";  
    452452  }  
    453453  @bottom-right { 
     
    489489      <meta name="dct.creator" content="Reschke, J. F."> 
    490490      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 
    491       <meta name="dct.issued" scheme="ISO8601" content="2013-03-18"> 
     491      <meta name="dct.issued" scheme="ISO8601" content="2013-03-19"> 
    492492      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    493493      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework."> 
     
    517517            <tr> 
    518518               <td class="left">Intended status: Standards Track</td> 
    519                <td class="right">March 18, 2013</td> 
     519               <td class="right">March 19, 2013</td> 
    520520            </tr> 
    521521            <tr> 
    522                <td class="left">Expires: September 19, 2013</td> 
     522               <td class="left">Expires: September 20, 2013</td> 
    523523               <td class="right"></td> 
    524524            </tr> 
     
    546546         in progress”. 
    547547      </p> 
    548       <p>This Internet-Draft will expire on September 19, 2013.</p> 
     548      <p>This Internet-Draft will expire on September 20, 2013.</p> 
    549549      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    550550      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    624624         Authentication" (<a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>). 
    625625      </p> 
    626       <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms that can be used by a server to challenge a client request and by a client to 
    627          provide authentication information. The "basic" and "digest" authentication schemes continue to be specified in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.2">RFC 2617</cite>. 
     626      <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication schemes that can be used by a server to challenge a client request and by a client to provide 
     627         authentication information. The "basic" and "digest" authentication schemes continue to be specified in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.2">RFC 2617</cite>. 
    628628      </p> 
    629629      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2> 
     
    638638      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="access.authentication.framework" href="#access.authentication.framework">Access Authentication Framework</a></h1> 
    639639      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="challenge.and.response" href="#challenge.and.response">Challenge and Response</a></h2> 
    640       <p id="rfc.section.2.1.p.1">HTTP provides a simple challenge-response authentication mechanism that can be used by a server to challenge a client request 
     640      <p id="rfc.section.2.1.p.1">HTTP provides a simple challenge-response authentication framework that can be used by a server to challenge a client request 
    641641         and by a client to provide authentication information. It uses an extensible, case-insensitive token to identify the authentication 
    642642         scheme, followed by additional information necessary for achieving authentication via that scheme. The latter can either be 
     
    687687      <p id="rfc.section.2.1.p.16">A server receiving credentials that are valid, but not adequate to gain access, ought to respond with the <a href="p2-semantics.html#status.403" class="smpl">403 (Forbidden)</a> status code (<a href="p2-semantics.html#status.403" title="403 Forbidden">Section 6.5.3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). 
    688688      </p> 
    689       <p id="rfc.section.2.1.p.17">The HTTP protocol does not restrict applications to this simple challenge-response mechanism for access authentication. Additional 
     689      <p id="rfc.section.2.1.p.17">The HTTP protocol does not restrict applications to this simple challenge-response framework for access authentication. Additional 
    690690         mechanisms <em class="bcp14">MAY</em> be used, such as encryption at the transport level or via message encapsulation, and with additional header fields specifying 
    691691         authentication information. However, such additional mechanisms are not defined by this specification. 
     
    11321132      <ul> 
    11331133         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>&gt;: "explain list expansion in ABNF appendices" 
     1134         </li> 
     1135         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/439">http://tools.ietf.org/wg/httpbis/trac/ticket/439</a>&gt;: "terminology: mechanism vs framework vs scheme" 
    11341136         </li> 
    11351137      </ul> 
  • draft-ietf-httpbis/latest/p7-auth.xml

    r2206 r2211  
    120120<t> 
    121121   HTTP provides several &OPTIONAL; challenge-response authentication 
    122    mechanisms that can be used by a server to challenge a client request and 
     122   schemes that can be used by a server to challenge a client request and 
    123123   by a client to provide authentication information. The "basic" and "digest" 
    124124   authentication schemes continue to be specified in 
     
    158158  <x:anchor-alias value="credentials"/> 
    159159<t> 
    160    HTTP provides a simple challenge-response authentication mechanism 
     160   HTTP provides a simple challenge-response authentication framework 
    161161   that can be used by a server to challenge a client request and by a 
    162162   client to provide authentication information. It uses an extensible, 
     
    261261<t> 
    262262   The HTTP protocol does not restrict applications to this simple 
    263    challenge-response mechanism for access authentication. Additional 
     263   challenge-response framework for access authentication. Additional 
    264264   mechanisms &MAY; be used, such as encryption at the transport level or 
    265265   via message encapsulation, and with additional header fields 
     
    11661166      "explain list expansion in ABNF appendices" 
    11671167    </t> 
     1168    <t> 
     1169      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/439"/>: 
     1170      "terminology: mechanism vs framework vs scheme" 
     1171    </t> 
    11681172  </list> 
    11691173</t> 
Note: See TracChangeset for help on using the changeset viewer.