source: draft-ietf-httpbis-method-registrations/15/draft-ietf-httpbis-method-registrations-15.txt @ 2684

Last change on this file since 2684 was 2620, checked in by julian.reschke@…, 7 years ago

Draft 15

  • Property svn:eol-style set to native
File size: 12.3 KB
Line 
1
2
3
4HTTPbis Working Group                                         J. Reschke
5Internet-Draft                                                greenbytes
6Intended status: Informational                          February 6, 2014
7Expires: August 10, 2014
8
9
10    Initial Hypertext Transfer Protocol (HTTP) Method Registrations
11               draft-ietf-httpbis-method-registrations-15
12
13Abstract
14
15   This document registers those Hypertext Transfer Protocol (HTTP)
16   methods which have been defined in RFCs before the IANA HTTP Method
17   Registry was established.
18
19Editorial Note (To be removed by RFC Editor)
20
21   Discussion of this draft takes place on the HTTPBIS working group
22   mailing list (ietf-http-wg@w3.org), which is archived at
23   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
24
25   The current issues list is at <http://trac.tools.ietf.org/wg/httpbis/
26   trac/query?component=method-registrations> and related documents
27   (including fancy diffs) can be found at
28   <http://tools.ietf.org/wg/httpbis/>.
29
30   The changes in this draft are summarized in Appendix A.2.
31
32Status of This Memo
33
34   This Internet-Draft is submitted in full conformance with the
35   provisions of BCP 78 and BCP 79.
36
37   Internet-Drafts are working documents of the Internet Engineering
38   Task Force (IETF).  Note that other groups may also distribute
39   working documents as Internet-Drafts.  The list of current Internet-
40   Drafts is at http://datatracker.ietf.org/drafts/current/.
41
42   Internet-Drafts are draft documents valid for a maximum of six months
43   and may be updated, replaced, or obsoleted by other documents at any
44   time.  It is inappropriate to use Internet-Drafts as reference
45   material or to cite them other than as "work in progress."
46
47   This Internet-Draft will expire on August 10, 2014.
48
49Copyright Notice
50
51   Copyright (c) 2014 IETF Trust and the persons identified as the
52
53
54
55Reschke                  Expires August 10, 2014                [Page 1]
56
57Internet-Draft          HTTP Method Registrations          February 2014
58
59
60   document authors.  All rights reserved.
61
62   This document is subject to BCP 78 and the IETF Trust's Legal
63   Provisions Relating to IETF Documents
64   (http://trustee.ietf.org/license-info) in effect on the date of
65   publication of this document.  Please review these documents
66   carefully, as they describe your rights and restrictions with respect
67   to this document.  Code Components extracted from this document must
68   include Simplified BSD License text as described in Section 4.e of
69   the Trust Legal Provisions and are provided without warranty as
70   described in the Simplified BSD License.
71
72Table of Contents
73
74   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
75   2.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
76   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
77   4.  Normative References  . . . . . . . . . . . . . . . . . . . . . 4
78   Appendix A.  Change Log (to be removed by RFC Editor before
79                publication) . . . . . . . . . . . . . . . . . . . . . 6
80     A.1.  Since draft-ietf-httpbis-method-registrations-13  . . . . . 6
81     A.2.  Since draft-ietf-httpbis-method-registrations-14  . . . . . 6
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111Reschke                  Expires August 10, 2014                [Page 2]
112
113Internet-Draft          HTTP Method Registrations          February 2014
114
115
1161.  Introduction
117
118   This document registers those Hypertext Transfer Protocol (HTTP)
119   methods which have been defined in RFCs other than
120   [draft-ietf-httpbis-p2-semantics] before the IANA HTTP Method
121   Registry was established.
122
1232.  Security Considerations
124
125   There are no security considerations related to the registration
126   itself.
127
128   Security considerations applicable to the individual HTTP methods
129   ought to be discussed in the specifications that define them.
130
1313.  IANA Considerations
132
133   The table below provides registrations of HTTP method names to be
134   added to the IANA HTTP Method registry at
135   <http://www.iana.org/assignments/http-methods> (see Section 8.1 of
136   [draft-ietf-httpbis-p2-semantics]).
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167Reschke                  Expires August 10, 2014                [Page 3]
168
169Internet-Draft          HTTP Method Registrations          February 2014
170
171
172   +-------------------+------+------------+---------------------------+
173   | Method Name       | Safe | Idempotent | Reference                 |
174   +-------------------+------+------------+---------------------------+
175   | ACL               | no   | yes        | [RFC3744], Section 8.1    |
176   | BASELINE-CONTROL  | no   | yes        | [RFC3253], Section 12.6   |
177   | BIND              | no   | yes        | [RFC5842], Section 4      |
178   | CHECKIN           | no   | yes        | [RFC3253], Section 4.4    |
179   |                   |      |            | and [RFC3253], Section    |
180   |                   |      |            | 9.4                       |
181   | CHECKOUT          | no   | yes        | [RFC3253], Section 4.3    |
182   |                   |      |            | and [RFC3253], Section    |
183   |                   |      |            | 8.8                       |
184   | COPY              | no   | yes        | [RFC4918], Section 9.8    |
185   | LABEL             | no   | yes        | [RFC3253], Section 8.2    |
186   | LINK              | no   | yes        | [RFC2068], Section        |
187   |                   |      |            | 19.6.1.2                  |
188   | LOCK              | no   | no         | [RFC4918], Section 9.10   |
189   | MERGE             | no   | yes        | [RFC3253], Section 11.2   |
190   | MKACTIVITY        | no   | yes        | [RFC3253], Section 13.5   |
191   | MKCALENDAR        | no   | yes        | [RFC4791], Section 5.3.1  |
192   | MKCOL             | no   | yes        | [RFC4918], Section 9.3    |
193   | MKREDIRECTREF     | no   | yes        | [RFC4437], Section 6      |
194   | MKWORKSPACE       | no   | yes        | [RFC3253], Section 6.3    |
195   | MOVE              | no   | yes        | [RFC4918], Section 9.9    |
196   | ORDERPATCH        | no   | yes        | [RFC3648], Section 7      |
197   | PATCH             | no   | no         | [RFC5789], Section 2      |
198   | PROPFIND          | yes  | yes        | [RFC4918], Section 9.1    |
199   | PROPPATCH         | no   | yes        | [RFC4918], Section 9.2    |
200   | REBIND            | no   | yes        | [RFC5842], Section 6      |
201   | REPORT            | yes  | yes        | [RFC3253], Section 3.6    |
202   | SEARCH            | yes  | yes        | [RFC5323], Section 2      |
203   | UNBIND            | no   | yes        | [RFC5842], Section 5      |
204   | UNCHECKOUT        | no   | yes        | [RFC3253], Section 4.5    |
205   | UNLINK            | no   | yes        | [RFC2068], Section        |
206   |                   |      |            | 19.6.1.3                  |
207   | UNLOCK            | no   | yes        | [RFC4918], Section 9.11   |
208   | UPDATE            | no   | yes        | [RFC3253], Section 7.1    |
209   | UPDATEREDIRECTREF | no   | yes        | [RFC4437], Section 7      |
210   | VERSION-CONTROL   | no   | yes        | [RFC3253], Section 3.5    |
211   +-------------------+------+------------+---------------------------+
212
2134.  Normative References
214
215   [RFC2068]                          Fielding, R., Gettys, J., Mogul,
216                                      J., Nielsen, H., and T. Berners-
217                                      Lee, "Hypertext Transfer Protocol
218                                      -- HTTP/1.1", RFC 2068,
219                                      January 1997.
220
221
222
223Reschke                  Expires August 10, 2014                [Page 4]
224
225Internet-Draft          HTTP Method Registrations          February 2014
226
227
228   [RFC3253]                          Clemm, G., Amsden, J., Ellison,
229                                      T., Kaler, C., and J. Whitehead,
230                                      "Versioning Extensions to WebDAV
231                                      (Web Distributed Authoring and
232                                      Versioning)", RFC 3253,
233                                      March 2002.
234
235   [RFC3648]                          Whitehead, J. and J. Reschke, Ed.,
236                                      "Web Distributed Authoring and
237                                      Versioning (WebDAV) Ordered
238                                      Collections Protocol", RFC 3648,
239                                      December 2003.
240
241   [RFC3744]                          Clemm, G., Reschke, J., Sedlar,
242                                      E., and J. Whitehead, "Web
243                                      Distributed Authoring and
244                                      Versioning (WebDAV) Access Control
245                                      Protocol", RFC 3744, May 2004.
246
247   [RFC4437]                          Whitehead, J., Clemm, G., and J.
248                                      Reschke, Ed., "Web Distributed
249                                      Authoring and Versioning (WebDAV)
250                                      Redirect Reference Resources",
251                                      RFC 4437, March 2006.
252
253   [RFC4791]                          Daboo, C., Desruisseaux, B., and
254                                      L. Dusseault, "Calendaring
255                                      Extensions to WebDAV (CalDAV)",
256                                      RFC 4791, March 2007.
257
258   [RFC4918]                          Dusseault, L., Ed., "HTTP
259                                      Extensions for Web Distributed
260                                      Authoring and Versioning
261                                      (WebDAV)", RFC 4918, June 2007.
262
263   [RFC5323]                          Reschke, J., Ed., Reddy, S.,
264                                      Davis, J., and A. Babich, "Web
265                                      Distributed Authoring and
266                                      Versioning (WebDAV) SEARCH",
267                                      RFC 5323, November 2008.
268
269   [RFC5789]                          Dusseault, L. and J. Snell, "PATCH
270                                      Method for HTTP", RFC 5789,
271                                      March 2010.
272
273   [RFC5842]                          Clemm, G., Crawford, J., Reschke,
274                                      J., Ed., and J. Whitehead,
275                                      "Binding Extensions to Web
276
277
278
279Reschke                  Expires August 10, 2014                [Page 5]
280
281Internet-Draft          HTTP Method Registrations          February 2014
282
283
284                                      Distributed Authoring and
285                                      Versioning (WebDAV)", RFC 5842,
286                                      April 2010.
287
288   [draft-ietf-httpbis-p2-semantics]  Fielding, R., Ed. and J. Reschke,
289                                      Ed., "Hypertext Transfer Protocol
290                                      (HTTP/1.1): Semantics and
291                                      Content",
292                                      draft-ietf-httpbis-p2-semantics-26
293                                      (work in progress), February 2014.
294
295Appendix A.  Change Log (to be removed by RFC Editor before publication)
296
297   Changes up to the IETF Last Call draft are summarized in <http://
298   trac.tools.ietf.org/html/
299   draft-ietf-httpbis-method-registrations-13#appendix-B>.
300
301A.1.  Since draft-ietf-httpbis-method-registrations-13
302
303   Closed issues:
304
305   o  <http://tools.ietf.org/wg/httpbis/trac/ticket/514>: "registration
306      tables should be inside IANA considerations"
307
308   Clarified the IANA action to say "add".
309
310   Updated httpbis reference.
311
312A.2.  Since draft-ietf-httpbis-method-registrations-14
313
314   Closed issues:
315
316   o  <http://tools.ietf.org/wg/httpbis/trac/ticket/529>: "IESG ballot
317      on draft-ietf-httpbis-method-registrations-14"
318
319   Removed misleading statement about "standards-track" RFCs, as some of
320   the methods registered here indeed originate from Experimental RFCs,
321   and furthermore the new registry established in Section 8.1 of
322   [draft-ietf-httpbis-p2-semantics] uses "IETF Review".
323
324   Updated httpbis reference.
325
326
327
328
329
330
331
332
333
334
335Reschke                  Expires August 10, 2014                [Page 6]
336
337Internet-Draft          HTTP Method Registrations          February 2014
338
339
340Author's Address
341
342   Julian F. Reschke
343   greenbytes GmbH
344   Hafenweg 16
345   Muenster, NW  48155
346   Germany
347
348   EMail: julian.reschke@greenbytes.de
349   URI:   http://greenbytes.de/tech/webdav/
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391Reschke                  Expires August 10, 2014                [Page 7]
392
Note: See TracBrowser for help on using the repository browser.