--- 1/draft-ietf-webdav-bind-15.txt 2007-01-05 22:12:25.000000000 +0100 +++ 2/draft-ietf-webdav-bind-16.txt 2007-01-05 22:12:25.000000000 +0100 @@ -1,23 +1,23 @@ Network Working Group G. Clemm Internet-Draft IBM Updates: J. Crawford -draft-ietf-webdav-rfc2518bis (if IBM Research -approved) J. Reschke, Ed. +draft-ietf-webdav-rfc2518bis IBM Research +(if approved) J. Reschke, Ed. Intended status: Standards Track greenbytes -Expires: February 28, 2007 J. Whitehead +Expires: July 9, 2007 J. Whitehead U.C. Santa Cruz - August 27, 2006 + January 5, 2007 Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) - draft-ietf-webdav-bind-15 + draft-ietf-webdav-bind-16 Status of this Memo 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 @@ -28,25 +28,25 @@ 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 on February 28, 2007. + This Internet-Draft will expire on July 9, 2007. Copyright Notice - Copyright (C) The Internet Society (2006). + Copyright (C) The IETF Trust (2007). Abstract This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to insure the integrity of any bindings that they allow to be created. @@ -107,41 +107,47 @@ 10.2. Bind Loops . . . . . . . . . . . . . . . . . . . . . . . . 32 10.3. Bindings, and Denial of Service . . . . . . . . . . . . . 32 10.4. Private Locations May Be Revealed . . . . . . . . . . . . 33 10.5. DAV:parent-set and Denial of Service . . . . . . . . . . . 33 11. Internationalization Considerations . . . . . . . . . . . . . 33 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 33 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34 14.1. Normative References . . . . . . . . . . . . . . . . . . . 34 14.2. Informative References . . . . . . . . . . . . . . . . . . 34 - Appendix A. Change Log (to be removed by RFC Editor before - publication) . . . . . . . . . . . . . . . . . . . . 34 - A.1. Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . 34 - A.2. Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 35 - A.3. Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 35 - A.4. Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 35 - A.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 35 - A.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 35 - A.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 35 - A.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36 - A.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36 - A.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 36 - A.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 36 - A.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 37 - A.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 37 - Appendix B. Open issues (to be removed by RFC Editor prior to - publication) . . . . . . . . . . . . . . . . . . . . 37 - B.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 - Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 - Intellectual Property and Copyright Statements . . . . . . . . . . 41 + Appendix A. Clarification to RFC2518bis' Usage of the term + 'lock root' . . . . . . . . . . . . . . . . . . . . . 34 + Appendix B. Change Log (to be removed by RFC Editor before + publication) . . . . . . . . . . . . . . . . . . . . 35 + B.1. Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . 35 + B.2. Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 35 + B.3. Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 35 + B.4. Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 36 + B.5. Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 36 + B.6. Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 36 + B.7. Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 36 + B.8. Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 36 + B.9. Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 36 + B.10. Since draft-ietf-webdav-bind-11 . . . . . . . . . . . . . 37 + B.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 37 + B.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 37 + B.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 37 + B.14. Since draft-ietf-webdav-bind-15 . . . . . . . . . . . . . 38 + Appendix C. Resolved issues (to be removed by RFC Editor + before publication) . . . . . . . . . . . . . . . . . 38 + C.1. rfc2518bis-lock-root . . . . . . . . . . . . . . . . . . . 38 + Appendix D. Open issues (to be removed by RFC Editor prior to + publication) . . . . . . . . . . . . . . . . . . . . 38 + D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 + Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 + Intellectual Property and Copyright Statements . . . . . . . . . . 42 1. Introduction This specification extends the WebDAV Distributed Authoring Protocol ([draft-ietf-webdav-rfc2518bis]) to enable clients to create new access paths to existing resources. This capability is useful for several reasons: URIs of WebDAV-compliant resources are hierarchical and correspond to a hierarchy of collections in resource space. The WebDAV Distributed @@ -206,21 +212,21 @@ resource. Section 5 specifies the UNBIND method, used to remove a binding to a resource. Section 6 specifies the REBIND method, used to move a binding to another collection. 1.1. Terminology The terminology used here follows and extends that in the WebDAV Distributed Authoring Protocol specification [draft-ietf-webdav-rfc2518bis]. - The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL-NOT", + The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. This document uses XML DTD fragments ([XML]) as a notational convention, using the rules defined in Section 17 of [draft-ietf-webdav-rfc2518bis]. URI Mapping A relation between an absolute URI and a resource. For an @@ -1457,116 +1463,147 @@ RFC 3986, January 2005. [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth Edition)", W3C REC-xml-20060816, August 2006, . [draft-ietf-webdav-rfc2518bis] Dusseault, L., Ed., "HTTP Extensions for Distributed Authoring - WebDAV RFC2518 bis", - draft-ietf-webdav-rfc2518bis-15 (work in progress), - May 2006. + draft-ietf-webdav-rfc2518bis-17 (work in progress), + December 2006. 14.2. Informative References [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. [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol", RFC 3744, May 2004. [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, July 2005. -Appendix A. Change Log (to be removed by RFC Editor before publication) +Appendix A. Clarification to RFC2518bis' Usage of the term 'lock root' -A.1. Since draft-ietf-webdav-bind-02 + [draft-ietf-webdav-rfc2518bis], Section 9.10.1 claims: + + A LOCK request to an existing resource will create a lock on the + resource identified by the Request-URI, provided the resource is + not already locked with a conflicting lock. The resource + identified in the Request-URI becomes the root of the lock. + + This is incorrect in that it implies that the "lock root" is a + resource, not a URL + (). + However, should a directly locked resource have multiple bindings, + only the one used in the Request-URI of the LOCK request will be the + protected from changes of clients not supplying the lock token. + + A correct description would be: + + A LOCK request to an existing resource will create a lock on the + resource identified by the Request-URI, provided the resource is + not already locked with a conflicting lock. The Request-URI + becomes the root of the lock. + + Note that this change makes the description consistent with the + definition of the DAV:lockroot XML element in Section 14.12 of + [draft-ietf-webdav-rfc2518bis]. + + The authors of this specification recommend that future revisions of + [draft-ietf-webdav-rfc2518bis] will update the description as + suggested above. + +Appendix B. Change Log (to be removed by RFC Editor before publication) + +B.1. Since draft-ietf-webdav-bind-02 Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and "2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed resolution, but keep it open. Add issues "ED_references" and "4_507_status". Started work on index. Rename document to "Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)". Rename "References" to "Normative References". Close issue "ED_references". Close issue "4_507_status". -A.2. Since draft-ietf-webdav-bind-03 +B.2. Since draft-ietf-webdav-bind-03 Add and close issues "9.2_redirect_loops", "ED_authors" and "ED_updates". Add section about capability discovery (DAV header). Close issues "5.1_LOOP_STATUS". Add and resolve new issue "5.1_506_STATUS_STREAMING". Update XML spec reference. Add issue "locking" and resolve as invalid. -A.3. Since draft-ietf-webdav-bind-04 +B.3. Since draft-ietf-webdav-bind-04 Add and close issues "6_precondition_binding_allowed" and "6_lock_behaviour". Add mailing list and issues list pointers to front. -A.4. Since draft-ietf-webdav-bind-05 +B.4. Since draft-ietf-webdav-bind-05 Editorial fixes. Add and resolve issues "1.3_error_negotiation", "2.5_language" and "7.1.1_add_resource_id". Add historical issue "4_LOCK_BEHAVIOR" and it's resolution for better tracking. -A.5. Since draft-ietf-webdav-bind-06 +B.5. Since draft-ietf-webdav-bind-06 Rewrite Editorial Note. Open and resolve issues "2.6_identical", "specify_safeness_and_idempotence" and "ED_rfc2026_ref". -A.6. Since draft-ietf-webdav-bind-07 +B.6. Since draft-ietf-webdav-bind-07 Add more index items (no change tracking). Add and resolve issues "2.3_copy_to_same", "bind_properties", "bind_vs_ACL", "6_rebind_intro" and "rfc2396bis" (actually an action item). Fix XML DTD fragment in section 3.3. Make spelling of "Request-URI" consistent. -A.7. Since draft-ietf-webdav-bind-08 +B.7. Since draft-ietf-webdav-bind-08 Resolved editorial issues raised by Jim Whitehead in . Add and resolve issues "atomicity", "2_allow_destroy", "2.1_separate_loop_discussion", "2.1.1_bind_loops_vs_locks", "2.3_copy_depth_infinity", "2.3_copy_example", "2.3_copy_vs_loops", "2.6_resource-id_vs_versions", "3.2_example" and "6_rebind_premissions". Add issue "2.6_when_do_ids_change". Re-open and resolve "6_rebind_intro". -A.8. Since draft-ietf-webdav-bind-09 +B.8. Since draft-ietf-webdav-bind-09 Add and resolve issue "6.1_rebind_vs_locks", adding proposed example text. Add action item "3.1_uuids". Close issue "2.6_when_do_ids_change". Add and resolve issues "2.6_bindings_vs_properties" and "uri_draft_ref". -A.9. Since draft-ietf-webdav-bind-10 +B.9. Since draft-ietf-webdav-bind-10 Resolve action item "3.1_uuids". Add and resolve issue "2.7_unlock_vs_bindings". Revisit issue "2.6_bindings_vs_properties", and remove the part of the sentence that speaks about live properties. Update "rfc2396bis" references to "RFC3986". Add issue "9_ns_op_and_acl" and add potential resolution. Align artwork where applicable (new xml2rfc1.29rc2 feature). -A.10. Since draft-ietf-webdav-bind-11 +B.10. Since draft-ietf-webdav-bind-11 Updated [draft-mealling-uuid-urn] to [RFC4122]. Add statement about live properties in Section 2.6. -A.11. Since draft-ietf-webdav-bind-12 +B.11. Since draft-ietf-webdav-bind-12 Updated Author's address. Uppercase "Section" when referring to other documents. Updating from RFC2518 to RFC2518bis: o Remove own explanation of DTD syntax. o Remove own definition of precondition/postcondition. @@ -1575,44 +1612,70 @@ o Remove own definition of DAV: request header. o Updated "Rationale for Distinguishing Bindings from URI Mappings" to reflect the changes in [draft-ietf-webdav-rfc2518bis], making proposals for more changes so that the issue can be closed (see also and ). -A.12. Since draft-ietf-webdav-bind-13 +B.12. Since draft-ietf-webdav-bind-13 Update [draft-ietf-webdav-rfc2518-bis] to draft 14. Update one incorrect section reference. Remove Section "Rationale for Distinguishing Bindings from URI Mappings" as [draft-ietf-webdav-rfc2518-bis] now uses the proper definition of collection state. Examples use application/xml instead of text/xml MIME type. Fix IANA section (there are no IANA considerations). -A.13. Since draft-ietf-webdav-bind-14 +B.13. Since draft-ietf-webdav-bind-14 Update [draft-ietf-webdav-rfc2518-bis] to draft 15. Update [XML] to 4th edition. Markup ASCII art for box recognition (doesn't affect ASCII version). Identify Julian Reschke as Editor. -Appendix B. Open issues (to be removed by RFC Editor prior to +B.14. Since draft-ietf-webdav-bind-15 + + Fix typo in RFC2119 keywords section (sorry!). + + Update [draft-ietf-webdav-rfc2518-bis] to draft 17. + + Add and resolve issue "rfc2518bis-lock-root". + +Appendix C. Resolved issues (to be removed by RFC Editor before publication) -B.1. edit + Issues that were either rejected or resolved in this version of this + document. + +C.1. rfc2518bis-lock-root + + Type: change + + julian.reschke@greenbytes.de (2007-01-04): + draft-ietf-webdav-rfc2518bis-17 uses the term "lock root" + inconsistently. Add an appendix explaining the problem and + suggesting a clarification. + + Resolution (2007-01-04): Add appendix explaining the issue and + recommending a fix to rfc2518bis. + +Appendix D. Open issues (to be removed by RFC Editor prior to + publication) + +D.1. edit Type: edit julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for editorial fixes/enhancements. Index 2 208 Already Reported (status code) 28 @@ -1734,33 +1799,34 @@ Jim Whitehead UC Santa Cruz, Dept. of Computer Science 1156 High Street Santa Cruz, CA 95064 Email: ejw@cse.ucsc.edu Full Copyright Statement - Copyright (C) The Internet Society (2006). + Copyright (C) The IETF Trust (2007). 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 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. + 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. Intellectual Property 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 @@ -1774,12 +1840,12 @@ 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 ietf-ipr@ietf.org. Acknowledgment - Funding for the RFC Editor function is provided by the IETF - Administrative Support Activity (IASA). + Funding for the RFC Editor function is currently provided by the + Internet Society.