idnits 2.17.1
draft-ietf-httpbis-authscheme-registrations-05.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
No issues found here.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
-- The document date (October 13, 2012) is 4212 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
** Obsolete normative reference: RFC 2617 (Obsoleted by RFC 7235, RFC 7615,
RFC 7616, RFC 7617)
** Obsolete normative reference: RFC 5849 (Obsoleted by RFC 6749)
Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 HTTPbis Working Group J. Reschke
3 Internet-Draft greenbytes
4 Intended status: Informational October 13, 2012
5 Expires: April 16, 2013
7 Initial Hypertext Transfer Protocol (HTTP)
8 Authentication Scheme Registrations
9 draft-ietf-httpbis-authscheme-registrations-05
11 Abstract
13 This document registers Hypertext Transfer Protocol (HTTP)
14 authentication schemes which have been defined in standards-track
15 RFCs before the IANA HTTP Authentication Scheme Registry was
16 established.
18 Editorial Note (To be removed by RFC Editor)
20 Discussion of this draft takes place on the HTTPBIS working group
21 mailing list (ietf-http-wg@w3.org), which is archived at
22 .
24 The current issues list is at and related documents
26 (including fancy diffs) can be found at
27 .
29 The changes in this draft are summarized in Appendix B.5.
31 Status of This Memo
33 This Internet-Draft is submitted in full conformance with the
34 provisions of BCP 78 and BCP 79.
36 Internet-Drafts are working documents of the Internet Engineering
37 Task Force (IETF). Note that other groups may also distribute
38 working documents as Internet-Drafts. The list of current Internet-
39 Drafts is at http://datatracker.ietf.org/drafts/current/.
41 Internet-Drafts are draft documents valid for a maximum of six months
42 and may be updated, replaced, or obsoleted by other documents at any
43 time. It is inappropriate to use Internet-Drafts as reference
44 material or to cite them other than as "work in progress."
46 This Internet-Draft will expire on April 16, 2013.
48 Copyright Notice
49 Copyright (c) 2012 IETF Trust and the persons identified as the
50 document authors. All rights reserved.
52 This document is subject to BCP 78 and the IETF Trust's Legal
53 Provisions Relating to IETF Documents
54 (http://trustee.ietf.org/license-info) in effect on the date of
55 publication of this document. Please review these documents
56 carefully, as they describe your rights and restrictions with respect
57 to this document. Code Components extracted from this document must
58 include Simplified BSD License text as described in Section 4.e of
59 the Trust Legal Provisions and are provided without warranty as
60 described in the Simplified BSD License.
62 Table of Contents
64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
65 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
66 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
67 4. Normative References . . . . . . . . . . . . . . . . . . . . . 3
68 Appendix A. Initial Registry Contents . . . . . . . . . . . . . . 4
69 Appendix B. Change Log (to be removed by RFC Editor before
70 publication) . . . . . . . . . . . . . . . . . . . . . 4
71 B.1. Since draft-ietf-httpbis-authscheme-registrations-00 . . . 4
72 B.2. Since draft-ietf-httpbis-authscheme-registrations-01 . . . 4
73 B.3. Since draft-ietf-httpbis-authscheme-registrations-02 . . . 4
74 B.4. Since draft-ietf-httpbis-authscheme-registrations-03 . . . 4
75 B.5. Since draft-ietf-httpbis-authscheme-registrations-04 . . . 5
77 1. Introduction
79 This document registers Hypertext Transfer Protocol (HTTP)
80 authentication schemes which have been defined in standards-track
81 RFCs before the IANA HTTP Authentication Scheme Registry was
82 established.
84 2. Security Considerations
86 There are no security considerations related to the registration
87 itself.
89 3. IANA Considerations
91 Appendix A provides initial registrations of HTTP authentication
92 schemes for the IANA HTTP Authentication Scheme registry at
93 (see Section 2.3
94 of [draft-ietf-httpbis-p7-auth]).
96 4. Normative References
98 [RFC2617] Franks, J., Hallam-Baker, P.,
99 Hostetler, J., Lawrence, S., Leach, P.,
100 Luotonen, A., and L. Stewart, "HTTP
101 Authentication: Basic and Digest Access
102 Authentication", RFC 2617, June 1999.
104 [RFC4559] Jaganathan, K., Zhu, L., and J. Brezak,
105 "SPNEGO-based Kerberos and NTLM HTTP
106 Authentication in Microsoft Windows",
107 RFC 4559, June 2006.
109 [RFC5849] Hammer-Lahav, E., "The OAuth 1.0
110 Protocol", RFC 5849, April 2010.
112 [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0
113 Authorization Framework: Bearer Token
114 Usage", RFC 6750, October 2012.
116 [draft-ietf-httpbis-p7-auth] Fielding, R., Ed. and J. Reschke, Ed.,
117 "Hypertext Transfer Protocol
118 (HTTP/1.1): Authentication",
119 draft-ietf-httpbis-p7-auth-21 (work in
120 progress), October 2012.
122 Appendix A. Initial Registry Contents
124 +----------------+------------+-------------------------------------+
125 | Authentication | Reference | Notes |
126 | Scheme Name | | |
127 +----------------+------------+-------------------------------------+
128 | Basic | [RFC2617], | |
129 | | Section 2 | |
130 | Bearer | [RFC6750] | |
131 | Digest | [RFC2617], | |
132 | | Section 3 | |
133 | Negotiate | [RFC4559], | This authentication scheme violates |
134 | | Section 3 | both HTTP semantics (being |
135 | | | connection-oriented) and syntax |
136 | | | (use of syntax incompatible with |
137 | | | the WWW-Authenticate and |
138 | | | Authorization header field syntax). |
139 | OAuth | [RFC5849], | |
140 | | Section | |
141 | | 3.5.1 | |
142 +----------------+------------+-------------------------------------+
144 Appendix B. Change Log (to be removed by RFC Editor before publication)
146 B.1. Since draft-ietf-httpbis-authscheme-registrations-00
148 Update draft-ietf-httpbis-p7-auth reference.
150 B.2. Since draft-ietf-httpbis-authscheme-registrations-01
152 Update draft-ietf-httpbis-p7-auth reference.
154 Closed issues:
156 o : "need to
157 reserve 'negotiate' as auth scheme name"
159 B.3. Since draft-ietf-httpbis-authscheme-registrations-02
161 Update draft-ietf-httpbis-p7-auth reference.
163 B.4. Since draft-ietf-httpbis-authscheme-registrations-03
165 Update draft-ietf-httpbis-p7-auth reference.
167 B.5. Since draft-ietf-httpbis-authscheme-registrations-04
169 Closed issues:
171 o : "add OAuth
172 auth scheme to initial registry contents"
174 Update draft-ietf-httpbis-p7-auth reference. Added OAuth 2.0 Bearer
175 scheme.
177 Author's Address
179 Julian F. Reschke
180 greenbytes GmbH
181 Hafenweg 16
182 Muenster, NW 48155
183 Germany
185 EMail: julian.reschke@greenbytes.de
186 URI: http://greenbytes.de/tech/webdav/