Changeset 2211 for draft-ietf-httpbis/latest

Timestamp:

19/03/13 15:16:02 (10 years ago)

Author:

julian.reschke@…

Message:

tune terminology (see #439)

Location:

draft-ietf-httpbis/latest

Files:

• p7-auth.html (modified) (8 diffs)
• p7-auth.xml (modified) (4 diffs)

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires September 19, 2013"; 
+       content: "Expires September 20, 2013"; 
   } 
   @bottom-right {
@@ -489 +489 @@
       <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="2013-03-18">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-03-19">
       <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. This document defines the HTTP Authentication framework.">
@@ -517 +517 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">March 18, 2013</td>
+               <td class="right">March 19, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: September 19, 2013</td>
+               <td class="left">Expires: September 20, 2013</td>
                <td class="right"></td>
             </tr>
@@ -546 +546 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 19, 2013.</p>
+      <p>This Internet-Draft will expire on September 20, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -624 +624 @@
          Authentication" (<a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>).
       </p>
-      <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
-         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>.
+      <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
+         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>.
       </p>
       <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>
@@ -638 +638 @@
       <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>
       <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>
-      <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
+      <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
          and by a client to provide authentication information. It uses an extensible, case-insensitive token to identify the authentication
          scheme, followed by additional information necessary for achieving authentication via that scheme. The latter can either be
@@ -687 +687 @@
       <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>).
       </p>
-      <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
+      <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
          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
          authentication information. However, such additional mechanisms are not defined by this specification.
@@ -1132 +1132 @@
       <ul>
          <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"
+         </li>
+         <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"
          </li>
       </ul>

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

@@ -120 +120 @@
 <t>
    HTTP provides several &OPTIONAL; challenge-response authentication
-   mechanisms that can be used by a server to challenge a client request and
+   schemes that can be used by a server to challenge a client request and
    by a client to provide authentication information. The "basic" and "digest"
    authentication schemes continue to be specified in
@@ -158 +158 @@
   <x:anchor-alias value="credentials"/>
 <t>
-   HTTP provides a simple challenge-response authentication mechanism
+   HTTP provides a simple challenge-response authentication framework
    that can be used by a server to challenge a client request and by a
    client to provide authentication information. It uses an extensible,
@@ -261 +261 @@
 <t>
    The HTTP protocol does not restrict applications to this simple
-   challenge-response mechanism for access authentication. Additional
+   challenge-response framework for access authentication. Additional
    mechanisms &MAY; be used, such as encryption at the transport level or
    via message encapsulation, and with additional header fields
@@ -1166 +1166 @@
       "explain list expansion in ABNF appendices"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/439"/>:
+      "terminology: mechanism vs framework vs scheme"
+    </t>
   </list>
 </t>