idnits 2.17.1 draft-ietf-httpbis-method-registrations-00.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 171. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 182. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 189. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 195. 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-04', but the file name used is 'draft-ietf-httpbis-method-registrations-00' 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 (August 29, 2008) is 5712 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: August 29, 2008 5 draft-ietf-httpbis-p2-semantics-04 6 (if approved) 7 Intended status: Informational 8 Expires: March 2, 2009 10 Initial Hypertext Transfer Protocol (HTTP) Method Registrations 11 draft-ietf-httpbis-method-registrations-00 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 March 2, 2009. 38 Abstract 40 This document registers those Hypertext Transfer ProtocolHypertext 41 Transfer Protocol (HTTP) methods which have been defined in 42 standards-track RFCs before the IANA HTTP Method Registry was 43 established. 45 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 48 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 49 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 50 4. Normative References . . . . . . . . . . . . . . . . . . . . . 3 51 Appendix A. Initial Registry Contents . . . . . . . . . . . . . . 4 52 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 Intellectual Property and Copyright Statements . . . . . . . . . . 6 55 1. Introduction 57 This document registers those Hypertext Transfer ProtocolHypertext 58 Transfer Protocol (HTTP) methods which have been defined in 59 standards-track RFCs before the IANA HTTP Method Registry was 60 established. 62 2. Security Considerations 64 There are no security considerations related to the registration 65 itself. 67 3. IANA Considerations 69 Appendix A provides initial registrations of HTTP method names for 70 the IANA HTTP Method registry at 71 (see Section 3.1 of 72 [draft-ietf-httpbis-p2-semantics]). 74 4. Normative References 76 [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. 77 Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", 78 RFC 2068, January 1997. 80 [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. 81 Whitehead, "Versioning Extensions to WebDAV (Web 82 Distributed Authoring and Versioning)", RFC 3253, 83 March 2002. 85 [RFC3648] Whitehead, J. and J. Reschke, Ed., "Web Distributed 86 Authoring and Versioning (WebDAV) Ordered Collections 87 Protocol", RFC 3648, December 2003. 89 [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web 90 Distributed Authoring and Versioning (WebDAV) Access 91 Control Protocol", RFC 3744, May 2004. 93 [RFC4437] Whitehead, J., Clemm, G., and J. Reschke, Ed., "Web 94 Distributed Authoring and Versioning (WebDAV) 95 Redirect Reference Resources", RFC 4437, March 2006. 97 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 98 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 99 March 2007. 101 [RFC4918] Dusseault, L., Ed., "HTTP Extensions for Web Distributed 102 Authoring and Versioning (WebDAV)", RFC 4918, June 2007. 104 [draft-ietf-httpbis-p2-semantics] 105 Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., 106 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., 107 and J. Reschke, Ed., "HTTP/1.1, part 2: Message 108 Semantics", draft-ietf-httpbis-p2-semantics-04 (work in 109 progress), August 2008. 111 Appendix A. Initial Registry Contents 113 +-------------------+------+----------------------------------------+ 114 | Method Name | Safe | Reference | 115 +-------------------+------+----------------------------------------+ 116 | ACL | no | [RFC3744], Section 8.1 | 117 | BASELINE-CONTROL | no | [RFC3253], Section 12.6 | 118 | CHECKIN | no | [RFC3253], Section 4.4 and [RFC3253], | 119 | | | Section 9.4 | 120 | CHECKOUT | no | [RFC3253], Section 4.3 and [RFC3253], | 121 | | | Section 8.8 | 122 | COPY | no | [RFC4918], Section 9.8 | 123 | LABEL | no | [RFC3253], Section 8.2 | 124 | LINK | no | [RFC2068], Section 19.6.1.2 | 125 | LOCK | no | [RFC4918], Section 9.10 | 126 | MERGE | no | [RFC3253], Section 11.2 | 127 | MKAKTIVITY | no | [RFC3253], Section 13.5 | 128 | MKCALENDAR | no | [RFC4791], Section 5.3.1 | 129 | MKCOL | no | [RFC4918], Section 9.3 | 130 | MKREDIRECTREF | no | [RFC4437], Section 6 | 131 | MKWORKSPACE | no | [RFC3253], Section 6.3 | 132 | MOVE | no | [RFC4918], Section 9.9 | 133 | ORDERPATCH | no | [RFC3648], Section 7 | 134 | PATCH | no | [RFC2068], Section 19.6.1.1 | 135 | PROPFIND | yes | [RFC4918], Section 9.1 | 136 | PROPPATCH | no | [RFC4918], Section 9.2 | 137 | REPORT | yes | [RFC3253], Section 3.6 | 138 | UNCHECKOUT | no | [RFC3253], Section 4.5 | 139 | UNLINK | no | [RFC2068], Section 19.6.1.3 | 140 | UNLOCK | no | [RFC4918], Section 9.11 | 141 | UPDATE | no | [RFC3253], Section 7.1 | 142 | UPDATEREDIRECTREF | no | [RFC4437], Section 7 | 143 | VERSION-CONTROL | no | [RFC3253], Section 3.5 | 144 +-------------------+------+----------------------------------------+ 146 Author's Address 148 Julian F. Reschke 149 greenbytes GmbH 150 Hafenweg 16 151 Muenster, NW 48155 152 Germany 154 Email: julian.reschke@greenbytes.de 155 URI: http://greenbytes.de/tech/webdav/ 157 Full Copyright Statement 159 Copyright (C) The IETF Trust (2008). 161 This document is subject to the rights, licenses and restrictions 162 contained in BCP 78, and except as set forth therein, the authors 163 retain all their rights. 165 This document and the information contained herein are provided on an 166 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 167 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 168 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 169 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 170 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 171 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 173 Intellectual Property 175 The IETF takes no position regarding the validity or scope of any 176 Intellectual Property Rights or other rights that might be claimed to 177 pertain to the implementation or use of the technology described in 178 this document or the extent to which any license under such rights 179 might or might not be available; nor does it represent that it has 180 made any independent effort to identify any such rights. Information 181 on the procedures with respect to rights in RFC documents can be 182 found in BCP 78 and BCP 79. 184 Copies of IPR disclosures made to the IETF Secretariat and any 185 assurances of licenses to be made available, or the result of an 186 attempt made to obtain a general license or permission for the use of 187 such proprietary rights by implementers or users of this 188 specification can be obtained from the IETF on-line IPR repository at 189 http://www.ietf.org/ipr. 191 The IETF invites any interested party to bring to its attention any 192 copyrights, patents or patent applications, or other proprietary 193 rights that may cover technology that may be required to implement 194 this standard. Please address the information to the IETF at 195 ietf-ipr@ietf.org.