idnits 2.17.1 draft-ietf-httpbis-authscheme-registrations-08.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 (September 25, 2013) is 3863 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 September 25, 2013 5 Expires: March 29, 2014 7 Initial Hypertext Transfer Protocol (HTTP) 8 Authentication Scheme Registrations 9 draft-ietf-httpbis-authscheme-registrations-08 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.8. 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 March 29, 2014. 48 Copyright Notice 49 Copyright (c) 2013 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 76 B.6. Since draft-ietf-httpbis-authscheme-registrations-05 . . . 5 77 B.7. Since draft-ietf-httpbis-authscheme-registrations-06 . . . 5 78 B.8. Since draft-ietf-httpbis-authscheme-registrations-07 . . . 5 80 1. Introduction 82 This document registers Hypertext Transfer Protocol (HTTP) 83 authentication schemes which have been defined in standards-track 84 RFCs before the IANA HTTP Authentication Scheme Registry was 85 established. 87 2. Security Considerations 89 There are no security considerations related to the registration 90 itself. 92 3. IANA Considerations 94 Appendix A provides initial registrations of HTTP authentication 95 schemes for the IANA HTTP Authentication Scheme registry at 96 (see Section 5.1 97 of [draft-ietf-httpbis-p7-auth]). 99 4. Normative References 101 [RFC2617] Franks, J., Hallam-Baker, P., 102 Hostetler, J., Lawrence, S., Leach, P., 103 Luotonen, A., and L. Stewart, "HTTP 104 Authentication: Basic and Digest Access 105 Authentication", RFC 2617, June 1999. 107 [RFC4559] Jaganathan, K., Zhu, L., and J. Brezak, 108 "SPNEGO-based Kerberos and NTLM HTTP 109 Authentication in Microsoft Windows", 110 RFC 4559, June 2006. 112 [RFC5849] Hammer-Lahav, E., "The OAuth 1.0 113 Protocol", RFC 5849, April 2010. 115 [RFC6750] Jones, M. and D. Hardt, "The OAuth 2.0 116 Authorization Framework: Bearer Token 117 Usage", RFC 6750, October 2012. 119 [draft-ietf-httpbis-p7-auth] Fielding, R., Ed. and J. Reschke, Ed., 120 "Hypertext Transfer Protocol 121 (HTTP/1.1): Authentication", 122 draft-ietf-httpbis-p7-auth-24 (work in 123 progress), September 2013. 125 Appendix A. Initial Registry Contents 127 +----------------+------------+-------------------------------------+ 128 | Authentication | Reference | Notes | 129 | Scheme Name | | | 130 +----------------+------------+-------------------------------------+ 131 | Basic | [RFC2617], | | 132 | | Section 2 | | 133 | Bearer | [RFC6750] | | 134 | Digest | [RFC2617], | | 135 | | Section 3 | | 136 | Negotiate | [RFC4559], | This authentication scheme violates | 137 | | Section 3 | both HTTP semantics (being | 138 | | | connection-oriented) and syntax | 139 | | | (use of syntax incompatible with | 140 | | | the WWW-Authenticate and | 141 | | | Authorization header field syntax). | 142 | OAuth | [RFC5849], | | 143 | | Section | | 144 | | 3.5.1 | | 145 +----------------+------------+-------------------------------------+ 147 Appendix B. Change Log (to be removed by RFC Editor before publication) 149 B.1. Since draft-ietf-httpbis-authscheme-registrations-00 151 Update draft-ietf-httpbis-p7-auth reference. 153 B.2. Since draft-ietf-httpbis-authscheme-registrations-01 155 Update draft-ietf-httpbis-p7-auth reference. 157 Closed issues: 159 o : "need to 160 reserve 'negotiate' as auth scheme name" 162 B.3. Since draft-ietf-httpbis-authscheme-registrations-02 164 Update draft-ietf-httpbis-p7-auth reference. 166 B.4. Since draft-ietf-httpbis-authscheme-registrations-03 168 Update draft-ietf-httpbis-p7-auth reference. 170 B.5. Since draft-ietf-httpbis-authscheme-registrations-04 172 Closed issues: 174 o : "add OAuth 175 auth scheme to initial registry contents" 177 Update draft-ietf-httpbis-p7-auth reference. Added OAuth 2.0 Bearer 178 scheme. 180 B.6. Since draft-ietf-httpbis-authscheme-registrations-05 182 Update draft-ietf-httpbis-p7-auth reference. 184 B.7. Since draft-ietf-httpbis-authscheme-registrations-06 186 Update draft-ietf-httpbis-p7-auth reference. 188 B.8. Since draft-ietf-httpbis-authscheme-registrations-07 190 Update draft-ietf-httpbis-p7-auth reference. 192 Author's Address 194 Julian F. Reschke 195 greenbytes GmbH 196 Hafenweg 16 197 Muenster, NW 48155 198 Germany 200 EMail: julian.reschke@greenbytes.de 201 URI: http://greenbytes.de/tech/webdav/