source: draft-ietf-httpbis-method-registrations/00/draft-ietf-httpbis-method-registrations-00.txt @ 1852

Last change on this file since 1852 was 322, checked in by julian.reschke@…, 15 years ago

prepare publication of draft 00 (regenerate deliverables)
File size: 10.0 KB
Line 
1
2
3
4Network Working Group                                         J. Reschke
5Internet-Draft                                                greenbytes
6Updates:                                                 August 29, 2008
7draft-ietf-httpbis-p2-semantics-04
8(if approved)
9Intended status: Informational
10Expires: March 2, 2009
11
12
13    Initial Hypertext Transfer Protocol (HTTP) Method Registrations
14               draft-ietf-httpbis-method-registrations-00
15
16Status of this Memo
17
18   By submitting this Internet-Draft, each author represents that any
19   applicable patent or other IPR claims of which he or she is aware
20   have been or will be disclosed, and any of which he or she becomes
21   aware will be disclosed, in accordance with Section 6 of BCP 79.
22
23   Internet-Drafts are working documents of the Internet Engineering
24   Task Force (IETF), its areas, and its working groups.  Note that
25   other groups may also distribute working documents as Internet-
26   Drafts.
27
28   Internet-Drafts are draft documents valid for a maximum of six months
29   and may be updated, replaced, or obsoleted by other documents at any
30   time.  It is inappropriate to use Internet-Drafts as reference
31   material or to cite them other than as "work in progress."
32
33   The list of current Internet-Drafts can be accessed at
34   http://www.ietf.org/ietf/1id-abstracts.txt.
35
36   The list of Internet-Draft Shadow Directories can be accessed at
37   http://www.ietf.org/shadow.html.
38
39   This Internet-Draft will expire on March 2, 2009.
40
41Abstract
42
43   This document registers those Hypertext Transfer ProtocolHypertext
44   Transfer Protocol (HTTP) methods which have been defined in
45   standards-track RFCs before the IANA HTTP Method Registry was
46   established.
47
48
49
50
51
52
53
54
55Reschke                   Expires March 2, 2009                 [Page 1]
56
57Internet-Draft          HTTP Method Registrations            August 2008
58
59
60Table of Contents
61
62   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
63   2.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
64   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3
65   4.  Normative References  . . . . . . . . . . . . . . . . . . . . . 3
66   Appendix A.  Initial Registry Contents  . . . . . . . . . . . . . . 4
67   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5
68   Intellectual Property and Copyright Statements  . . . . . . . . . . 6
69
70
71
72
73
74
75
76
77
78
79
80
81
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 March 2, 2009                 [Page 2]
112
113Internet-Draft          HTTP Method Registrations            August 2008
114
115
1161.  Introduction
117
118   This document registers those Hypertext Transfer ProtocolHypertext
119   Transfer Protocol (HTTP) methods which have been defined in
120   standards-track RFCs before the IANA HTTP Method Registry was
121   established.
122
123
1242.  Security Considerations
125
126   There are no security considerations related to the registration
127   itself.
128
129
1303.  IANA Considerations
131
132   Appendix A provides initial registrations of HTTP method names for
133   the IANA HTTP Method registry at
134   <http://www.iana.org/assignments/http-methods> (see Section 3.1 of
135   [draft-ietf-httpbis-p2-semantics]).
136
137
1384.  Normative References
139
140   [RFC2068]  Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
141              Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
142              RFC 2068, January 1997.
143
144   [RFC3253]  Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
145              Whitehead, "Versioning Extensions to WebDAV (Web
146              Distributed Authoring and Versioning)", RFC 3253,
147              March 2002.
148
149   [RFC3648]  Whitehead, J. and J. Reschke, Ed., "Web Distributed
150              Authoring and Versioning (WebDAV) Ordered Collections
151              Protocol", RFC 3648, December 2003.
152
153   [RFC3744]  Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
154              Distributed Authoring and Versioning (WebDAV) Access
155              Control Protocol", RFC 3744, May 2004.
156
157   [RFC4437]  Whitehead, J., Clemm, G., and J. Reschke, Ed., "Web
158              Distributed Authoring and Versioning (WebDAV)
159              Redirect Reference Resources", RFC 4437, March 2006.
160
161   [RFC4791]  Daboo, C., Desruisseaux, B., and L. Dusseault,
162              "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
163              March 2007.
164
165
166
167Reschke                   Expires March 2, 2009                 [Page 3]
168
169Internet-Draft          HTTP Method Registrations            August 2008
170
171
172   [RFC4918]  Dusseault, L., Ed., "HTTP Extensions for Web Distributed
173              Authoring and Versioning (WebDAV)", RFC 4918, June 2007.
174
175   [draft-ietf-httpbis-p2-semantics]
176              Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
177              Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
178              and J. Reschke, Ed., "HTTP/1.1, part 2: Message
179              Semantics", draft-ietf-httpbis-p2-semantics-04 (work in
180              progress), August 2008.
181
182
183Appendix A.  Initial Registry Contents
184
185   +-------------------+------+----------------------------------------+
186   | Method Name       | Safe | Reference                              |
187   +-------------------+------+----------------------------------------+
188   | ACL               | no   | [RFC3744], Section 8.1                 |
189   | BASELINE-CONTROL  | no   | [RFC3253], Section 12.6                |
190   | CHECKIN           | no   | [RFC3253], Section 4.4 and [RFC3253],  |
191   |                   |      | Section 9.4                            |
192   | CHECKOUT          | no   | [RFC3253], Section 4.3 and [RFC3253],  |
193   |                   |      | Section 8.8                            |
194   | COPY              | no   | [RFC4918], Section 9.8                 |
195   | LABEL             | no   | [RFC3253], Section 8.2                 |
196   | LINK              | no   | [RFC2068], Section 19.6.1.2            |
197   | LOCK              | no   | [RFC4918], Section 9.10                |
198   | MERGE             | no   | [RFC3253], Section 11.2                |
199   | MKAKTIVITY        | no   | [RFC3253], Section 13.5                |
200   | MKCALENDAR        | no   | [RFC4791], Section 5.3.1               |
201   | MKCOL             | no   | [RFC4918], Section 9.3                 |
202   | MKREDIRECTREF     | no   | [RFC4437], Section 6                   |
203   | MKWORKSPACE       | no   | [RFC3253], Section 6.3                 |
204   | MOVE              | no   | [RFC4918], Section 9.9                 |
205   | ORDERPATCH        | no   | [RFC3648], Section 7                   |
206   | PATCH             | no   | [RFC2068], Section 19.6.1.1            |
207   | PROPFIND          | yes  | [RFC4918], Section 9.1                 |
208   | PROPPATCH         | no   | [RFC4918], Section 9.2                 |
209   | REPORT            | yes  | [RFC3253], Section 3.6                 |
210   | UNCHECKOUT        | no   | [RFC3253], Section 4.5                 |
211   | UNLINK            | no   | [RFC2068], Section 19.6.1.3            |
212   | UNLOCK            | no   | [RFC4918], Section 9.11                |
213   | UPDATE            | no   | [RFC3253], Section 7.1                 |
214   | UPDATEREDIRECTREF | no   | [RFC4437], Section 7                   |
215   | VERSION-CONTROL   | no   | [RFC3253], Section 3.5                 |
216   +-------------------+------+----------------------------------------+
217
218
219
220
221
222
223Reschke                   Expires March 2, 2009                 [Page 4]
224
225Internet-Draft          HTTP Method Registrations            August 2008
226
227
228Author's Address
229
230   Julian F. Reschke
231   greenbytes GmbH
232   Hafenweg 16
233   Muenster, NW  48155
234   Germany
235
236   Email: julian.reschke@greenbytes.de
237   URI:   http://greenbytes.de/tech/webdav/
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279Reschke                   Expires March 2, 2009                 [Page 5]
280
281Internet-Draft          HTTP Method Registrations            August 2008
282
283
284Full Copyright Statement
285
286   Copyright (C) The IETF Trust (2008).
287
288   This document is subject to the rights, licenses and restrictions
289   contained in BCP 78, and except as set forth therein, the authors
290   retain all their rights.
291
292   This document and the information contained herein are provided on an
293   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
294   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
295   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
296   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
297   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
298   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
299
300
301Intellectual Property
302
303   The IETF takes no position regarding the validity or scope of any
304   Intellectual Property Rights or other rights that might be claimed to
305   pertain to the implementation or use of the technology described in
306   this document or the extent to which any license under such rights
307   might or might not be available; nor does it represent that it has
308   made any independent effort to identify any such rights.  Information
309   on the procedures with respect to rights in RFC documents can be
310   found in BCP 78 and BCP 79.
311
312   Copies of IPR disclosures made to the IETF Secretariat and any
313   assurances of licenses to be made available, or the result of an
314   attempt made to obtain a general license or permission for the use of
315   such proprietary rights by implementers or users of this
316   specification can be obtained from the IETF on-line IPR repository at
317   http://www.ietf.org/ipr.
318
319   The IETF invites any interested party to bring to its attention any
320   copyrights, patents or patent applications, or other proprietary
321   rights that may cover technology that may be required to implement
322   this standard.  Please address the information to the IETF at
323   ietf-ipr@ietf.org.
324
325
326
327
328
329
330
331
332
333
334
335Reschke                   Expires March 2, 2009                 [Page 6]
336
Note: See TracBrowser for help on using the repository browser.