idnits 2.17.1 draft-ietf-httpbis-method-registrations-14.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 (November 17, 2013) is 3806 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 November 17, 2013 5 Expires: May 21, 2014 7 Initial Hypertext Transfer Protocol (HTTP) Method Registrations 8 draft-ietf-httpbis-method-registrations-14 10 Abstract 12 This document registers those Hypertext Transfer Protocol (HTTP) 13 methods which have been defined in standards-track RFCs before the 14 IANA HTTP Method 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.1. 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 May 21, 2014. 46 Copyright Notice 48 Copyright (c) 2013 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 71 1. Introduction 73 This document registers those Hypertext Transfer Protocol (HTTP) 74 methods which have been defined in standards-track RFCs other than 75 [draft-ietf-httpbis-p2-semantics] before the IANA HTTP Method 76 Registry was established. 78 2. Security Considerations 80 There are no security considerations related to the registration 81 itself. 83 3. IANA Considerations 85 The table below provides registrations of HTTP method names to be 86 added to the IANA HTTP Method registry at 87 (see Section 8.1 of 88 [draft-ietf-httpbis-p2-semantics]). 90 +-------------------+------+------------+---------------------------+ 91 | Method Name | Safe | Idempotent | Reference | 92 +-------------------+------+------------+---------------------------+ 93 | ACL | no | yes | [RFC3744], Section 8.1 | 94 | BASELINE-CONTROL | no | yes | [RFC3253], Section 12.6 | 95 | BIND | no | yes | [RFC5842], Section 4 | 96 | CHECKIN | no | yes | [RFC3253], Section 4.4 | 97 | | | | and [RFC3253], Section | 98 | | | | 9.4 | 99 | CHECKOUT | no | yes | [RFC3253], Section 4.3 | 100 | | | | and [RFC3253], Section | 101 | | | | 8.8 | 102 | COPY | no | yes | [RFC4918], Section 9.8 | 103 | LABEL | no | yes | [RFC3253], Section 8.2 | 104 | LINK | no | yes | [RFC2068], Section | 105 | | | | 19.6.1.2 | 106 | LOCK | no | no | [RFC4918], Section 9.10 | 107 | MERGE | no | yes | [RFC3253], Section 11.2 | 108 | MKACTIVITY | no | yes | [RFC3253], Section 13.5 | 109 | MKCALENDAR | no | yes | [RFC4791], Section 5.3.1 | 110 | MKCOL | no | yes | [RFC4918], Section 9.3 | 111 | MKREDIRECTREF | no | yes | [RFC4437], Section 6 | 112 | MKWORKSPACE | no | yes | [RFC3253], Section 6.3 | 113 | MOVE | no | yes | [RFC4918], Section 9.9 | 114 | ORDERPATCH | no | yes | [RFC3648], Section 7 | 115 | PATCH | no | no | [RFC5789], Section 2 | 116 | PROPFIND | yes | yes | [RFC4918], Section 9.1 | 117 | PROPPATCH | no | yes | [RFC4918], Section 9.2 | 118 | REBIND | no | yes | [RFC5842], Section 6 | 119 | REPORT | yes | yes | [RFC3253], Section 3.6 | 120 | SEARCH | yes | yes | [RFC5323], Section 2 | 121 | UNBIND | no | yes | [RFC5842], Section 5 | 122 | UNCHECKOUT | no | yes | [RFC3253], Section 4.5 | 123 | UNLINK | no | yes | [RFC2068], Section | 124 | | | | 19.6.1.3 | 125 | UNLOCK | no | yes | [RFC4918], Section 9.11 | 126 | UPDATE | no | yes | [RFC3253], Section 7.1 | 127 | UPDATEREDIRECTREF | no | yes | [RFC4437], Section 7 | 128 | VERSION-CONTROL | no | yes | [RFC3253], Section 3.5 | 129 +-------------------+------+------------+---------------------------+ 131 4. Normative References 133 [RFC2068] Fielding, R., Gettys, J., Mogul, 134 J., Nielsen, H., and T. Berners- 135 Lee, "Hypertext Transfer Protocol 136 -- HTTP/1.1", RFC 2068, 137 January 1997. 139 [RFC3253] Clemm, G., Amsden, J., Ellison, 140 T., Kaler, C., and J. Whitehead, 141 "Versioning Extensions to WebDAV 142 (Web Distributed Authoring and 143 Versioning)", RFC 3253, 144 March 2002. 146 [RFC3648] Whitehead, J. and J. Reschke, Ed., 147 "Web Distributed Authoring and 148 Versioning (WebDAV) Ordered 149 Collections Protocol", RFC 3648, 150 December 2003. 152 [RFC3744] Clemm, G., Reschke, J., Sedlar, 153 E., and J. Whitehead, "Web 154 Distributed Authoring and 155 Versioning (WebDAV) Access Control 156 Protocol", RFC 3744, May 2004. 158 [RFC4437] Whitehead, J., Clemm, G., and J. 159 Reschke, Ed., "Web Distributed 160 Authoring and Versioning (WebDAV) 161 Redirect Reference Resources", 162 RFC 4437, March 2006. 164 [RFC4791] Daboo, C., Desruisseaux, B., and 165 L. Dusseault, "Calendaring 166 Extensions to WebDAV (CalDAV)", 167 RFC 4791, March 2007. 169 [RFC4918] Dusseault, L., Ed., "HTTP 170 Extensions for Web Distributed 171 Authoring and Versioning 172 (WebDAV)", RFC 4918, June 2007. 174 [RFC5323] Reschke, J., Ed., Reddy, S., 175 Davis, J., and A. Babich, "Web 176 Distributed Authoring and 177 Versioning (WebDAV) SEARCH", 178 RFC 5323, November 2008. 180 [RFC5789] Dusseault, L. and J. Snell, "PATCH 181 Method for HTTP", RFC 5789, 182 March 2010. 184 [RFC5842] Clemm, G., Crawford, J., Reschke, 185 J., Ed., and J. Whitehead, 186 "Binding Extensions to Web 187 Distributed Authoring and 188 Versioning (WebDAV)", RFC 5842, 189 April 2010. 191 [draft-ietf-httpbis-p2-semantics] Fielding, R., Ed. and J. Reschke, 192 Ed., "Hypertext Transfer Protocol 193 (HTTP/1.1): Semantics and 194 Content", 195 draft-ietf-httpbis-p2-semantics-25 196 (work in progress), November 2013. 198 Appendix A. Change Log (to be removed by RFC Editor before publication) 200 Changes up to the IETF Last Call draft are summarized in . 204 A.1. Since draft-ietf-httpbis-method-registrations-13 206 Closed issues: 208 o : "registration 209 tables should be inside IANA considerations" 211 Clarified the IANA action to say "add". 213 Updated httpbis reference. 215 Author's Address 217 Julian F. Reschke 218 greenbytes GmbH 219 Hafenweg 16 220 Muenster, NW 48155 221 Germany 223 EMail: julian.reschke@greenbytes.de 224 URI: http://greenbytes.de/tech/webdav/