--- 1/draft-ietf-webdav-bind-14.txt 2006-08-29 01:12:18.000000000 +0200 +++ 2/draft-ietf-webdav-bind-15.txt 2006-08-29 01:12:18.000000000 +0200 @@ -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 -Expires: August 26, 2006 greenbytes - J. Whitehead +approved) J. Reschke, Ed. +Intended status: Standards Track greenbytes +Expires: February 28, 2007 J. Whitehead U.C. Santa Cruz - February 22, 2006 + August 27, 2006 Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) - draft-ietf-webdav-bind-14 + draft-ietf-webdav-bind-15 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,21 +28,21 @@ 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 August 26, 2006. + This Internet-Draft will expire on February 28, 2007. Copyright Notice Copyright (C) The Internet Society (2006). 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. @@ -120,29 +120,27 @@ 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 . . . . . . . . . . . . . 36 - Appendix B. Resolved issues (to be removed by RFC Editor - before publication) . . . . . . . . . . . . . . . . . 37 - B.1. webdav-rev . . . . . . . . . . . . . . . . . . . . . . . . 37 - Appendix C. Open issues (to be removed by RFC Editor prior to + 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 - C.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 - Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 + B.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 + Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 Intellectual Property and Copyright Statements . . . . . . . . . . 41 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 @@ -208,21 +206,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 @@ -732,21 +730,21 @@ collection, and the segment identifies the binding name of that resource in that collection. A given collection MUST appear only once in the DAV:parent-set for any given binding, even if there are multiple URI mappings to that collection. - 3.2.1. Example for DAV:parent-set property For example, if collection C1 is mapped to both /CollX and /CollY, and C1 contains a binding named "x.gif" to a resource R1, then either [/CollX, x.gif] or [/CollY, x.gif] can appear in the DAV:parent-set of R1, but not both. But if C1 also had a binding named "y.gif" to R1, then there would be two entries for C1 in the DAV:binding-set of R1 (i.e. both [/CollX, x.gif] and [/CollX, y.gif] or, alternatively, @@ -1452,30 +1450,29 @@ [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and - F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third - Edition)", W3C REC-xml-20040204, February 2004, - . + 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-14 (work in progress), - February 2006, . + draft-ietf-webdav-rfc2518bis-15 (work in progress), + May 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 @@ -1589,61 +1586,52 @@ 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). -Appendix B. Resolved issues (to be removed by RFC Editor before - publication) - - Issues that were either rejected or resolved in this version of this - document. - -B.1. webdav-rev +A.13. Since draft-ietf-webdav-bind-14 - Type: edit + Update [draft-ietf-webdav-rfc2518-bis] to draft 15. Update [XML] to + 4th edition. - julian.reschke@greenbytes.de (2006-01-30): Update from RFC2518 to - RFC2518bis. + Markup ASCII art for box recognition (doesn't affect ASCII version). - Resolution (2006-02-21): Removed own explanation of DTD syntax, - removed own definition of precondition/postcondition, removed - reference to broken RFC2518 language about DELETE and UNLOCK, removed - own definition of DAV: request header, updated examples to use - application/xml instead of text/xml MIME type, removed "Rationale for - Distinguishing Bindings from URI Mappings" to reflect the changes in - draft-ietf-webdav-rfc2518bis-14. + Identify Julian Reschke as Editor. -Appendix C. Open issues (to be removed by RFC Editor prior to +Appendix B. Open issues (to be removed by RFC Editor prior to publication) -C.1. edit +B.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 5 506 Loop Detected (status code) 31 B BIND method 18 + Marshalling 19 + Postconditions 20 + Preconditions 19 Binding 6 C Collection 6 Condition Names DAV:bind-into-collection (pre) 19 DAV:bind-source-exists (pre) 19 DAV:binding-allowed (pre) 20 DAV:binding-deleted (post) 22, 25 DAV:can-overwrite (pre) 20, 24 @@ -1699,28 +1686,34 @@ UNBIND 21 P Path Segment 6 Properties DAV:parent-set 17 DAV:resource-id 17 R REBIND method 23 + Marshalling 23 + Postconditions 25 + Preconditions 24 S Status Codes 208 Already Reported 28 506 Loop Detected 31 U UNBIND method 21 + Marshalling 21 + Postconditions 22 + Preconditions 22 URI Mapping 5 Authors' Addresses Geoffrey Clemm IBM 20 Maguire Road Lexington, MA 02421 Email: geoffrey.clemm@us.ibm.com @@ -1717,44 +1710,59 @@ URI Mapping 5 Authors' Addresses Geoffrey Clemm IBM 20 Maguire Road Lexington, MA 02421 Email: geoffrey.clemm@us.ibm.com - Jason Crawford IBM Research P.O. Box 704 Yorktown Heights, NY 10598 Email: ccjason@us.ibm.com - Julian F. Reschke + Julian F. Reschke (editor) greenbytes GmbH Hafenweg 16 Muenster, NW 48155 Germany Email: julian.reschke@greenbytes.de Jim Whitehead UC Santa Cruz, Dept. of Computer Science 1156 High Street Santa Cruz, CA 95064 Email: ejw@cse.ucsc.edu -Intellectual Property Statement +Full Copyright Statement + + Copyright (C) The Internet Society (2006). + + 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. + +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 found in BCP 78 and BCP 79. @@ -1764,30 +1772,14 @@ such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at 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. -Disclaimer of Validity - - 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. - -Copyright Statement - - Copyright (C) The Internet Society (2006). 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. - Acknowledgment - Funding for the RFC Editor function is currently provided by the - Internet Society. + Funding for the RFC Editor function is provided by the IETF + Administrative Support Activity (IASA).