|Network Working Group||J. F. Reschke|
|<draft-ietf-httpbis-method-registrations-latest>||October 11, 2008|
|Updates: draft-ietf-httpbis-p2-semantics-04 (if approved)|
|Intended status: Informational|
|Expires: April 2009|
Initial Hypertext Transfer Protocol (HTTP) Method Registrations
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.
The list of current Internet-Drafts can be accessed at <http://www.ietf.org/ietf/1id-abstracts.txt>.
The list of Internet-Draft Shadow Directories can be accessed at <http://www.ietf.org/shadow.html>.
This Internet-Draft will expire in April 2009.
This document registers those Hypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established.
This document registers those Hypertext Transfer ProtocolHypertext Transfer Protocol (HTTP) methods which have been defined in standards-track RFCs before the IANA HTTP Method Registry was established.
There are no security considerations related to the registration itself.
Appendix A provides initial registrations of HTTP method names for the IANA HTTP Method registry at <http://www.iana.org/assignments/http-methods> (see Section 3.1 of [draft-ietf-httpbis-p2-semantics]).
|[RFC2068]||Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1”, RFC 2068, January 1997.|
|[RFC3253]||Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. Whitehead, “Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)”, RFC 3253, March 2002.|
|[RFC3648]||Whitehead, J. and J. F. Reschke, Ed., “Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol”, RFC 3648, December 2003.|
|[RFC3744]||Clemm, G., Reschke, J. F., Sedlar, E., and J. Whitehead, “Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol”, RFC 3744, May 2004.|
|[RFC4437]||Whitehead, J., Clemm, G., and J. F. Reschke, Ed., “Web Distributed Authoring and Versioning (WebDAV) Redirect Reference Resources”, RFC 4437, March 2006.|
|[RFC4791]||Daboo, C., Desruisseaux, B., and L.M. Dusseault, “Calendaring Extensions to WebDAV (CalDAV)”, RFC 4791, March 2007.|
|[RFC4918]||Dusseault, L., Ed., “HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)”, RFC 4918, June 2007.|
|[draft-ietf-httpbis-p2-semantics]||Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., and J. F. Reschke, Ed., “HTTP/1.1, part 2: Message Semantics”, Internet-Draft draft-ietf-httpbis-p2-semantics-04 (work in progress), August 2008.|
|ACL||no||[RFC3744], Section 8.1|
|BASELINE-CONTROL||no||[RFC3253], Section 12.6|
|CHECKIN||no||[RFC3253], Section 4.4 and [RFC3253], Section 9.4|
|CHECKOUT||no||[RFC3253], Section 4.3 and [RFC3253], Section 8.8|
|COPY||no||[RFC4918], Section 9.8|
|LABEL||no||[RFC3253], Section 8.2|
|LINK||no||[RFC2068], Section 188.8.131.52|
|LOCK||no||[RFC4918], Section 9.10|
|MERGE||no||[RFC3253], Section 11.2|
|MKAKTIVITY||no||[RFC3253], Section 13.5|
|MKCALENDAR||no||[RFC4791], Section 5.3.1|
|MKCOL||no||[RFC4918], Section 9.3|
|MKREDIRECTREF||no||[RFC4437], Section 6|
|MKWORKSPACE||no||[RFC3253], Section 6.3|
|MOVE||no||[RFC4918], Section 9.9|
|ORDERPATCH||no||[RFC3648], Section 7|
|PATCH||no||[RFC2068], Section 184.108.40.206|
|PROPFIND||yes||[RFC4918], Section 9.1|
|PROPPATCH||no||[RFC4918], Section 9.2|
|REPORT||yes||[RFC3253], Section 3.6|
|UNCHECKOUT||no||[RFC3253], Section 4.5|
|UNLINK||no||[RFC2068], Section 220.127.116.11|
|UNLOCK||no||[RFC4918], Section 9.11|
|UPDATE||no||[RFC3253], Section 7.1|
|UPDATEREDIRECTREF||no||[RFC4437], Section 7|
|VERSION-CONTROL||no||[RFC3253], Section 3.5|
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at <http://www.ietf.org/ipr>.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at firstname.lastname@example.org.