idnits 2.17.1
draft-ietf-httpbis-method-registrations-15.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 :
----------------------------------------------------------------------------
== There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses
in the document. If these are example addresses, they should be changed.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (February 6, 2014) is 3731 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
** Obsolete normative reference: RFC 2068 (Obsoleted by RFC 2616)
Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--).
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 February 6, 2014
5 Expires: August 10, 2014
7 Initial Hypertext Transfer Protocol (HTTP) Method Registrations
8 draft-ietf-httpbis-method-registrations-15
10 Abstract
12 This document registers those Hypertext Transfer Protocol (HTTP)
13 methods which have been defined in RFCs before the IANA HTTP Method
14 Registry was established.
16 Editorial Note (To be removed by RFC Editor)
18 Discussion of this draft takes place on the HTTPBIS working group
19 mailing list (ietf-http-wg@w3.org), which is archived at
20 .
22 The current issues list is at and related documents
24 (including fancy diffs) can be found at
25 .
27 The changes in this draft are summarized in Appendix A.2.
29 Status of This Memo
31 This Internet-Draft is submitted in full conformance with the
32 provisions of BCP 78 and BCP 79.
34 Internet-Drafts are working documents of the Internet Engineering
35 Task Force (IETF). Note that other groups may also distribute
36 working documents as Internet-Drafts. The list of current Internet-
37 Drafts is at http://datatracker.ietf.org/drafts/current/.
39 Internet-Drafts are draft documents valid for a maximum of six months
40 and may be updated, replaced, or obsoleted by other documents at any
41 time. It is inappropriate to use Internet-Drafts as reference
42 material or to cite them other than as "work in progress."
44 This Internet-Draft will expire on August 10, 2014.
46 Copyright Notice
48 Copyright (c) 2014 IETF Trust and the persons identified as the
49 document authors. All rights reserved.
51 This document is subject to BCP 78 and the IETF Trust's Legal
52 Provisions Relating to IETF Documents
53 (http://trustee.ietf.org/license-info) in effect on the date of
54 publication of this document. Please review these documents
55 carefully, as they describe your rights and restrictions with respect
56 to this document. Code Components extracted from this document must
57 include Simplified BSD License text as described in Section 4.e of
58 the Trust Legal Provisions and are provided without warranty as
59 described in the Simplified BSD License.
61 Table of Contents
63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
64 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
65 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
66 4. Normative References . . . . . . . . . . . . . . . . . . . . . 4
67 Appendix A. Change Log (to be removed by RFC Editor before
68 publication) . . . . . . . . . . . . . . . . . . . . . 6
69 A.1. Since draft-ietf-httpbis-method-registrations-13 . . . . . 6
70 A.2. Since draft-ietf-httpbis-method-registrations-14 . . . . . 6
72 1. Introduction
74 This document registers those Hypertext Transfer Protocol (HTTP)
75 methods which have been defined in RFCs other than
76 [draft-ietf-httpbis-p2-semantics] before the IANA HTTP Method
77 Registry was established.
79 2. Security Considerations
81 There are no security considerations related to the registration
82 itself.
84 Security considerations applicable to the individual HTTP methods
85 ought to be discussed in the specifications that define them.
87 3. IANA Considerations
89 The table below provides registrations of HTTP method names to be
90 added to the IANA HTTP Method registry at
91 (see Section 8.1 of
92 [draft-ietf-httpbis-p2-semantics]).
94 +-------------------+------+------------+---------------------------+
95 | Method Name | Safe | Idempotent | Reference |
96 +-------------------+------+------------+---------------------------+
97 | ACL | no | yes | [RFC3744], Section 8.1 |
98 | BASELINE-CONTROL | no | yes | [RFC3253], Section 12.6 |
99 | BIND | no | yes | [RFC5842], Section 4 |
100 | CHECKIN | no | yes | [RFC3253], Section 4.4 |
101 | | | | and [RFC3253], Section |
102 | | | | 9.4 |
103 | CHECKOUT | no | yes | [RFC3253], Section 4.3 |
104 | | | | and [RFC3253], Section |
105 | | | | 8.8 |
106 | COPY | no | yes | [RFC4918], Section 9.8 |
107 | LABEL | no | yes | [RFC3253], Section 8.2 |
108 | LINK | no | yes | [RFC2068], Section |
109 | | | | 19.6.1.2 |
110 | LOCK | no | no | [RFC4918], Section 9.10 |
111 | MERGE | no | yes | [RFC3253], Section 11.2 |
112 | MKACTIVITY | no | yes | [RFC3253], Section 13.5 |
113 | MKCALENDAR | no | yes | [RFC4791], Section 5.3.1 |
114 | MKCOL | no | yes | [RFC4918], Section 9.3 |
115 | MKREDIRECTREF | no | yes | [RFC4437], Section 6 |
116 | MKWORKSPACE | no | yes | [RFC3253], Section 6.3 |
117 | MOVE | no | yes | [RFC4918], Section 9.9 |
118 | ORDERPATCH | no | yes | [RFC3648], Section 7 |
119 | PATCH | no | no | [RFC5789], Section 2 |
120 | PROPFIND | yes | yes | [RFC4918], Section 9.1 |
121 | PROPPATCH | no | yes | [RFC4918], Section 9.2 |
122 | REBIND | no | yes | [RFC5842], Section 6 |
123 | REPORT | yes | yes | [RFC3253], Section 3.6 |
124 | SEARCH | yes | yes | [RFC5323], Section 2 |
125 | UNBIND | no | yes | [RFC5842], Section 5 |
126 | UNCHECKOUT | no | yes | [RFC3253], Section 4.5 |
127 | UNLINK | no | yes | [RFC2068], Section |
128 | | | | 19.6.1.3 |
129 | UNLOCK | no | yes | [RFC4918], Section 9.11 |
130 | UPDATE | no | yes | [RFC3253], Section 7.1 |
131 | UPDATEREDIRECTREF | no | yes | [RFC4437], Section 7 |
132 | VERSION-CONTROL | no | yes | [RFC3253], Section 3.5 |
133 +-------------------+------+------------+---------------------------+
135 4. Normative References
137 [RFC2068] Fielding, R., Gettys, J., Mogul,
138 J., Nielsen, H., and T. Berners-
139 Lee, "Hypertext Transfer Protocol
140 -- HTTP/1.1", RFC 2068,
141 January 1997.
143 [RFC3253] Clemm, G., Amsden, J., Ellison,
144 T., Kaler, C., and J. Whitehead,
145 "Versioning Extensions to WebDAV
146 (Web Distributed Authoring and
147 Versioning)", RFC 3253,
148 March 2002.
150 [RFC3648] Whitehead, J. and J. Reschke, Ed.,
151 "Web Distributed Authoring and
152 Versioning (WebDAV) Ordered
153 Collections Protocol", RFC 3648,
154 December 2003.
156 [RFC3744] Clemm, G., Reschke, J., Sedlar,
157 E., and J. Whitehead, "Web
158 Distributed Authoring and
159 Versioning (WebDAV) Access Control
160 Protocol", RFC 3744, May 2004.
162 [RFC4437] Whitehead, J., Clemm, G., and J.
163 Reschke, Ed., "Web Distributed
164 Authoring and Versioning (WebDAV)
165 Redirect Reference Resources",
166 RFC 4437, March 2006.
168 [RFC4791] Daboo, C., Desruisseaux, B., and
169 L. Dusseault, "Calendaring
170 Extensions to WebDAV (CalDAV)",
171 RFC 4791, March 2007.
173 [RFC4918] Dusseault, L., Ed., "HTTP
174 Extensions for Web Distributed
175 Authoring and Versioning
176 (WebDAV)", RFC 4918, June 2007.
178 [RFC5323] Reschke, J., Ed., Reddy, S.,
179 Davis, J., and A. Babich, "Web
180 Distributed Authoring and
181 Versioning (WebDAV) SEARCH",
182 RFC 5323, November 2008.
184 [RFC5789] Dusseault, L. and J. Snell, "PATCH
185 Method for HTTP", RFC 5789,
186 March 2010.
188 [RFC5842] Clemm, G., Crawford, J., Reschke,
189 J., Ed., and J. Whitehead,
190 "Binding Extensions to Web
191 Distributed Authoring and
192 Versioning (WebDAV)", RFC 5842,
193 April 2010.
195 [draft-ietf-httpbis-p2-semantics] Fielding, R., Ed. and J. Reschke,
196 Ed., "Hypertext Transfer Protocol
197 (HTTP/1.1): Semantics and
198 Content",
199 draft-ietf-httpbis-p2-semantics-26
200 (work in progress), February 2014.
202 Appendix A. Change Log (to be removed by RFC Editor before publication)
204 Changes up to the IETF Last Call draft are summarized in .
208 A.1. Since draft-ietf-httpbis-method-registrations-13
210 Closed issues:
212 o : "registration
213 tables should be inside IANA considerations"
215 Clarified the IANA action to say "add".
217 Updated httpbis reference.
219 A.2. Since draft-ietf-httpbis-method-registrations-14
221 Closed issues:
223 o : "IESG ballot
224 on draft-ietf-httpbis-method-registrations-14"
226 Removed misleading statement about "standards-track" RFCs, as some of
227 the methods registered here indeed originate from Experimental RFCs,
228 and furthermore the new registry established in Section 8.1 of
229 [draft-ietf-httpbis-p2-semantics] uses "IETF Review".
231 Updated httpbis reference.
233 Author's Address
235 Julian F. Reschke
236 greenbytes GmbH
237 Hafenweg 16
238 Muenster, NW 48155
239 Germany
241 EMail: julian.reschke@greenbytes.de
242 URI: http://greenbytes.de/tech/webdav/