idnits 2.17.1
draft-ietf-httpbis-conditional-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 2150 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 2616
(Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235)
-- Obsolete informational reference (is this intentional?): RFC 7232
(Obsoleted by RFC 9110)
Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 4 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 Conditional Requests
11 draft-ietf-httpbis-conditional-01
13 Abstract
15 The Hypertext Transfer Protocol (HTTP) is a stateless application-
16 level protocol for distributed, collaborative, hypertext information
17 systems. This document formerly defined HTTP conditional requests,
18 which has since been moved to the core HTTP Semantics document.
20 Editorial Note
22 This note is to be removed before publishing as an RFC.
24 Discussion of this draft takes place on the HTTP working group
25 mailing list (ietf-http-wg@w3.org), which is archived at
26 .
28 Working Group information can be found at ;
29 source code and issues list for this draft can be found at
30 .
32 The changes in this draft are summarized in Appendix A.
34 Status of This Memo
36 This Internet-Draft is submitted in full conformance with the
37 provisions of BCP 78 and BCP 79.
39 Internet-Drafts are working documents of the Internet Engineering
40 Task Force (IETF). Note that other groups may also distribute
41 working documents as Internet-Drafts. The list of current Internet-
42 Drafts is at https://datatracker.ietf.org/drafts/current/.
44 Internet-Drafts are draft documents valid for a maximum of six months
45 and may be updated, replaced, or obsoleted by other documents at any
46 time. It is inappropriate to use Internet-Drafts as reference
47 material or to cite them other than as "work in progress."
48 This Internet-Draft will expire on December 2, 2018.
50 Copyright Notice
52 Copyright (c) 2018 IETF Trust and the persons identified as the
53 document authors. All rights reserved.
55 This document is subject to BCP 78 and the IETF Trust's Legal
56 Provisions Relating to IETF Documents
57 (https://trustee.ietf.org/license-info) in effect on the date of
58 publication of this document. Please review these documents
59 carefully, as they describe your rights and restrictions with respect
60 to this document. Code Components extracted from this document must
61 include Simplified BSD License text as described in Section 4.e of
62 the Trust Legal Provisions and are provided without warranty as
63 described in the Simplified BSD License.
65 This document may contain material from IETF Documents or IETF
66 Contributions published or made publicly available before November
67 10, 2008. The person(s) controlling the copyright in some of this
68 material may not have granted the IETF Trust the right to allow
69 modifications of such material outside the IETF Standards Process.
70 Without obtaining an adequate license from the person(s) controlling
71 the copyright in such materials, this document may not be modified
72 outside the IETF Standards Process, and derivative works of it may
73 not be created outside the IETF Standards Process, except to format
74 it for publication as an RFC or to translate it into languages other
75 than English.
77 Table of Contents
79 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
80 2. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
81 2.1. Normative References . . . . . . . . . . . . . . . . . . 3
82 2.2. Informative References . . . . . . . . . . . . . . . . . 3
83 Appendix A. Changes from RFC 7232 . . . . . . . . . . . . . . . 4
84 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 4
85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
87 1. Introduction
89 Conditional requests are HTTP requests [Semantics] that include one
90 or more header fields indicating a precondition to be tested before
91 applying the method semantics to the target resource.
93 The entire content of this document (previously in [RFC2616] and
94 [RFC7232]) has been moved to [Semantics].
96 2. References
98 2.1. Normative References
100 [Semantics]
101 Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
102 Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-01
103 (work in progress), May 2018.
105 2.2. Informative References
107 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
108 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
109 Transfer Protocol -- HTTP/1.1", RFC 2616,
110 DOI 10.17487/RFC2616, June 1999,
111 .
113 [RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
114 Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
115 DOI 10.17487/RFC7232, June 2014,
116 .
118 Appendix A. Changes from RFC 7232
120 All content has been moved to [Semantics].
122 Acknowledgments
124 See Appendix "Acknowledgments" of [Semantics].
126 Authors' Addresses
128 Roy T. Fielding (editor)
129 Adobe
130 345 Park Ave
131 San Jose, CA 95110
132 USA
134 EMail: fielding@gbiv.com
135 URI: https://roy.gbiv.com/
137 Mark Nottingham (editor)
138 Fastly
140 EMail: mnot@mnot.net
141 URI: https://www.mnot.net/
143 Julian F. Reschke (editor)
144 greenbytes GmbH
145 Hafenweg 16
146 Muenster, NW 48155
147 Germany
149 EMail: julian.reschke@greenbytes.de
150 URI: https://greenbytes.de/tech/webdav/