idnits 2.17.1 draft-ietf-httpbis-method-registrations-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) 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-06', but the file name used is 'draft-ietf-httpbis-method-registrations-02' Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. 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 (May 23, 2009) is 5446 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 (==), 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 Updates: May 23, 2009 5 draft-ietf-httpbis-p2-semantics-06 6 (if approved) 7 Intended status: Informational 8 Expires: November 24, 2009 10 Initial Hypertext Transfer Protocol (HTTP) Method Registrations 11 draft-ietf-httpbis-method-registrations-02 13 Status of this Memo 15 This Internet-Draft is submitted to IETF in full conformance with the 16 provisions of BCP 78 and BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on November 24, 2009. 36 Copyright Notice 38 Copyright (c) 2009 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents in effect on the date of 43 publication of this document (http://trustee.ietf.org/license-info). 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. 47 Abstract 49 This document registers those Hypertext Transfer Protocol (HTTP) 50 methods which have been defined in standards-track RFCs before the 51 IANA HTTP Method Registry was established. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 57 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 58 4. Normative References . . . . . . . . . . . . . . . . . . . . . 3 59 Appendix A. Initial Registry Contents . . . . . . . . . . . . . . 4 60 Appendix B. Change Log (to be removed by RFC Editor before 61 publication) . . . . . . . . . . . . . . . . . . . . . 5 62 B.1. Since draft-ietf-httpbis-p1-method-registrations-00 . . . . 5 63 B.2. Since draft-ietf-httpbis-p1-method-registrations-01 . . . . 5 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 This document registers those Hypertext Transfer ProtocolHypertext 69 Transfer Protocol (HTTP) methods which have been defined in 70 standards-track RFCs before the IANA HTTP Method Registry was 71 established. 73 2. Security Considerations 75 There are no security considerations related to the registration 76 itself. 78 3. IANA Considerations 80 Appendix A provides initial registrations of HTTP method names for 81 the IANA HTTP Method registry at 82 (see Section 2.1 of 83 [draft-ietf-httpbis-p2-semantics]). 85 4. Normative References 87 [RFC2068] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. 88 Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", 89 RFC 2068, January 1997. 91 [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. 92 Whitehead, "Versioning Extensions to WebDAV (Web 93 Distributed Authoring and Versioning)", RFC 3253, 94 March 2002. 96 [RFC3648] Whitehead, J. and J. Reschke, Ed., "Web Distributed 97 Authoring and Versioning (WebDAV) Ordered Collections 98 Protocol", RFC 3648, December 2003. 100 [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web 101 Distributed Authoring and Versioning (WebDAV) Access 102 Control Protocol", RFC 3744, May 2004. 104 [RFC4437] Whitehead, J., Clemm, G., and J. Reschke, Ed., "Web 105 Distributed Authoring and Versioning (WebDAV) 106 Redirect Reference Resources", RFC 4437, March 2006. 108 [RFC4791] Daboo, C., Desruisseaux, B., and L. Dusseault, 109 "Calendaring Extensions to WebDAV (CalDAV)", RFC 4791, 110 March 2007. 112 [RFC4918] Dusseault, L., Ed., "HTTP Extensions for Web Distributed 113 Authoring and Versioning (WebDAV)", RFC 4918, June 2007. 115 [RFC5323] Reschke, J., Ed., Reddy, S., Davis, J., and A. Babich, 116 "Web Distributed Authoring and Versioning (WebDAV) 117 SEARCH", RFC 5323, November 2008. 119 [draft-ietf-httpbis-p2-semantics] 120 Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., 121 Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., 122 and J. Reschke, Ed., "HTTP/1.1, part 2: Message 123 Semantics", draft-ietf-httpbis-p2-semantics-06 (work in 124 progress), March 2009. 126 Appendix A. Initial Registry Contents 128 +-------------------+------+----------------------------------------+ 129 | Method Name | Safe | Reference | 130 +-------------------+------+----------------------------------------+ 131 | ACL | no | [RFC3744], Section 8.1 | 132 | BASELINE-CONTROL | no | [RFC3253], Section 12.6 | 133 | CHECKIN | no | [RFC3253], Section 4.4 and [RFC3253], | 134 | | | Section 9.4 | 135 | CHECKOUT | no | [RFC3253], Section 4.3 and [RFC3253], | 136 | | | Section 8.8 | 137 | COPY | no | [RFC4918], Section 9.8 | 138 | LABEL | no | [RFC3253], Section 8.2 | 139 | LINK | no | [RFC2068], Section 19.6.1.2 | 140 | LOCK | no | [RFC4918], Section 9.10 | 141 | MERGE | no | [RFC3253], Section 11.2 | 142 | MKAKTIVITY | no | [RFC3253], Section 13.5 | 143 | MKCALENDAR | no | [RFC4791], Section 5.3.1 | 144 | MKCOL | no | [RFC4918], Section 9.3 | 145 | MKREDIRECTREF | no | [RFC4437], Section 6 | 146 | MKWORKSPACE | no | [RFC3253], Section 6.3 | 147 | MOVE | no | [RFC4918], Section 9.9 | 148 | ORDERPATCH | no | [RFC3648], Section 7 | 149 | PATCH | no | [RFC2068], Section 19.6.1.1 | 150 | PROPFIND | yes | [RFC4918], Section 9.1 | 151 | PROPPATCH | no | [RFC4918], Section 9.2 | 152 | REPORT | yes | [RFC3253], Section 3.6 | 153 | SEARCH | yes | [RFC5323], Section 2 | 154 | UNCHECKOUT | no | [RFC3253], Section 4.5 | 155 | UNLINK | no | [RFC2068], Section 19.6.1.3 | 156 | UNLOCK | no | [RFC4918], Section 9.11 | 157 | UPDATE | no | [RFC3253], Section 7.1 | 158 | UPDATEREDIRECTREF | no | [RFC4437], Section 7 | 159 | VERSION-CONTROL | no | [RFC3253], Section 3.5 | 160 +-------------------+------+----------------------------------------+ 162 Appendix B. Change Log (to be removed by RFC Editor before publication) 164 B.1. Since draft-ietf-httpbis-p1-method-registrations-00 166 Added SEARCH method (RFC 5323). 168 B.2. Since draft-ietf-httpbis-p1-method-registrations-01 170 Update draft-ietf-httpbis-p2-semantics reference. 172 Author's Address 174 Julian F. Reschke 175 greenbytes GmbH 176 Hafenweg 16 177 Muenster, NW 48155 178 Germany 180 Email: julian.reschke@greenbytes.de 181 URI: http://greenbytes.de/tech/webdav/