idnits 2.17.1 draft-ietf-httpbis-method-registrations-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 184. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 195. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 202. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 208. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == Mismatching filename: the document gives the document name as 'draft-ietf-httpbis-p2-semantics-05', but the file name used is 'draft-ietf-httpbis-method-registrations-01' Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 19, 2008) is 5630 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2068 (Obsoleted by RFC 2616) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Reschke 3 Internet-Draft greenbytes 4 Updates: November 19, 2008 5 draft-ietf-httpbis-p2-semantics-05 6 (if approved) 7 Intended status: Informational 8 Expires: May 23, 2009 10 Initial Hypertext Transfer Protocol (HTTP) Method Registrations 11 draft-ietf-httpbis-method-registrations-01 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on May 23, 2009. 38 Abstract 40 This document registers those Hypertext Transfer Protocol (HTTP) 41 methods which have been defined in standards-track RFCs before the 42 IANA HTTP Method Registry was established. 44 Table of Contents 46 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 47 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 48 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 49 4. Normative References . . . . . . . . . . . . . . . . . . . . . 3 50 Appendix A. Initial Registry Contents . . . . . . . . . . . . . . 4 51 Appendix B. Change Log (to be removed by RFC Editor before 52 publication) . . . . . . . . . . . . . . . . . . . . . 5 53 B.1. Since draft-ietf-httpbis-p1-method-registrations-00 . . . . 5 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 55 Intellectual Property and Copyright Statements . . . . . . . . . . 6 57 1. Introduction 59 This document registers those Hypertext Transfer ProtocolHypertext 60 Transfer Protocol (HTTP) methods which have been defined in 61 standards-track RFCs before the IANA HTTP Method Registry was 62 established. 64 2. Security Considerations 66 There are no security considerations related to the registration 67 itself. 69 3. IANA Considerations 71 Appendix A provides initial registrations of HTTP method names for 72 the IANA HTTP Method registry at 73 (see Section 3.1 of 74 [draft-ietf-httpbis-p2-semantics]). 76 4. Normative References 78 [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. 79 Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", 80 RFC 2068, January 1997. 82 [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. 83 Whitehead, "Versioning Extensions to WebDAV (Web 84 Distributed Authoring and Versioning)", RFC 3253, 85 March 2002. 87 [RFC3648] Whitehead, J. and J. Reschke, Ed., "Web Distributed 88 Authoring and Versioning (WebDAV) Ordered Collections 89 Protocol", RFC 3648, December 2003. 91 [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web 92 Distributed Authoring and Versioning (WebDAV) Access 93 Control Protocol", RFC 3744, May 2004. 95 [RFC4437] Whitehead, J., Clemm, G., and J. Reschke, Ed., "Web 96 Distributed Authoring and Versioning (WebDAV) 97 Redirect Reference Resources", RFC 4437, March 2006. 99 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 100 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 101 March 2007. 103 [RFC4918] Dusseault, L., Ed., "HTTP Extensions for Web Distributed 104 Authoring and Versioning (WebDAV)", RFC 4918, June 2007. 106 [RFC5323] Reschke, J., Ed., Reddy, S., Davis, J., and A. Babich, 107 "Web Distributed Authoring and Versioning (WebDAV) 108 SEARCH", RFC 5323, November 2008. 110 [draft-ietf-httpbis-p2-semantics] 111 Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., 112 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., 113 and J. Reschke, Ed., "HTTP/1.1, part 2: Message 114 Semantics", draft-ietf-httpbis-p2-semantics-04 (work in 115 progress), August 2008. 117 Appendix A. Initial Registry Contents 119 +-------------------+------+----------------------------------------+ 120 | Method Name | Safe | Reference | 121 +-------------------+------+----------------------------------------+ 122 | ACL | no | [RFC3744], Section 8.1 | 123 | BASELINE-CONTROL | no | [RFC3253], Section 12.6 | 124 | CHECKIN | no | [RFC3253], Section 4.4 and [RFC3253], | 125 | | | Section 9.4 | 126 | CHECKOUT | no | [RFC3253], Section 4.3 and [RFC3253], | 127 | | | Section 8.8 | 128 | COPY | no | [RFC4918], Section 9.8 | 129 | LABEL | no | [RFC3253], Section 8.2 | 130 | LINK | no | [RFC2068], Section 19.6.1.2 | 131 | LOCK | no | [RFC4918], Section 9.10 | 132 | MERGE | no | [RFC3253], Section 11.2 | 133 | MKAKTIVITY | no | [RFC3253], Section 13.5 | 134 | MKCALENDAR | no | [RFC4791], Section 5.3.1 | 135 | MKCOL | no | [RFC4918], Section 9.3 | 136 | MKREDIRECTREF | no | [RFC4437], Section 6 | 137 | MKWORKSPACE | no | [RFC3253], Section 6.3 | 138 | MOVE | no | [RFC4918], Section 9.9 | 139 | ORDERPATCH | no | [RFC3648], Section 7 | 140 | PATCH | no | [RFC2068], Section 19.6.1.1 | 141 | PROPFIND | yes | [RFC4918], Section 9.1 | 142 | PROPPATCH | no | [RFC4918], Section 9.2 | 143 | REPORT | yes | [RFC3253], Section 3.6 | 144 | SEARCH | yes | [RFC5323], Section 2 | 145 | UNCHECKOUT | no | [RFC3253], Section 4.5 | 146 | UNLINK | no | [RFC2068], Section 19.6.1.3 | 147 | UNLOCK | no | [RFC4918], Section 9.11 | 148 | UPDATE | no | [RFC3253], Section 7.1 | 149 | UPDATEREDIRECTREF | no | [RFC4437], Section 7 | 150 | VERSION-CONTROL | no | [RFC3253], Section 3.5 | 151 +-------------------+------+----------------------------------------+ 153 Appendix B. Change Log (to be removed by RFC Editor before publication) 155 B.1. Since draft-ietf-httpbis-p1-method-registrations-00 157 Added SEARCH method (RFC 5323). 159 Author's Address 161 Julian F. Reschke 162 greenbytes GmbH 163 Hafenweg 16 164 Muenster, NW 48155 165 Germany 167 Email: julian.reschke@greenbytes.de 168 URI: http://greenbytes.de/tech/webdav/ 170 Full Copyright Statement 172 Copyright (C) The IETF Trust (2008). 174 This document is subject to the rights, licenses and restrictions 175 contained in BCP 78, and except as set forth therein, the authors 176 retain all their rights. 178 This document and the information contained herein are provided on an 179 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 180 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 181 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 182 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 183 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 184 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 186 Intellectual Property 188 The IETF takes no position regarding the validity or scope of any 189 Intellectual Property Rights or other rights that might be claimed to 190 pertain to the implementation or use of the technology described in 191 this document or the extent to which any license under such rights 192 might or might not be available; nor does it represent that it has 193 made any independent effort to identify any such rights. Information 194 on the procedures with respect to rights in RFC documents can be 195 found in BCP 78 and BCP 79. 197 Copies of IPR disclosures made to the IETF Secretariat and any 198 assurances of licenses to be made available, or the result of an 199 attempt made to obtain a general license or permission for the use of 200 such proprietary rights by implementers or users of this 201 specification can be obtained from the IETF on-line IPR repository at 202 http://www.ietf.org/ipr. 204 The IETF invites any interested party to bring to its attention any 205 copyrights, patents or patent applications, or other proprietary 206 rights that may cover technology that may be required to implement 207 this standard. Please address the information to the IETF at 208 ietf-ipr@ietf.org.