Ignore:
Timestamp:
Mar 19, 2013, 8:16:02 AM (7 years ago)
Author:
julian.reschke@…
Message:

tune terminology (see #439)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • 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.