Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme Registrations
draft-ietf-httpbis-authscheme-registrations-06

Abstract

This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established.

Editorial Note (To be removed by RFC Editor)

Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at http://lists.w3.org/Archives/Public/ietf-http-wg/.

The current issues list is at http://trac.tools.ietf.org/wg/httpbis/trac/query?component=authscheme-registrations and related documents (including fancy diffs) can be found at http://tools.ietf.org/wg/httpbis/.

The changes in this draft are summarized in Appendix B.6.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on August 27, 2013.

Copyright Notice

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

1. Introduction
2. Security Considerations
3. IANA Considerations
4. Normative References
Appendix A. Initial Registry Contents
Appendix B. Change Log (to be removed by RFC Editor before publication)
B.1. Since draft-ietf-httpbis-authscheme-registrations-00
B.2. Since draft-ietf-httpbis-authscheme-registrations-01
B.3. Since draft-ietf-httpbis-authscheme-registrations-02
B.4. Since draft-ietf-httpbis-authscheme-registrations-03
B.5. Since draft-ietf-httpbis-authscheme-registrations-04
B.6. Since draft-ietf-httpbis-authscheme-registrations-05
Author's Address

1. Introduction

This document registers Hypertext Transfer Protocol (HTTP) authentication schemes which have been defined in standards-track RFCs before the IANA HTTP Authentication Scheme Registry was established.

2. Security Considerations

There are no security considerations related to the registration itself.

3. IANA Considerations

Appendix A provides initial registrations of HTTP authentication schemes for the IANA HTTP Authentication Scheme registry at http://www.iana.org/assignments/http-authschemes (see Section 2.3 of [draft-ietf-httpbis-p7-auth]).

4. Normative References

[draft-ietf-httpbis-p7-auth]	Fielding, R. and J. F. Reschke, "Hypertext Transfer Protocol (HTTP/1.1): Authentication", Internet-Draft draft-ietf-httpbis-p7-auth-22, February 2013.
[RFC2617]	Franks, J., Hallam-Baker, P.M., Hostetler, J.L., Lawrence, S.D., Leach, P.J., Luotonen, A. and L. Stewart, "HTTP Authentication: Basic and Digest Access Authentication", RFC 2617, June 1999.
[RFC4559]	Jaganathan, K., Zhu, L. and J. Brezak, "SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows", RFC 4559, June 2006.
[RFC5849]	Hammer-Lahav, E., "The OAuth 1.0 Protocol", RFC 5849, April 2010.
[RFC6750]	Jones, M. and D. Hardt, "The OAuth 2.0 Authorization Framework: Bearer Token Usage", RFC 6750, October 2012.

Appendix A. Initial Registry Contents

Authentication Scheme Name	Reference	Notes
Basic	[RFC2617], Section 2
Bearer	[RFC6750]
Digest	[RFC2617], Section 3
Negotiate	[RFC4559], Section 3	This authentication scheme violates both HTTP semantics (being connection-oriented) and syntax (use of syntax incompatible with the WWW-Authenticate and Authorization header field syntax).
OAuth	[RFC5849], Section 3.5.1