draft-ietf-webdav-bind-22.txt   draft-ietf-webdav-bind-23.txt 
Network Working Group G. Clemm Network Working Group G. Clemm
Internet-Draft IBM Internet-Draft IBM
Updates: 4918 (if approved) J. Crawford Updates: 4918 (if approved) J. Crawford
Intended status: Standards Track IBM Research Intended status: Experimental IBM Research
Expires: May 1, 2009 J. Reschke, Ed. Expires: August 29, 2009 J. Reschke, Ed.
greenbytes greenbytes
J. Whitehead J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
October 28, 2008 February 25, 2009
Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)
draft-ietf-webdav-bind-22 draft-ietf-webdav-bind-23
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79. This document may contain material
have been or will be disclosed, and any of which he or she becomes from IETF Documents or IETF Contributions published or made publicly
aware will be disclosed, in accordance with Section 6 of BCP 79. available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 1, 2009. This Internet-Draft will expire on August 29, 2009.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
This specification defines bindings, and the BIND method for creating This specification defines bindings, and the BIND method for creating
multiple bindings to the same resource. Creating a new binding to a 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. resource causes at least one new URI to be mapped to that resource.
Servers are required to insure the integrity of any bindings that Servers are required to insure the integrity of any bindings that
they allow to be created. they allow to be created.
Editorial Note (To be removed by RFC Editor before publication) Editorial Note (To be removed by RFC Editor before publication)
skipping to change at page 3, line 48 skipping to change at page 4, line 35
B.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 42 B.11. Since draft-ietf-webdav-bind-12 . . . . . . . . . . . . . 42
B.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 43 B.12. Since draft-ietf-webdav-bind-13 . . . . . . . . . . . . . 43
B.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 43 B.13. Since draft-ietf-webdav-bind-14 . . . . . . . . . . . . . 43
B.14. Since draft-ietf-webdav-bind-15 . . . . . . . . . . . . . 43 B.14. Since draft-ietf-webdav-bind-15 . . . . . . . . . . . . . 43
B.15. Since draft-ietf-webdav-bind-16 . . . . . . . . . . . . . 43 B.15. Since draft-ietf-webdav-bind-16 . . . . . . . . . . . . . 43
B.16. Since draft-ietf-webdav-bind-17 . . . . . . . . . . . . . 43 B.16. Since draft-ietf-webdav-bind-17 . . . . . . . . . . . . . 43
B.17. Since draft-ietf-webdav-bind-18 . . . . . . . . . . . . . 44 B.17. Since draft-ietf-webdav-bind-18 . . . . . . . . . . . . . 44
B.18. Since draft-ietf-webdav-bind-19 . . . . . . . . . . . . . 44 B.18. Since draft-ietf-webdav-bind-19 . . . . . . . . . . . . . 44
B.19. Since draft-ietf-webdav-bind-20 . . . . . . . . . . . . . 44 B.19. Since draft-ietf-webdav-bind-20 . . . . . . . . . . . . . 44
B.20. Since draft-ietf-webdav-bind-21 . . . . . . . . . . . . . 44 B.20. Since draft-ietf-webdav-bind-21 . . . . . . . . . . . . . 44
Appendix C. Resolved issues (to be removed by RFC Editor B.21. Since draft-ietf-webdav-bind-22 . . . . . . . . . . . . . 44
before publication) . . . . . . . . . . . . . . . . . 44 Appendix C. Open issues (to be removed by RFC Editor prior to
C.1. status-codes . . . . . . . . . . . . . . . . . . . . . . . 44 publication) . . . . . . . . . . . . . . . . . . . . 44
C.2. relation-to-deltav . . . . . . . . . . . . . . . . . . . . 45 C.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix D. Open issues (to be removed by RFC Editor prior to Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
publication) . . . . . . . . . . . . . . . . . . . . 45
D.1. edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 47
Intellectual Property and Copyright Statements . . . . . . . . . . 49
1. Introduction 1. Introduction
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
([RFC4918]) to enable clients to create new access paths to existing ([RFC4918]) to enable clients to create new access paths to existing
resources. This capability is useful for several reasons: resources. This capability is useful for several reasons:
URIs of WebDAV-compliant resources are hierarchical and correspond to URIs of WebDAV-compliant resources are hierarchical and correspond to
a hierarchy of collections in resource space. The WebDAV Distributed a hierarchy of collections in resource space. The WebDAV Distributed
Authoring Protocol makes it possible to organize these resources into Authoring Protocol makes it possible to organize these resources into
skipping to change at page 39, line 16 skipping to change at page 39, line 16
Section 7 defines the HTTP status codes 208 (Already Reported) and Section 7 defines the HTTP status codes 208 (Already Reported) and
506 (Loop Detected), to be added to the registry at 506 (Loop Detected), to be added to the registry at
<http://www.iana.org/assignments/http-status-codes>. <http://www.iana.org/assignments/http-status-codes>.
14. Acknowledgements 14. Acknowledgements
This document is the collaborative product of the authors and Tyson This document is the collaborative product of the authors and Tyson
Chihaya, Jim Davis, Chuck Fay and Judith Slein. It has benefited Chihaya, Jim Davis, Chuck Fay and Judith Slein. It has benefited
from thoughtful discussion by Jim Amsden, Peter Carlson, Steve from thoughtful discussion by Jim Amsden, Peter Carlson, Steve
Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Spencer Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Cyrus
Dawkins, Mark Day, Werner Donne, Rajiv Dulepet, David Durand, Lisa Daboo, Spencer Dawkins, Mark Day, Werner Donne, Rajiv Dulepet, David
Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe Durand, Lisa Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland,
Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Joe Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager,
Kaler, Manoj Kasichainula, Rohit Khare, Brian Korver, Daniel Chris Kaler, Manoj Kasichainula, Rohit Khare, Brian Korver, Daniel
LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra
Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness,
John Stracke, John Tigue, John Turner, Kevin Wiggen, and other John Stracke, John Tigue, John Turner, Kevin Wiggen, and other
members of the WebDAV working group. members of the WebDAV working group.
15. References 15. References
15.1. Normative References 15.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
skipping to change at page 39, line 45 skipping to change at page 39, line 45
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, January 2005. RFC 3986, January 2005.
[RFC4918] Dusseault, L., Ed., "HTTP Extensions for Web Distributed [RFC4918] Dusseault, L., Ed., "HTTP Extensions for Web Distributed
Authoring and Versioning (WebDAV)", RFC 4918, June 2007. Authoring and Versioning (WebDAV)", RFC 4918, June 2007.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and [XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fourth F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", W3C REC-xml-20060816, August 2006, Edition)", W3C REC-xml-20081126, November 2008,
<http://www.w3.org/TR/2006/REC-xml-20060816>. <http://www.w3.org/TR/2008/REC-xml-20081126/>.
15.2. Informative References 15.2. Informative References
[RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J. [RFC3253] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
Whitehead, "Versioning Extensions to WebDAV (Web Whitehead, "Versioning Extensions to WebDAV (Web
Distributed Authoring and Versioning)", RFC 3253, Distributed Authoring and Versioning)", RFC 3253,
March 2002. March 2002.
[RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web [RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
Distributed Authoring and Versioning (WebDAV) Access Distributed Authoring and Versioning (WebDAV) Access
skipping to change at page 44, line 18 skipping to change at page 44, line 18
B.18. Since draft-ietf-webdav-bind-19 B.18. Since draft-ietf-webdav-bind-19
Add and resolve issues "2.1.1-bind-loops", "2.1.1-cycles", "2.5-move- Add and resolve issues "2.1.1-bind-loops", "2.1.1-cycles", "2.5-move-
creating-cycles", "3.1-clarify-resource-id" and "4-precondition- creating-cycles", "3.1-clarify-resource-id" and "4-precondition-
language". language".
B.19. Since draft-ietf-webdav-bind-20 B.19. Since draft-ietf-webdav-bind-20
Use "urn:uuid:" instead of "opaquelocktoken:" scheme in examples. Use "urn:uuid:" instead of "opaquelocktoken:" scheme in examples.
Replace RFC518bis issue link by pointer to RFC Errata Page. Replace RFC2518bis issue link by pointer to RFC Errata Page.
Add issues "relation-to-deltav" and "status-codes". Add issues "relation-to-deltav" and "status-codes".
B.20. Since draft-ietf-webdav-bind-21 B.20. Since draft-ietf-webdav-bind-21
Resolve issues "relation-to-deltav" and "status-codes". Resolve issues "relation-to-deltav" and "status-codes".
Add correct content length values to examples (no change bars). Add correct content length values to examples (no change bars).
Appendix C. Resolved issues (to be removed by RFC Editor before B.21. Since draft-ietf-webdav-bind-22
publication)
Issues that were either rejected or resolved in this version of this
document.
C.1. status-codes
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2008JulSep/
0067.html>
julian.reschke@greenbytes.de (2008-09-26): The spec currently micro-
manages HTTP status codes: for instance, for a successful BIND it
requires status codes of 200 or 201, while - from an HTTP point of
view - a 204 should be acceptable as well. Proposal: rephrase the
text so that other success codes are acceptable as well, or remove
the normative language completely, point to RFC2616, and rely on
examples.
Resolution (2008-10-05): Also allow 204 where previously only 200 was
allowed. Add Location header to example using status 201.
C.2. relation-to-deltav
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2008JulSep/
0031.html>
werner.donne@re.be (2008-08-11): ...When supporting version Set "Intended Status" to "Experimental".
controlled collections, bindings may be introduced in a server
without actually issuing the BIND method. When a MOVE is performed
of a resource from one collection to another, both collections should
be checked out. An additional binding would be the result if one
collection would be subsequently checked in, while the check-out of
the other is undone. The resulting situation is meaningless if the
binding model is not supported...
Resolution (2008-10-04): Add new section containing that example. Update XML reference to "Extensible Markup Language (XML) 1.0 (Fifth
Edition)".
Appendix D. Open issues (to be removed by RFC Editor prior to Appendix C. Open issues (to be removed by RFC Editor prior to
publication) publication)
D.1. edit C.1. edit
Type: edit Type: edit
julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for julian.reschke@greenbytes.de (2004-05-30): Umbrella issue for
editorial fixes/enhancements. editorial fixes/enhancements.
Index Index
2 2
208 Already Reported (status code) 31, 39 208 Already Reported (status code) 31, 39
skipping to change at page 49, line 4 skipping to change at line 2026
Germany Germany
Email: julian.reschke@greenbytes.de Email: julian.reschke@greenbytes.de
Jim Whitehead Jim Whitehead
UC Santa Cruz, Dept. of Computer Science UC Santa Cruz, Dept. of Computer Science
1156 High Street 1156 High Street
Santa Cruz, CA 95064 Santa Cruz, CA 95064
Email: ejw@cse.ucsc.edu Email: ejw@cse.ucsc.edu
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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, 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
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
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.
 End of changes. 16 change blocks. 
68 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/