draft-ietf-webdav-bind-10.txt   draft-ietf-webdav-bind-11.txt 
Network Working Group G. Clemm Network Working Group G. Clemm
Internet-Draft IBM Internet-Draft IBM
Updates: 2518 (if approved) J. Crawford Updates: 2518 (if approved) J. Crawford
Expires: July 6, 2005 IBM Research Expires: August 21, 2005 IBM Research
J. Reschke J. Reschke
greenbytes greenbytes
J. Whitehead J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
January 5, 2005 February 17, 2005
Binding Extensions to Web Distributed Authoring and Versioning Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)
(WebDAV) draft-ietf-webdav-bind-11
draft-ietf-webdav-bind-10
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of Section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of 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 is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
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 other groups may also distribute working documents as Internet-
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 July 6, 2005. This Internet-Draft will expire on August 21, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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.
skipping to change at page 3, line 23 skipping to change at page 3, line 23
2.1.1 Bind loops . . . . . . . . . . . . . . . . . . . . . . 10 2.1.1 Bind loops . . . . . . . . . . . . . . . . . . . . . . 10
2.2 URI Mappings Created by a new Binding . . . . . . . . . . 10 2.2 URI Mappings Created by a new Binding . . . . . . . . . . 10
2.3 COPY and Bindings . . . . . . . . . . . . . . . . . . . . 11 2.3 COPY and Bindings . . . . . . . . . . . . . . . . . . . . 11
2.3.1 Example: COPY with 'Depth: infinity' in presence 2.3.1 Example: COPY with 'Depth: infinity' in presence
of bind loops . . . . . . . . . . . . . . . . . . . . 12 of bind loops . . . . . . . . . . . . . . . . . . . . 12
2.3.2 Example: COPY with 'Depth: infinity' with multiple 2.3.2 Example: COPY with 'Depth: infinity' with multiple
bindings to a leaf resource . . . . . . . . . . . . . 14 bindings to a leaf resource . . . . . . . . . . . . . 14
2.4 DELETE and Bindings . . . . . . . . . . . . . . . . . . . 15 2.4 DELETE and Bindings . . . . . . . . . . . . . . . . . . . 15
2.5 MOVE and Bindings . . . . . . . . . . . . . . . . . . . . 15 2.5 MOVE and Bindings . . . . . . . . . . . . . . . . . . . . 15
2.6 PROPFIND and Bindings . . . . . . . . . . . . . . . . . . 16 2.6 PROPFIND and Bindings . . . . . . . . . . . . . . . . . . 16
2.7 Determining Whether Two Bindings Are to the Same 2.7 UNLOCK and Bindings . . . . . . . . . . . . . . . . . . . 16
Resource . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.8 Determining Whether Two Bindings Are to the Same
2.8 Discovering the Bindings to a Resource . . . . . . . . . . 17 Resource . . . . . . . . . . . . . . . . . . . . . . . . . 17
3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.9 Discovering the Bindings to a Resource . . . . . . . . . . 17
3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 DAV:resource-id Property . . . . . . . . . . . . . . . . . 18 3.1 DAV:resource-id Property . . . . . . . . . . . . . . . . . 18
3.2 DAV:parent-set Property . . . . . . . . . . . . . . . . . 18 3.2 DAV:parent-set Property . . . . . . . . . . . . . . . . . 18
3.2.1 Example for DAV:parent-set property . . . . . . . . . 18 3.2.1 Example for DAV:parent-set property . . . . . . . . . 19
4. BIND Method . . . . . . . . . . . . . . . . . . . . . . . . . 19 4. BIND Method . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.1 Example: BIND . . . . . . . . . . . . . . . . . . . . . . 22 4.1 Example: BIND . . . . . . . . . . . . . . . . . . . . . . 22
5. UNBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 22 5. UNBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 22
5.1 Example: UNBIND . . . . . . . . . . . . . . . . . . . . . 24 5.1 Example: UNBIND . . . . . . . . . . . . . . . . . . . . . 24
6. REBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 24 6. REBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1 Example: REBIND . . . . . . . . . . . . . . . . . . . . . 26 6.1 Example: REBIND . . . . . . . . . . . . . . . . . . . . . 26
6.2 Example: REBIND in presence of locks and bind loops . . . 27 6.2 Example: REBIND in presence of locks and bind loops . . . 27
7. Additional Status Codes . . . . . . . . . . . . . . . . . . . 29 7. Additional Status Codes . . . . . . . . . . . . . . . . . . . 29
7.1 208 Already Reported . . . . . . . . . . . . . . . . . . . 29 7.1 208 Already Reported . . . . . . . . . . . . . . . . . . . 29
7.1.1 Example: PROPFIND by bind-aware client . . . . . . . . 30 7.1.1 Example: PROPFIND by bind-aware client . . . . . . . . 30
7.1.2 Example: PROPFIND by non-bind-aware client . . . . . . 31 7.1.2 Example: PROPFIND by non-bind-aware client . . . . . . 31
7.2 506 Loop Detected . . . . . . . . . . . . . . . . . . . . 32 7.2 506 Loop Detected . . . . . . . . . . . . . . . . . . . . 32
8. Capability discovery . . . . . . . . . . . . . . . . . . . . . 32 8. Capability discovery . . . . . . . . . . . . . . . . . . . . . 32
8.1 OPTIONS method . . . . . . . . . . . . . . . . . . . . . . 32 8.1 OPTIONS method . . . . . . . . . . . . . . . . . . . . . . 32
8.2 'DAV' request header . . . . . . . . . . . . . . . . . . . 32 8.2 'DAV' request header . . . . . . . . . . . . . . . . . . . 32
8.2.1 Generic syntax . . . . . . . . . . . . . . . . . . . . 32 8.2.1 Generic syntax . . . . . . . . . . . . . . . . . . . . 32
8.2.2 Client compliance class 'bind' . . . . . . . . . . . . 33 8.2.2 Client compliance class 'bind' . . . . . . . . . . . . 33
9. Security Considerations . . . . . . . . . . . . . . . . . . . 33 9. Relationship to WebDAV Access Control Protocol . . . . . . . . 33
9.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . 33 10. Security Considerations . . . . . . . . . . . . . . . . . . 33
9.2 Bind Loops . . . . . . . . . . . . . . . . . . . . . . . . 33 10.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . 33
9.3 Bindings, and Denial of Service . . . . . . . . . . . . . 33 10.2 Bind Loops . . . . . . . . . . . . . . . . . . . . . . . . 33
9.4 Private Locations May Be Revealed . . . . . . . . . . . . 34 10.3 Bindings, and Denial of Service . . . . . . . . . . . . . 34
9.5 DAV:parent-set and Denial of Service . . . . . . . . . . . 34 10.4 Private Locations May Be Revealed . . . . . . . . . . . . 34
10. Internationalization Considerations . . . . . . . . . . . . 34 10.5 DAV:parent-set and Denial of Service . . . . . . . . . . . 34
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 34 11. Internationalization Considerations . . . . . . . . . . . . 34
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . 34
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 35 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 34
13.1 Normative References . . . . . . . . . . . . . . . . . . . . 35 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
13.2 Informative References . . . . . . . . . . . . . . . . . . . 35 14.1 Normative References . . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 35 14.2 Informative References . . . . . . . . . . . . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 36
A. Change Log (to be removed by RFC Editor before publication) . 36 A. Change Log (to be removed by RFC Editor before publication) . 36
A.1 Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . 36 A.1 Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . 36
A.2 Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 36 A.2 Since draft-ietf-webdav-bind-03 . . . . . . . . . . . . . 37
A.3 Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 36 A.3 Since draft-ietf-webdav-bind-04 . . . . . . . . . . . . . 37
A.4 Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 37 A.4 Since draft-ietf-webdav-bind-05 . . . . . . . . . . . . . 37
A.5 Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 37 A.5 Since draft-ietf-webdav-bind-06 . . . . . . . . . . . . . 37
A.6 Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 37 A.6 Since draft-ietf-webdav-bind-07 . . . . . . . . . . . . . 37
A.7 Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 37 A.7 Since draft-ietf-webdav-bind-08 . . . . . . . . . . . . . 37
A.8 Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 37 A.8 Since draft-ietf-webdav-bind-09 . . . . . . . . . . . . . 37
B. Resolved issues (to be removed by RFC Editor before A.9 Since draft-ietf-webdav-bind-10 . . . . . . . . . . . . . 38
publication) . . . . . . . . . . . . . . . . . . . . . . . . . 37 B. Open issues (to be removed by RFC Editor prior to
B.1 uri_draft_ref . . . . . . . . . . . . . . . . . . . . . . 37 publication) . . . . . . . . . . . . . . . . . . . . . . . . . 38
B.2 2.6_bindings_vs_properties . . . . . . . . . . . . . . . . 38 B.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
B.3 2.6_when_do_ids_change . . . . . . . . . . . . . . . . . . 38 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
B.4 6.1_rebind_vs_locks . . . . . . . . . . . . . . . . . . . 38 Intellectual Property and Copyright Statements . . . . . . . . 41
C. Open issues (to be removed by RFC Editor prior to
publication) . . . . . . . . . . . . . . . . . . . . . . . . . 39
C.1 edit . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
C.2 3.1_uuids . . . . . . . . . . . . . . . . . . . . . . . . 39
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Intellectual Property and Copyright Statements . . . . . . . . 42
1. Introduction 1. Introduction
This specification extends the WebDAV Distributed Authoring Protocol This specification extends the WebDAV Distributed Authoring Protocol
to enable clients to create new access paths to existing resources. to enable clients to create new access paths to existing resources.
This capability is useful for several reasons: 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 7, line 15 skipping to change at page 7, line 15
can be thought of as (U => R). Since a resource can represent can be thought of as (U => R). Since a resource can represent
items that are not network retrievable, as well as those that are, items that are not network retrievable, as well as those that are,
it is possible for a resource to have zero, one, or many URI it is possible for a resource to have zero, one, or many URI
mappings. Mapping a resource to an "http" scheme URI makes it mappings. Mapping a resource to an "http" scheme URI makes it
possible to submit HTTP protocol requests to the resource using possible to submit HTTP protocol requests to the resource using
the URI. the URI.
Path Segment Path Segment
Informally, the characters found between slashes ("/") in a URI. Informally, the characters found between slashes ("/") in a URI.
Formally, as defined in section 3.3 of Formally, as defined in section 3.3 of [RFC3986].
[draft-fielding-uri-rfc2396bis].
Binding Binding
A relation between a single path segment (in a collection) and a A relation between a single path segment (in a collection) and a
resource. A binding is part of the state of a collection. If two resource. A binding is part of the state of a collection. If two
different collections contain a binding between the same path different collections contain a binding between the same path
segment and the same resource, these are two distinct bindings. segment and the same resource, these are two distinct bindings.
So for a collection C, a path segment S, and a resource R, the So for a collection C, a path segment S, and a resource R, the
binding can be thought of as C:(S -> R). Bindings create URI binding can be thought of as C:(S -> R). Bindings create URI
mappings, and hence allow requests to be sent to a single resource mappings, and hence allow requests to be sent to a single resource
skipping to change at page 9, line 33 skipping to change at page 9, line 31
with a binding in that collection accessible via a new URI, and thus with a binding in that collection accessible via a new URI, and thus
creates new URI mappings to those resources but no new bindings. creates new URI mappings to those resources but no new bindings.
For example, suppose a new binding CollY is created for collection C1 For example, suppose a new binding CollY is created for collection C1
in the figure below. It immediately becomes possible to access in the figure below. It immediately becomes possible to access
resource R1 using the URI /CollY/x.gif and to access resource R2 resource R1 using the URI /CollY/x.gif and to access resource R2
using the URI /CollY/y.jpg, but no new bindings for these child using the URI /CollY/y.jpg, but no new bindings for these child
resources were created. This is because bindings are part of the resources were created. This is because bindings are part of the
state of a collection, and associate a URI that is relative to that state of a collection, and associate a URI that is relative to that
collection with its target resource. No change to the bindings in collection with its target resource. No change to the bindings in
Collection C1 is needed to make its children accessible using Collection C1 is needed to make its children accessible using /CollY/
/CollY/x.gif and /CollY/y.jpg. x.gif and /CollY/y.jpg.
+-------------------------+ +-------------------------+
| Root Collection | | Root Collection |
| bindings: | | bindings: |
| CollX CollY | | CollX CollY |
+-------------------------+ +-------------------------+
| / | /
| / | /
| / | /
+------------------+ +------------------+
skipping to change at page 10, line 15 skipping to change at page 10, line 14
+-------------+ +-------------+ +-------------+ +-------------+
2.1.1 Bind loops 2.1.1 Bind loops
Bindings to collections can result in loops, which servers MUST Bindings to collections can result in loops, which servers MUST
detect when processing "Depth: infinity" requests. It is sometimes detect when processing "Depth: infinity" requests. It is sometimes
possible to complete an operation in spite of the presence of a loop. possible to complete an operation in spite of the presence of a loop.
For instance, a PROPFIND can still succeed if the server uses the new For instance, a PROPFIND can still succeed if the server uses the new
status code 208 (Already Reported) defined in Section 7.1. status code 208 (Already Reported) defined in Section 7.1.
However, the 506 (Loop Detected) status code is defined in Section However, the 506 (Loop Detected) status code is defined in
7.2 for use in contexts where an operation is terminated because a Section 7.2 for use in contexts where an operation is terminated
loop was encountered. because a loop was encountered.
2.2 URI Mappings Created by a new Binding 2.2 URI Mappings Created by a new Binding
Suppose a binding from "Binding-Name" to resource R is to be added to Suppose a binding from "Binding-Name" to resource R is to be added to
a collection, C. Then if C-MAP is the set of URIs that were mapped a collection, C. Then if C-MAP is the set of URIs that were mapped to
to C before the BIND request, then for each URI "C-URI" in C-MAP, the C before the BIND request, then for each URI "C-URI" in C-MAP, the
URI "C-URI/Binding-Name" is mapped to resource R following the BIND URI "C-URI/Binding-Name" is mapped to resource R following the BIND
request. request.
For example, if a binding from "foo.html" to R is added to a For example, if a binding from "foo.html" to R is added to a
collection C, and if the following URIs are mapped to C: collection C, and if the following URIs are mapped to C:
http://www.example.com/A/1/ http://www.example.com/A/1/
http://example.com/A/one/ http://example.com/A/one/
then the following new mappings to R are introduced: then the following new mappings to R are introduced:
skipping to change at page 12, line 47 skipping to change at page 12, line 47
+-------------+ | bindings: | | +-------------+ | bindings: | |
| y.gif CollZ | | | y.gif CollZ | |
+------------------+ | +------------------+ |
| | | | | |
| +--------+ | +--------+
| |
+-------------+ +-------------+
| Resource R2 | | Resource R2 |
+-------------+ +-------------+
If a COPY with Depth inifinity is submitted to /CollX, with If a COPY with Depth infinity is submitted to /CollX, with
destination of /CollA, the outcome of the copy operation is: destination of /CollA, the outcome of the copy operation is:
+------------------+ +------------------+
| Root Collection | | Root Collection |
| bindings: | | bindings: |
| CollX CollA | | CollX CollA |
+------------------+ +------------------+
| | | |
| +---------------------------+ | +---------------------------+
| | | |
skipping to change at page 15, line 23 skipping to change at page 15, line 23
removes the binding named "x" from "/a" but MUST NOT remove the removes the binding named "x" from "/a" but MUST NOT remove the
binding named "y" from "/b" (i.e. after the DELETE, "/y/b" continues binding named "y" from "/b" (i.e. after the DELETE, "/y/b" continues
to identify the resource R). In particular, although Section 8.6.1 to identify the resource R). In particular, although Section 8.6.1
of [RFC2518] states that during DELETE processing, a server "MUST of [RFC2518] states that during DELETE processing, a server "MUST
remove any URI for the resource identified by the Request-URI from remove any URI for the resource identified by the Request-URI from
collections which contain it as a member", a server that supports the collections which contain it as a member", a server that supports the
binding protocol MUST NOT follow this requirement. binding protocol MUST NOT follow this requirement.
When DELETE is applied to a collection, it MUST NOT modify the When DELETE is applied to a collection, it MUST NOT modify the
membership of any other collection that is not itself a member of the membership of any other collection that is not itself a member of the
collection being deleted. For example, if both "/a/.../x" and collection being deleted. For example, if both "/a/.../x" and "/b/
"/b/.../y" identify the same collection, C, then applying DELETE to .../y" identify the same collection, C, then applying DELETE to "/a"
"/a" must not delete an internal member from C or from any other must not delete an internal member from C or from any other
collection that is a member of C, because that would modify the collection that is a member of C, because that would modify the
membership of "/b". membership of "/b".
If a collection supports the UNBIND method (see Section 5), a DELETE If a collection supports the UNBIND method (see Section 5), a DELETE
of an internal member of a collection MAY be implemented as an UNBIND of an internal member of a collection MAY be implemented as an UNBIND
request. In this case, applying DELETE to a Request-URI has the request. In this case, applying DELETE to a Request-URI has the
effect of removing the binding identified by the final segment of the effect of removing the binding identified by the final segment of the
Request-URI from the collection identified by the Request-URI minus Request-URI from the collection identified by the Request-URI minus
its final segment. Although [RFC2518] allows a DELETE to be a its final segment. Although [RFC2518] allows a DELETE to be a non-
non-atomic operation, when the DELETE operation is implemented as an atomic operation, when the DELETE operation is implemented as an
UNBIND, the operation is atomic. In particular, a DELETE on a UNBIND, the operation is atomic. In particular, a DELETE on a
hierarchy of resources is simply the removal of a binding to the hierarchy of resources is simply the removal of a binding to the
collection identified by the Request-URI. collection identified by the Request-URI.
2.5 MOVE and Bindings 2.5 MOVE and Bindings
When MOVE is applied to a resource, the other bindings to that When MOVE is applied to a resource, the other bindings to that
resource MUST be unaffected, and if the resource being moved is a resource MUST be unaffected, and if the resource being moved is a
collection, the bindings to any members of that collection MUST be collection, the bindings to any members of that collection MUST be
unaffected. Also, if MOVE is used with Overwrite:T to delete an unaffected. Also, if MOVE is used with Overwrite:T to delete an
skipping to change at page 16, line 43 skipping to change at page 16, line 43
URI-1 URI-2 URI-X URI-1 URI-2 URI-X
| | | | | |
| | | <---- URI Mappings | | | <---- URI Mappings
| | | | | |
+---------------------+ +---------------------+
| Resource R | | Resource R |
+---------------------+ +---------------------+
2.6 PROPFIND and Bindings 2.6 PROPFIND and Bindings
Consistent with [RFC2518] the value of a dead property MUST be, and Consistent with [RFC2518] the value of a dead property MUST be
the value of a live property SHOULD be, independent of the number of independent of the number of bindings to its host resource or of the
bindings to its host resource or of the path submitted to PROPFIND. path submitted to PROPFIND.
2.7 Determining Whether Two Bindings Are to the Same Resource 2.7 UNLOCK and Bindings
Due to the specific language used in section 8.11 of [RFC2518], it
might be thought that an UNLOCK request to a locked resource would
unlock just the particular binding expressed by the Request-URI,
rather than the resource identified by that URI. This is not the
case, however. Section 6 of [RFC2518] clearly states that locks are
on resources, not URIs, so the server MUST allow UNLOCK to be used to
unlock a locked resource through any binding to that resource. The
authors of this specification anticipate and recommend that future
revisions of [RFC2518] maintain this behavior.
2.8 Determining Whether Two Bindings Are to the Same Resource
It is useful to have some way of determining whether two bindings are It is useful to have some way of determining whether two bindings are
to the same resource. Two resources might have identical contents to the same resource. Two resources might have identical contents
and properties, but not be the same resource (e.g. an update to one and properties, but not be the same resource (e.g. an update to one
resource does not affect the other resource). resource does not affect the other resource).
The REQUIRED DAV:resource-id property defined in Section 3.1 is a The REQUIRED DAV:resource-id property defined in Section 3.1 is a
resource identifier, which MUST be unique across all resources for resource identifier, which MUST be unique across all resources for
all time. If the values of DAV:resource-id returned by PROPFIND all time. If the values of DAV:resource-id returned by PROPFIND
requests through two bindings are identical character by character, requests through two bindings are identical character by character,
the client can be assured that the two bindings are to the same the client can be assured that the two bindings are to the same
resource. resource.
The DAV:resource-id property is created, and its value assigned, when The DAV:resource-id property is created, and its value assigned, when
the resource is created. The value of DAV:resource-id MUST NOT be the resource is created. The value of DAV:resource-id MUST NOT be
changed. Even after the resource is no longer accessible through any changed. Even after the resource is no longer accessible through any
URI, that value MUST NOT be reassigned to another resource's URI, that value MUST NOT be reassigned to another resource's DAV:
DAV:resource-id property. resource-id property.
Any method that creates a new resource MUST assign a new, unique Any method that creates a new resource MUST assign a new, unique
value to its DAV:resource-id property. For example, a PUT applied to value to its DAV:resource-id property. For example, a PUT applied to
a null resource, COPY (when not overwriting an existing target) and a null resource, COPY (when not overwriting an existing target) and
CHECKIN (see [RFC3253], section 4.4) must assign a new, unique value CHECKIN (see [RFC3253], section 4.4) must assign a new, unique value
to the DAV:resource-id property of the new resource they create. to the DAV:resource-id property of the new resource they create.
On the other hand, any method that affects an existing resource must On the other hand, any method that affects an existing resource must
not change the value of its DAV:resource-id property. Specifically, not change the value of its DAV:resource-id property. Specifically,
a PUT or a COPY that updates an existing resource must not change the a PUT or a COPY that updates an existing resource must not change the
value of its DAV:resource-id property. A REBIND, since it does not value of its DAV:resource-id property. A REBIND, since it does not
create a new resource, but only changes the location of an existing create a new resource, but only changes the location of an existing
resource, must not change the value of the DAV:resource-id property. resource, must not change the value of the DAV:resource-id property.
2.8 Discovering the Bindings to a Resource 2.9 Discovering the Bindings to a Resource
An OPTIONAL DAV:parent-set property on a resource provides a list of An OPTIONAL DAV:parent-set property on a resource provides a list of
the bindings that associate a collection and a URI segment with that the bindings that associate a collection and a URI segment with that
resource. If the DAV:parent-set property exists on a given resource, resource. If the DAV:parent-set property exists on a given resource,
it MUST contain a complete list of all bindings to that resource that it MUST contain a complete list of all bindings to that resource that
the client is authorized to see. When deciding whether to support the client is authorized to see. When deciding whether to support
the DAV:parent-set property, server implementers / administrators the DAV:parent-set property, server implementers / administrators
should balance the benefits it provides against the cost of should balance the benefits it provides against the cost of
maintaining the property and the security risks enumerated in maintaining the property and the security risks enumerated in
Sections 9.4 and 9.5. Sections 10.4 and 10.5.
3. Properties 3. Properties
The bind feature introduces the following properties for a resource. The bind feature introduces the properties defined below.
A DAV:allprop PROPFIND request SHOULD NOT return any of the A DAV:allprop PROPFIND request SHOULD NOT return any of the
properties defined by this document. This allows a binding server to properties defined by this document. This allows a binding server to
perform efficiently when a naive client, which does not understand perform efficiently when a naive client, which does not understand
the cost of asking a server to compute all possible live properties, the cost of asking a server to compute all possible live properties,
issues a DAV:allprop PROPFIND request. issues a DAV:allprop PROPFIND request.
3.1 DAV:resource-id Property 3.1 DAV:resource-id Property
The DAV:resource-id property is a REQUIRED property that enables The DAV:resource-id property is a REQUIRED property that enables
clients to determine whether two bindings are to the same resource. clients to determine whether two bindings are to the same resource.
The value of DAV:resource-id is a URI, and may use any registered URI The value of DAV:resource-id is a URI, and may use any registered URI
scheme that guarantees the uniqueness of the value across all scheme that guarantees the uniqueness of the value across all
resources for all time (e.g. the opaquelocktoken: scheme defined in resources for all time (e.g. the urn:uuid: URN namespace defined in
[RFC2518]). [draft-mealling-uuid-urn] or the opaquelocktoken: URI scheme defined
in [RFC2518]).
<!ELEMENT resource-id (href)> <!ELEMENT resource-id (href)>
3.2 DAV:parent-set Property 3.2 DAV:parent-set Property
The DAV:parent-set property is an OPTIONAL property that enables The DAV:parent-set property is an OPTIONAL property that enables
clients to discover what collections contain a binding to this clients to discover what collections contain a binding to this
resource (i.e. what collections have that resource as an internal resource (i.e. what collections have that resource as an internal
member). It contains an of href/segment pair for each collection member). It contains an of href/segment pair for each collection
that has a binding to the resource. The href identifies the that has a binding to the resource. The href identifies the
skipping to change at page 18, line 36 skipping to change at page 18, line 49
resource in that collection. resource in that collection.
A given collection MUST appear only once in the DAV:parent-set for 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 any given binding, even if there are multiple URI mappings to that
collection. collection.
<!ELEMENT parent-set (parent)*> <!ELEMENT parent-set (parent)*>
<!ELEMENT parent (href, segment)> <!ELEMENT parent (href, segment)>
<!ELEMENT segment (#PCDATA)> <!ELEMENT segment (#PCDATA)>
<!-- PCDATA value: segment, as defined in section 3.3 of <!-- PCDATA value: segment, as defined in section 3.3 of
[draft-fielding-uri-rfc2396bis] --> [RFC3986] -->
3.2.1 Example for DAV:parent-set property 3.2.1 Example for DAV:parent-set property
For example, if collection C1 is mapped to both /CollX and /CollY, 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 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 [/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 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, 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, R1 (i.e. both [/CollX, x.gif] and [/CollX, y.gif] or, alternatively,
both [/CollY, x.gif] and [/CollY, y.gif]). both [/CollY, x.gif] and [/CollY, y.gif]).
skipping to change at page 19, line 41 skipping to change at page 19, line 51
<segment>x.gif</segment> <segment>x.gif</segment>
</parent> </parent>
<parent> <parent>
<href>/CollX</href> <href>/CollX</href>
<segment>y.gif</segment> <segment>y.gif</segment>
</parent> </parent>
</parent-set> </parent-set>
4. BIND Method 4. BIND Method
The BIND method modifies the collection identified by the The BIND method modifies the collection identified by the Request-
Request-URI, by adding a new binding from the segment specified in URI, by adding a new binding from the segment specified in the BIND
the BIND body to the resource identified in the BIND body. body to the resource identified in the BIND body.
If a server cannot guarantee the integrity of the binding, the BIND If a server cannot guarantee the integrity of the binding, the BIND
request MUST fail. Note that it is especially difficult to maintain request MUST fail. Note that it is especially difficult to maintain
the integrity of cross-server bindings. Unless the server where the the integrity of cross-server bindings. Unless the server where the
resource resides knows about all bindings on all servers to that resource resides knows about all bindings on all servers to that
resource, it may unwittingly destroy the resource or make it resource, it may unwittingly destroy the resource or make it
inaccessible without notifying another server that manages a binding inaccessible without notifying another server that manages a binding
to the resource. For example, if server A permits creation of a to the resource. For example, if server A permits creation of a
binding to a resource on server B, server A must notify server B binding to a resource on server B, server A must notify server B
about its binding and must have an agreement with B that B will not about its binding and must have an agreement with B that B will not
skipping to change at page 20, line 36 skipping to change at page 20, line 46
The request body MUST be a DAV:bind XML element. The request body MUST be a DAV:bind XML element.
<!ELEMENT bind (segment, href)> <!ELEMENT bind (segment, href)>
If the request succeeds, the server MUST return 201 (Created) when If the request succeeds, the server MUST return 201 (Created) when
a new binding was created and 200 (OK) when an existing binding a new binding was created and 200 (OK) when an existing binding
was replaced. was replaced.
If a response body for a successful request is included, it MUST If a response body for a successful request is included, it MUST
be a DAV:bind-response XML element. Note that this document does be a DAV:bind-response XML element. Note that this document does
not define any elements for the BIND response body, but the not define any elements for the BIND response body, but the DAV:
DAV:bind-response element is defined to ensure interoperability bind-response element is defined to ensure interoperability
between future extensions that do define elements for the BIND between future extensions that do define elements for the BIND
response body. response body.
<!ELEMENT bind-response ANY> <!ELEMENT bind-response ANY>
Preconditions: Preconditions:
(DAV:bind-into-collection): The Request-URI MUST identify a (DAV:bind-into-collection): The Request-URI MUST identify a
collection. collection.
(DAV:bind-source-exists): The DAV:href element MUST identify a (DAV:bind-source-exists): The DAV:href element MUST identify a
resource. resource.
(DAV:binding-allowed): The resource identified by the DAV:href (DAV:binding-allowed): The resource identified by the DAV:href
supports multiple bindings to it. supports multiple bindings to it.
skipping to change at page 21, line 6 skipping to change at page 21, line 15
(DAV:bind-into-collection): The Request-URI MUST identify a (DAV:bind-into-collection): The Request-URI MUST identify a
collection. collection.
(DAV:bind-source-exists): The DAV:href element MUST identify a (DAV:bind-source-exists): The DAV:href element MUST identify a
resource. resource.
(DAV:binding-allowed): The resource identified by the DAV:href (DAV:binding-allowed): The resource identified by the DAV:href
supports multiple bindings to it. supports multiple bindings to it.
(DAV:cross-server-binding): If the resource identified by the (DAV:cross-server-binding): If the resource identified by the DAV:
DAV:href element in the request body is on another server from the href element in the request body is on another server from the
collection identified by the Request-URI, the server MUST support collection identified by the Request-URI, the server MUST support
cross-server bindings. cross-server bindings.
(DAV:name-allowed): The name specified by the DAV:segment is (DAV:name-allowed): The name specified by the DAV:segment is
available for use as a new binding name. available for use as a new binding name.
(DAV:can-overwrite): If the collection already contains a binding (DAV:can-overwrite): If the collection already contains a binding
with the specified path segment, and if an Overwrite header is with the specified path segment, and if an Overwrite header is
included, the value of the Overwrite header MUST be "T". included, the value of the Overwrite header MUST be "T".
skipping to change at page 22, line 33 skipping to change at page 22, line 33
The server added a new binding to the collection, The server added a new binding to the collection,
"http://www.example.com/CollY", associating "bar.html" with the "http://www.example.com/CollY", associating "bar.html" with the
resource identified by the URI resource identified by the URI
"http://www.example.com/CollX/foo.html". Clients can now use the URI "http://www.example.com/CollX/foo.html". Clients can now use the URI
"http://www.example.com/CollY/bar.html" to submit requests to that "http://www.example.com/CollY/bar.html" to submit requests to that
resource. resource.
5. UNBIND Method 5. UNBIND Method
The UNBIND method modifies the collection identified by the The UNBIND method modifies the collection identified by the Request-
Request-URI, by removing the binding identified by the segment URI, by removing the binding identified by the segment specified in
specified in the UNBIND body. the UNBIND body.
Once a resource is unreachable by any URI mapping, the server MAY Once a resource is unreachable by any URI mapping, the server MAY
reclaim system resources associated with that resource. If UNBIND reclaim system resources associated with that resource. If UNBIND
removes a binding to a resource, but there remain URI mappings to removes a binding to a resource, but there remain URI mappings to
that resource, the server MUST NOT reclaim system resources that resource, the server MUST NOT reclaim system resources
associated with the resource. associated with the resource.
If an UNBIND request fails, the server state preceding the request If an UNBIND request fails, the server state preceding the request
MUST be restored. This method is unsafe and idempotent (see MUST be restored. This method is unsafe and idempotent (see
[RFC2616], section 9.1). [RFC2616], section 9.1).
skipping to change at page 25, line 22 skipping to change at page 25, line 22
<!ELEMENT rebind-response ANY> <!ELEMENT rebind-response ANY>
Preconditions: Preconditions:
(DAV:rebind-into-collection): The Request-URI MUST identify a (DAV:rebind-into-collection): The Request-URI MUST identify a
collection. collection.
(DAV:rebind-source-exists): The DAV:href element MUST identify a (DAV:rebind-source-exists): The DAV:href element MUST identify a
resource. resource.
(DAV:cross-server-binding): If the resource identified by the (DAV:cross-server-binding): If the resource identified by the DAV:
DAV:href element in the request body is on another server from the href element in the request body is on another server from the
collection identified by the Request-URI, the server MUST support collection identified by the Request-URI, the server MUST support
cross-server bindings. cross-server bindings.
(DAV:name-allowed): The name specified by the DAV:segment is (DAV:name-allowed): The name specified by the DAV:segment is
available for use as a new binding name. available for use as a new binding name.
(DAV:can-overwrite): If the collection already contains a binding (DAV:can-overwrite): If the collection already contains a binding
with the specified path segment, and if an Overwrite header is with the specified path segment, and if an Overwrite header is
included, the value of the Overwrite header MUST be "T". included, the value of the Overwrite header MUST be "T".
skipping to change at page 29, line 43 skipping to change at page 29, line 43
+---------------------------+ +---------------------------+
| Resource R2 | | Resource R2 |
| (inherited lock from C1) | | (inherited lock from C1) |
| (lock token L1) | | (lock token L1) |
+---------------------------+ +---------------------------+
7. Additional Status Codes 7. Additional Status Codes
7.1 208 Already Reported 7.1 208 Already Reported
The 208 (Already Reported) status code can be used inside a The 208 (Already Reported) status code can be used inside a DAV:
DAV:propstat response element to avoid enumerating the internal propstat response element to avoid enumerating the internal members
members of multiple bindings to the same collection repeatedly. For of multiple bindings to the same collection repeatedly. For each
each binding to a collection inside the request's scope, only one binding to a collection inside the request's scope, only one will be
will be reported with a 200 status, while subsequent DAV:response reported with a 200 status, while subsequent DAV:response elements
elements for all other bindings will use the 208 status, and no for all other bindings will use the 208 status, and no DAV:response
DAV:response elements for their descendants are included. elements for their descendants are included.
Note that the 208 status will only occur for "Depth: infinity" Note that the 208 status will only occur for "Depth: infinity"
requests, and that it is of particular importance when the multiple requests, and that it is of particular importance when the multiple
collection bindings cause a bind loop as discussed in Section 2.2. collection bindings cause a bind loop as discussed in Section 2.2.
A client can request the DAV:resourceid property in a PROPFIND A client can request the DAV:resource-id property in a PROPFIND
request to guarantee that they can accurately reconstruct the binding request to guarantee that they can accurately reconstruct the binding
structure of a collection with multiple bindings to a single structure of a collection with multiple bindings to a single
resource. resource.
For backward compatibility with clients not aware of the 208 status For backward compatibility with clients not aware of the 208 status
code appearing in multistatus response bodies, it SHOULD NOT be used code appearing in multistatus response bodies, it SHOULD NOT be used
unless the client has signalled support for this specification using unless the client has signalled support for this specification using
the "DAV" request header (see Section 8.2). Instead, a 506 status the "DAV" request header (see Section 8.2). Instead, a 506 status
should be returned when a binding loop is discovered. This allows should be returned when a binding loop is discovered. This allows
the server to return the 506 as the top level return status, if it the server to return the 506 as the top level return status, if it
skipping to change at page 31, line 13 skipping to change at page 31, line 13
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.example.com/Coll/</D:href> <D:href>http://www.example.com/Coll/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Loop Demo</D:displayname> <D:displayname>Loop Demo</D:displayname>
<D:resource-id> <D:resource-id>
<D:href <D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href> >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href>
</D:resource-id> </D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.example.com/Coll/Foo</D:href> <D:href>http://www.example.com/Coll/Foo</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Bird Inventory</D:displayname> <D:displayname>Bird Inventory</D:displayname>
<D:resource-id> <D:resource-id>
<D:href <D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf9</D:href> >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf9</D:href>
</D:resource-id> </D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.example.com/Coll/Bar</D:href> <D:href>http://www.example.com/Coll/Bar</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Loop Demo</D:displayname> <D:displayname>Loop Demo</D:displayname>
<D:resource-id> <D:resource-id>
<D:href <D:href
>opaquelocktoken:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href> >urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf8</D:href>
</D:resource-id> </D:resource-id>
</D:prop> </D:prop>
<D:status>HTTP/1.1 208 Already Reported</D:status> <D:status>HTTP/1.1 208 Already Reported</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
7.1.2 Example: PROPFIND by non-bind-aware client 7.1.2 Example: PROPFIND by non-bind-aware client
In this example, the client isn't aware of the 208 status code In this example, the client isn't aware of the 208 status code
skipping to change at page 33, line 21 skipping to change at page 33, line 21
cacheable or the server MUST mark the response accordingly using the cacheable or the server MUST mark the response accordingly using the
"Vary" header (see [RFC2616], section 14.44). "Vary" header (see [RFC2616], section 14.44).
8.2.2 Client compliance class 'bind' 8.2.2 Client compliance class 'bind'
Clients SHOULD signal support for all MUST level requirements and Clients SHOULD signal support for all MUST level requirements and
REQUIRED features by submitting a "DAV" request header containing the REQUIRED features by submitting a "DAV" request header containing the
compliance class name "bind". In particular, the client MUST compliance class name "bind". In particular, the client MUST
understand the 208 status code defined in Section 7.1. understand the 208 status code defined in Section 7.1.
9. Security Considerations 9. Relationship to WebDAV Access Control Protocol
BIND and REBIND behave the same as MOVE with respect to the DAV:acl
property (see [RFC3744], section 7.3).
10. Security Considerations
This section is provided to make WebDAV implementors aware of the This section is provided to make WebDAV implementors aware of the
security implications of this protocol. security implications of this protocol.
All of the security considerations of HTTP/1.1 and the WebDAV All of the security considerations of HTTP/1.1 and the WebDAV
Distributed Authoring Protocol specification also apply to this Distributed Authoring Protocol specification also apply to this
protocol specification. In addition, bindings introduce several new protocol specification. In addition, bindings introduce several new
security concerns and increase the risk of some existing threats. security concerns and increase the risk of some existing threats.
These issues are detailed below. These issues are detailed below.
9.1 Privacy Concerns 10.1 Privacy Concerns
In a context where cross-server bindings are supported, creating In a context where cross-server bindings are supported, creating
bindings on a trusted server may make it possible for a hostile agent bindings on a trusted server may make it possible for a hostile agent
to induce users to send private information to a target on a to induce users to send private information to a target on a
different server. different server.
9.2 Bind Loops 10.2 Bind Loops
Although bind loops were already possible in HTTP 1.1, the Although bind loops were already possible in HTTP 1.1, the
introduction of the BIND method creates a new avenue for clients to introduction of the BIND method creates a new avenue for clients to
create loops accidentally or maliciously. If the binding and its create loops accidentally or maliciously. If the binding and its
target are on the same server, the server may be able to detect BIND target are on the same server, the server may be able to detect BIND
requests that would create loops. Servers are required to detect requests that would create loops. Servers are required to detect
loops that are caused by bindings to collections during the loops that are caused by bindings to collections during the
processing of any requests with "Depth: infinity". processing of any requests with "Depth: infinity".
9.3 Bindings, and Denial of Service 10.3 Bindings, and Denial of Service
Denial of service attacks were already possible by posting URIs that Denial of service attacks were already possible by posting URIs that
were intended for limited use at heavily used Web sites. The were intended for limited use at heavily used Web sites. The
introduction of BIND creates a new avenue for similar denial of introduction of BIND creates a new avenue for similar denial of
service attacks. If cross-server bindings are supported, clients can service attacks. If cross-server bindings are supported, clients can
now create bindings at heavily used sites to target locations that now create bindings at heavily used sites to target locations that
were not designed for heavy usage. were not designed for heavy usage.
9.4 Private Locations May Be Revealed 10.4 Private Locations May Be Revealed
If the DAV:parent-set property is maintained on a resource, the If the DAV:parent-set property is maintained on a resource, the
owners of the bindings risk revealing private locations. The owners of the bindings risk revealing private locations. The
directory structures where bindings are located are available to directory structures where bindings are located are available to
anyone who has access to the DAV:parent-set property on the resource. anyone who has access to the DAV:parent-set property on the resource.
Moving a binding may reveal its new location to anyone with access to Moving a binding may reveal its new location to anyone with access to
DAV:parent-set on its resource. DAV:parent-set on its resource.
9.5 DAV:parent-set and Denial of Service 10.5 DAV:parent-set and Denial of Service
If the server maintains the DAV:parent-set property in response to If the server maintains the DAV:parent-set property in response to
bindings created in other administrative domains, it is exposed to bindings created in other administrative domains, it is exposed to
hostile attempts to make it devote resources to adding bindings to hostile attempts to make it devote resources to adding bindings to
the list. the list.
10. Internationalization Considerations 11. Internationalization Considerations
All internationalization considerations mentioned in [RFC2518] also All internationalization considerations mentioned in [RFC2518] also
apply to this document. apply to this document.
11. IANA Considerations 12. IANA Considerations
All IANA considerations mentioned in [RFC2518] also apply to this All IANA considerations mentioned in [RFC2518] also apply to this
document. document.
12. Acknowledgements 13. 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. This draft has Chihaya, Jim Davis, Chuck Fay and Judith Slein. This draft has
benefited from thoughtful discussion by Jim Amsden, Peter Carlson, benefited from thoughtful discussion by Jim Amsden, Peter Carlson,
Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Steve Carter, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun,
Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Lisa
Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe Dusseault, Stefan Eissing, Roy Fielding, Yaron Goland, Joe
Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Hildebrand, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris
Kaler, Manoj Kasichainula, Rohit Khare, Brian Korver, Daniel 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.
13. References 14. References
13.1 Normative References 14.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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D. [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D.
Jensen, "HTTP Extensions for Distributed Authoring -- Jensen, "HTTP Extensions for Distributed Authoring --
WEBDAV", RFC 2518, February 1999. WEBDAV", RFC 2518, February 1999.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E. and [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 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Third
Edition)", W3C REC-xml-20040204, February 2004, Edition)", W3C REC-xml-20040204, February 2004,
<http://www.w3.org/TR/2004/REC-xml-20040204>. <http://www.w3.org/TR/2004/REC-xml-20040204>.
[draft-fielding-uri-rfc2396bis] 14.2 Informative References
Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax",
draft-fielding-uri-rfc2396bis-07 (work in progress),
September 2004.
13.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, March Distributed Authoring and Versioning)", RFC 3253,
2002. 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.
[draft-mealling-uuid-urn]
Leach, P., Mealling, M., and R. Salz, "A UUID URN
Namespace", draft-mealling-uuid-urn-05 (work in progress),
January 2005, <http://www.ietf.org/internet-drafts/
draft-mealling-uuid-urn-05.txt>.
Authors' Addresses Authors' Addresses
Geoffrey Clemm Geoffrey Clemm
IBM IBM
20 Maguire Road 20 Maguire Road
Lexington, MA 02421 Lexington, MA 02421
EMail: geoffrey.clemm@us.ibm.com Email: geoffrey.clemm@us.ibm.com
Jason Crawford Jason Crawford
IBM Research IBM Research
P.O. Box 704 P.O. Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
EMail: ccjason@us.ibm.com Email: ccjason@us.ibm.com
Julian F. Reschke Julian F. Reschke
greenbytes GmbH greenbytes GmbH
Salzmannstrasse 152 Salzmannstrasse 152
Muenster, NW 48159 Muenster, NW 48159
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
Appendix A. Change Log (to be removed by RFC Editor before publication) Appendix A. Change Log (to be removed by RFC Editor before publication)
A.1 Since draft-ietf-webdav-bind-02 A.1 Since draft-ietf-webdav-bind-02
Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and
"2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed "2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed
resolution, but keep it open. Add issues "ED_references" and resolution, but keep it open. Add issues "ED_references" and
"4_507_status". Started work on index. Rename document to "Binding "4_507_status". Started work on index. Rename document to "Binding
Extensions to Web Distributed Authoring and Versioning (WebDAV)". Extensions to Web Distributed Authoring and Versioning (WebDAV)".
skipping to change at page 37, line 27 skipping to change at page 37, line 40
A.6 Since draft-ietf-webdav-bind-07 A.6 Since draft-ietf-webdav-bind-07
Add more index items (no change tracking). Add and resolve issues Add more index items (no change tracking). Add and resolve issues
"2.3_copy_to_same", "bind_properties", "bind_vs_ACL", "2.3_copy_to_same", "bind_properties", "bind_vs_ACL",
"6_rebind_intro" and "rfc2396bis" (actually an action item). Fix XML "6_rebind_intro" and "rfc2396bis" (actually an action item). Fix XML
DTD fragment in section 3.3. Make spelling of "Request-URI" DTD fragment in section 3.3. Make spelling of "Request-URI"
consistent. consistent.
A.7 Since draft-ietf-webdav-bind-08 A.7 Since draft-ietf-webdav-bind-08
Resolved editorial issues raised by Jim Whitehead in Resolved editorial issues raised by Jim Whitehead in <http://
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0129.ht lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0129.html>.
ml>. Add and resolve issues "atomicity", "2_allow_destroy", Add and resolve issues "atomicity", "2_allow_destroy",
"2.1_separate_loop_discussion", "2.1.1_bind_loops_vs_locks", "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.3_copy_depth_infinity", "2.3_copy_example", "2.3_copy_vs_loops",
"2.6_resource-id_vs_versions", "3.2_example" and "2.6_resource-id_vs_versions", "3.2_example" and
"6_rebind_premissions". Add issue "2.6_when_do_ids_change". Re-open "6_rebind_premissions". Add issue "2.6_when_do_ids_change". Re-open
and resolve "6_rebind_intro". and resolve "6_rebind_intro".
A.8 Since draft-ietf-webdav-bind-09 A.8 Since draft-ietf-webdav-bind-09
Add and resolve issue "6.1_rebind_vs_locks", adding proposed example Add and resolve issue "6.1_rebind_vs_locks", adding proposed example
text. Add action item "3.1_uuids". Close issue text. Add action item "3.1_uuids". Close issue
"2.6_when_do_ids_change". Add and resolve issues "2.6_when_do_ids_change". Add and resolve issues
"2.6_bindings_vs_properties" and "uri_draft_ref". "2.6_bindings_vs_properties" and "uri_draft_ref".
Appendix B. Resolved issues (to be removed by RFC Editor before A.9 Since draft-ietf-webdav-bind-10
publication)
Issues that were either rejected or resolved in this version of this
document.
B.1 uri_draft_ref
Type: edit
julian.reschke@greenbytes.de (2005-01-01): Fix reference to
draft-fielding-uri-rfc2396bis-07
B.2 2.6_bindings_vs_properties
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0248.ht
ml>
ejw@cs.ucsc.edu (2004-12-06): I think it would be good to include the
following language in the bind specification: Note that, consistent
with [RFC2518], the value of a dead property is independent of the
number of bindings to its host resource, and of the path submitted to
PROPFIND. Since live properties can be aribtrary computational
processes, they MAY vary depending on path or number of bindings, but
SHOULD NOT do this unless the definition of the live property
explicitly includes this dependency. Here I avoided adding new
requirements in areas already covered by 2518, but did add
requirements for the new situation raised by the BIND specification.
Resolution (2004-12-14): Add that statement (see
http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0299.htm
l and subsequent messages).
B.3 2.6_when_do_ids_change
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0129.ht
ml>
ejw@cs.ucsc.edu (2004-11-29): Change "must not" to "MUST NOT" (and
eliminate the "For example" at the start of the sentence -- perhaps
change to "Specifically,"
julian.reschke@greenbytes.de (2004-11-30): Fix language, replace MOVE
by REBIND (because MOVE may be implemented as COPY/DELETE). Unclear
whether we need more changes.
Resolution (2004-12-13): Closed (see
http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0300.htm
l).
B.4 6.1_rebind_vs_locks
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2004OctDec/0281.ht
ml>
ejw@cs.ucsc.edu (2004-12-09): (Request to add a REBIND example that
requires submitting a lock token)
Resolution (2004-12-21): Example added. 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).
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) publication)
C.1 edit B.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.
C.2 3.1_uuids
Type: edit
julian.reschke@greenbytes.de (2004-12-11): Action item: if
draft-mealling-uuid-urn gets accepted in time, consider referencing
it and using urn:uuid URIs instead of opaquelocktoken URIs. See IETF
I-D Tracker.
Index Index
2 2
208 Already Reported (status code) 29 208 Already Reported (status code) 29
5 5
506 Loop Detected (status code) 32 506 Loop Detected (status code) 32
B B
BIND method 19 BIND method 19
Binding 7 Binding 7
C C
Collection 7 Collection 7
Condition Names Condition Names
DAV:bind-into-collection (pre) 20 DAV:bind-into-collection (pre) 21
DAV:bind-source-exists (pre) 20 DAV:bind-source-exists (pre) 21
DAV:binding-allowed (pre) 20 DAV:binding-allowed (pre) 21
DAV:binding-deleted (post) 23, 26 DAV:binding-deleted (post) 23, 26
DAV:can-overwrite (pre) 21, 25 DAV:can-overwrite (pre) 21, 25
DAV:cross-server-binding (pre) 21, 25 DAV:cross-server-binding (pre) 21, 25
DAV:cycle-allowed (pre) 21, 25 DAV:cycle-allowed (pre) 21, 25
DAV:lock-deleted (post) 23, 26 DAV:lock-deleted (post) 23, 26
DAV:locked-overwrite-allowed (pre) 21 DAV:locked-overwrite-allowed (pre) 21
DAV:locked-source-collection-update-allowed (pre) 25 DAV:locked-source-collection-update-allowed (pre) 25
DAV:locked-update-allowed (pre) 21, 23, 25 DAV:locked-update-allowed (pre) 21, 23, 25
DAV:name-allowed (pre) 21, 25 DAV:name-allowed (pre) 21, 25
DAV:new-binding (post) 21, 26 DAV:new-binding (post) 21, 26
skipping to change at page 40, line 44 skipping to change at page 39, line 44
DAV:protected-url-deletion-allowed (pre) 23 DAV:protected-url-deletion-allowed (pre) 23
DAV:protected-url-modification-allowed (pre) 25 DAV:protected-url-modification-allowed (pre) 25
DAV:rebind-from-collection (pre) 25 DAV:rebind-from-collection (pre) 25
DAV:rebind-source-exists (pre) 25 DAV:rebind-source-exists (pre) 25
DAV:unbind-from-collection (pre) 23 DAV:unbind-from-collection (pre) 23
DAV:unbind-source-exists (pre) 23 DAV:unbind-source-exists (pre) 23
D D
DAV header DAV header
compliance class 'bind' 32 compliance class 'bind' 32
DAV:bind-into-collection precondition 20 DAV:bind-into-collection precondition 21
DAV:bind-source-exists precondition 20 DAV:bind-source-exists precondition 21
DAV:binding-allowed precondition 20 DAV:binding-allowed precondition 21
DAV:binding-deleted postcondition 23, 26 DAV:binding-deleted postcondition 23, 26
DAV:can-overwrite precondition 21, 25 DAV:can-overwrite precondition 21, 25
DAV:cross-server-binding precondition 21, 25 DAV:cross-server-binding precondition 21, 25
DAV:cycle-allowed precondition 21, 25 DAV:cycle-allowed precondition 21, 25
DAV:lock-deleted postcondition 23, 26 DAV:lock-deleted postcondition 23, 26
DAV:locked-overwrite-allowed precondition 21 DAV:locked-overwrite-allowed precondition 21
DAV:locked-source-collection-update-allowed precondition 25 DAV:locked-source-collection-update-allowed precondition 25
DAV:locked-update-allowed precondition 21, 23, 25 DAV:locked-update-allowed precondition 21, 23, 25
DAV:name-allowed precondition 21, 25 DAV:name-allowed precondition 21, 25
DAV:new-binding postcondition 21, 26 DAV:new-binding postcondition 21, 26
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/