idnits 2.17.00 (12 Aug 2021)
/tmp/idnits49774/draft-ietf-httpbis-auth-01.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 :
----------------------------------------------------------------------------
** The document seems to lack a Security Considerations section.
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
== The document seems to contain a disclaimer for pre-RFC5378 work, but was
first submitted on or after 10 November 2008. The disclaimer is usually
necessary only for documents that revise or obsolete older RFCs, and that
take significant amounts of text from those RFCs. If you can contact all
authors of the source material and they are willing to grant the BCP78
rights to the IETF Trust, you can and should remove the disclaimer.
Otherwise, the disclaimer is needed and you can ignore this comment.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (May 31, 2018) is 1444 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
== Outdated reference: A later version (-19) exists of
draft-ietf-httpbis-semantics-01
-- Possible downref: Normative reference to a draft: ref. 'Semantics'
-- Obsolete informational reference (is this intentional?): RFC 2617
(Obsoleted by RFC 7235, RFC 7615, RFC 7616, RFC 7617)
Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 HTTP Working Group R. Fielding, Ed.
3 Internet-Draft Adobe
4 Intended status: Standards Track M. Nottingham, Ed.
5 Expires: December 2, 2018 Fastly
6 J. Reschke, Ed.
7 greenbytes
8 May 31, 2018
10 HTTP Authentication
11 draft-ietf-httpbis-auth-01
13 Abstract
15 The Hypertext Transfer Protocol (HTTP) is a stateless application-
16 level protocol for distributed, collaborative, hypermedia information
17 systems. This document formerly defined the HTTP Authentication
18 framework, which has since been moved to the core HTTP Semantics
19 document.
21 Editorial Note
23 This note is to be removed before publishing as an RFC.
25 Discussion of this draft takes place on the HTTP working group
26 mailing list (ietf-http-wg@w3.org), which is archived at
27 .
29 Working Group information can be found at ;
30 source code and issues list for this draft can be found at
31 .
33 The changes in this draft are summarized in Appendix A.
35 Status of This Memo
37 This Internet-Draft is submitted in full conformance with the
38 provisions of BCP 78 and BCP 79.
40 Internet-Drafts are working documents of the Internet Engineering
41 Task Force (IETF). Note that other groups may also distribute
42 working documents as Internet-Drafts. The list of current Internet-
43 Drafts is at https://datatracker.ietf.org/drafts/current/.
45 Internet-Drafts are draft documents valid for a maximum of six months
46 and may be updated, replaced, or obsoleted by other documents at any
47 time. It is inappropriate to use Internet-Drafts as reference
48 material or to cite them other than as "work in progress."
49 This Internet-Draft will expire on December 2, 2018.
51 Copyright Notice
53 Copyright (c) 2018 IETF Trust and the persons identified as the
54 document authors. All rights reserved.
56 This document is subject to BCP 78 and the IETF Trust's Legal
57 Provisions Relating to IETF Documents
58 (https://trustee.ietf.org/license-info) in effect on the date of
59 publication of this document. Please review these documents
60 carefully, as they describe your rights and restrictions with respect
61 to this document. Code Components extracted from this document must
62 include Simplified BSD License text as described in Section 4.e of
63 the Trust Legal Provisions and are provided without warranty as
64 described in the Simplified BSD License.
66 This document may contain material from IETF Documents or IETF
67 Contributions published or made publicly available before November
68 10, 2008. The person(s) controlling the copyright in some of this
69 material may not have granted the IETF Trust the right to allow
70 modifications of such material outside the IETF Standards Process.
71 Without obtaining an adequate license from the person(s) controlling
72 the copyright in such materials, this document may not be modified
73 outside the IETF Standards Process, and derivative works of it may
74 not be created outside the IETF Standards Process, except to format
75 it for publication as an RFC or to translate it into languages other
76 than English.
78 Table of Contents
80 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
81 2. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
82 2.1. Normative References . . . . . . . . . . . . . . . . . . 3
83 2.2. Informative References . . . . . . . . . . . . . . . . . 3
84 Appendix A. Changes from RFC 7235 . . . . . . . . . . . . . . . 4
85 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 4
86 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
88 1. Introduction
90 HTTP provides a general framework for access control and
91 authentication, via an extensible set of challenge-response
92 authentication schemes, which can be used by a server to challenge a
93 client request and by a client to provide authentication information.
95 The entire content of this document (previously in [RFC2617] and
96 [RFC7235]) has been moved to [Semantics].
98 2. References
100 2.1. Normative References
102 [Semantics]
103 Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
104 Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-01
105 (work in progress), May 2018.
107 2.2. Informative References
109 [RFC2617] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
110 Leach, P., Luotonen, A., and L. Stewart, "HTTP
111 Authentication: Basic and Digest Access Authentication",
112 RFC 2617, DOI 10.17487/RFC2617, June 1999,
113 .
115 [RFC7235] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
116 Protocol (HTTP/1.1): Authentication", RFC 7235,
117 DOI 10.17487/RFC7235, June 2014,
118 .
120 Appendix A. Changes from RFC 7235
122 All content has been moved to [Semantics].
124 Acknowledgments
126 See Appendix "Acknowledgments" of [Semantics].
128 Authors' Addresses
130 Roy T. Fielding (editor)
131 Adobe
132 345 Park Ave
133 San Jose, CA 95110
134 USA
136 EMail: fielding@gbiv.com
137 URI: https://roy.gbiv.com/
139 Mark Nottingham (editor)
140 Fastly
142 EMail: mnot@mnot.net
143 URI: https://www.mnot.net/
145 Julian F. Reschke (editor)
146 greenbytes GmbH
147 Hafenweg 16
148 Muenster, NW 48155
149 Germany
151 EMail: julian.reschke@greenbytes.de
152 URI: https://greenbytes.de/tech/webdav/