source: draft-ietf-httpbis-authscheme-registrations/latest/auth48/rfc7236-to-be.xml @ 2694

Last change on this file since 2694 was 2694, checked in by julian.reschke@…, 7 years ago

add rfc7236-to-be (#553)

  • Property svn:mime-type set to text/xml
File size: 7.0 KB
Line 
1<?xml version="1.0" encoding="US-ASCII"?>
2<!-- v2 -->
3<!--
4    This XML document is the output of clean-for-DTD.xslt; a tool that strips
5    extensions to RFC2629(bis) from documents for processing with xml2rfc.
6-->
7<?xml-stylesheet type='text/xsl' href='../../draft-ietf-httpbis/myxml2rfc.xslt'?>
8<?rfc toc="yes"?>
9<?rfc symrefs="yes"?>
10<?rfc sortrefs="yes"?>
11<?rfc compact="yes"?>
12<?rfc comments="yes"?>
13<?rfc inline="yes"?>
14<?rfc subcompact="no"?>
15<?rfc rfcedstyle="yes"?>
16<!DOCTYPE rfc
17  PUBLIC "" "rfc2629.dtd">
18<rfc submissionType="IETF" ipr="trust200902" number="7236" category="info" consensus="yes">
19
20        <front>
21  <title abbrev="HTTP Authentication Scheme Registrations">Initial Hypertext Transfer Protocol (HTTP)
22  Authentication Scheme Registrations</title>
23
24  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
25    <organization abbrev="greenbytes">greenbytes GmbH</organization>
26    <address>
27      <postal>
28        <street>Hafenweg 16</street>
29        <city>Muenster</city><region>NW</region><code>48155</code>
30        <country>Germany</country>
31      </postal>
32      <email>julian.reschke@greenbytes.de</email>       
33      <uri>http://greenbytes.de/tech/webdav/</uri>     
34    </address>
35  </author>
36
37  <date month="May" year="2014"/>
38
39  <area>Applications</area>
40  <workgroup>HTTPbis Working Group</workgroup>
41
42<!-- [rfced] Please insert any keywords (beyond those that appear in
43the title) for use on http://www.rfc-editor.org/search.
44-->
45
46<keyword>example</keyword>
47
48 
49  <abstract>
50  <t>
51    This document registers Hypertext Transfer Protocol (HTTP)
52    authentication schemes that have been defined in RFCs
53    before the IANA HTTP Authentication Scheme Registry was established.
54  </t>
55  </abstract>
56 
57  </front>
58
59  <middle>
60
61<section title="Introduction" anchor="introduction">
62  <t>
63    This document registers Hypertext Transfer Protocol (HTTP)
64    authentication schemes that have been defined in RFCs
65    before the IANA HTTP Authentication Scheme Registry was established.
66  </t>
67</section> 
68 
69<section title="Security Considerations" anchor="security.considerations">
70  <t>
71    There are no security considerations related to the registration itself.
72  </t>
73  <t>
74    Security considerations applicable to the individual authentication schemes
75    ought to be discussed in the specifications that define them.
76  </t>
77</section> 
78
79<section title="IANA Considerations" anchor="iana.considerations">
80<t>
81  The registrations below have been
82  added to the IANA "HTTP Authentication Schemes" registry
83  at &lt;http://www.iana.org/assignments/http-authschemes&gt;
84  (see Section 5.1 of <xref target="RFC7235"/>).
85</t>
86<texttable align="left">
87
88<ttcol>Authentication Scheme Name</ttcol>
89<ttcol>Reference</ttcol>
90<ttcol>Notes</ttcol>
91
92<c>Basic</c><c><xref target="RFC2617"/>, Section 2</c><c/>
93<c>Bearer</c><c><xref target="RFC6750"/></c><c/>
94
95<c>Digest</c><c><xref target="RFC2617"/>, Section 3</c><c/>
96
97<c>Negotiate</c><c><xref target="RFC4559"/>, Section 3</c>
98<c>This authentication scheme violates both HTTP semantics (being connection-oriented)
99and syntax (use of syntax incompatible with the WWW-Authenticate and Authorization header field
100syntax).</c>
101
102<c>OAuth</c><c><xref target="RFC5849"/>, Section 3.5.1</c><c/>
103<!-- [rfced] RFC 5849 has been obsoleted by RFC 6749.  Should the reference in
104the table and in the IANA registry be updated to point to RFC 6749?
105
106   | OAuth          | [RFC5849], |
107   |                | Section    |
108   |                | 3.5.1      |
109
110-->
111
112</texttable>
113</section> 
114  </middle>
115  <back>
116 
117<references title="Normative References">
118
119<!--Companion document; draft-ietf-httpbis-p7-auth  -->
120
121<reference anchor="RFC7235">
122  <front>
123    <title>Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
124    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
125      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
126      <address><email>fielding@gbiv.com</email></address>
127    </author>
128    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
129      <organization abbrev="greenbytes">greenbytes GmbH</organization>
130      <address><email>julian.reschke@greenbytes.de</email></address>
131    </author>
132    <date month="May" year="2014"/>
133  </front>
134  <seriesInfo name="RFC" value="7235"/>
135 
136</reference>
137
138<reference anchor="RFC2617">
139  <front>
140    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
141    <author initials="J." surname="Franks" fullname="John Franks">
142      <organization>Northwestern University, Department of Mathematics</organization>
143      <address><email>john@math.nwu.edu</email></address>
144    </author>
145    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
146      <organization>Verisign Inc.</organization>
147      <address><email>pbaker@verisign.com</email></address>
148    </author>
149    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
150      <organization>AbiSource, Inc.</organization>
151      <address><email>jeff@AbiSource.com</email></address>
152    </author>
153    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
154      <organization>Agranat Systems, Inc.</organization>
155      <address><email>lawrence@agranat.com</email></address>
156    </author>
157    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
158      <organization>Microsoft Corporation</organization>
159      <address><email>paulle@microsoft.com</email></address>
160    </author>
161    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
162      <organization>Netscape Communications Corporation</organization>
163    </author>
164    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
165      <organization>Open Market, Inc.</organization>
166      <address><email>stewart@OpenMarket.com</email></address>
167    </author>
168    <date month="June" year="1999"/>
169  </front>
170  <seriesInfo name="RFC" value="2617"/>
171</reference>
172
173<reference anchor="RFC4559">
174  <front>
175    <title>SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows</title>
176    <author initials="K." surname="Jaganathan" fullname="K. Jaganathan"/>
177    <author initials="L." surname="Zhu" fullname="L. Zhu"/>
178    <author initials="J." surname="Brezak" fullname="J. Brezak"/>
179    <date year="2006" month="June"/>
180  </front>
181  <seriesInfo name="RFC" value="4559"/>
182</reference>
183
184<reference anchor="RFC5849">
185  <front>
186    <title>The OAuth 1.0 Protocol</title>
187    <author initials="E." surname="Hammer-Lahav" fullname="Eran Hammer-Lahav"/>
188    <date year="2010" month="April"/>
189  </front>
190  <seriesInfo name="RFC" value="5849"/>
191</reference>
192
193<reference anchor="RFC6750">
194  <front>
195    <title>The OAuth 2.0 Authorization Framework: Bearer Token Usage</title>
196    <author initials="M." surname="Jones" fullname="Michael B. Jones"/>
197    <author initials="D." surname="Hardt" fullname="Dick Hardt"/>
198    <date year="2012" month="October"/>
199  </front>
200  <seriesInfo name="RFC" value="6750"/>
201</reference>
202
203</references>
204 
205<!--<references title="Informative References">
206</references>-->
207
208  </back>
209
210</rfc>
Note: See TracBrowser for help on using the repository browser.