draft-ietf-webdav-bind-02.txt   draft-ietf-webdav-bind-03.txt 
INTERNET-DRAFT G. Clemm Network Working Group G. Clemm
draft-ietf-webdav-bind-02 IBM Internet-Draft IBM
J. Crawford Expires: June 10, 2004 J. Crawford
IBM Research IBM Research
J. Reschke J. Reschke
Greenbytes greenbytes
J. Slein J. Slein
Xerox Xerox
E.J. Whitehead J. Whitehead
U.C. Santa Cruz U.C. Santa Cruz
December 11, 2003
Expires December 27, 2003 June 27, 2003 Binding Extensions to Web Distributed Authoring and Versioning
(WebDAV)
Binding Extensions to WebDAV draft-ietf-webdav-bind-03
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all
provisions of RFC 2026, Section 10.
Internet-Drafts are working documents of the Internet Engineering Task This document is an Internet-Draft and is in full conformance with
Force (IETF), its areas, and its working groups. Note that other groups all provisions of Section 10 of RFC2026.
may also distribute working documents as Internet-Drafts.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-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 material time. It is inappropriate to use Internet-Drafts as reference
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://
http://www.ietf.org/ietf/1id-abstracts.txt 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 June 10, 2004.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
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 they Servers are required to insure the integrity of any bindings that
allow to be created. they allow to be created.
Clemm, et al. [Page 1]
Table of Contents Table of Contents
1 INTRODUCTION............................................3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Terminology...........................................4 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Rationale for Distinguishing Bindings from URI 1.2 Rationale for Distinguishing Bindings from URI Mappings . . . 6
Mappings..............................................6 1.3 Method Preconditions and Postconditions . . . . . . . . . . . 7
1.3 Method Preconditions and Postconditions...............6 2. Overview of Bindings . . . . . . . . . . . . . . . . . . . . . 7
2.1 Bindings to Collections . . . . . . . . . . . . . . . . . . . 8
2 OVERVIEW OF BINDINGS....................................7 2.2 URI Mappings Created by a new Binding . . . . . . . . . . . . 9
2.1 Bindings to Collections...............................7 2.3 COPY and Bindings . . . . . . . . . . . . . . . . . . . . . . 10
2.2 URI Mappings Created by a new Binding.................8 2.4 DELETE and Bindings . . . . . . . . . . . . . . . . . . . . . 11
2.3 COPY and Bindings.....................................9 2.5 MOVE and Bindings . . . . . . . . . . . . . . . . . . . . . . 12
2.4 DELETE and Bindings..................................10 2.6 Determining Whether Two Bindings Are to the Same Resource . . 13
2.5 MOVE and Bindings....................................10 2.7 Discovering the Bindings to a Resource . . . . . . . . . . . . 14
2.6 Determining Whether Two Bindings Are to the Same 3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Resource.............................................11 3.1 DAV:resource-id Property . . . . . . . . . . . . . . . . . . . 14
2.7 Discovering the Bindings to a Resource...............12 3.2 DAV:parent-set Property . . . . . . . . . . . . . . . . . . . 14
4. BIND Method . . . . . . . . . . . . . . . . . . . . . . . . . 15
3 PROPERTIES.............................................12 4.1 Example: BIND . . . . . . . . . . . . . . . . . . . . . . . . 17
3.1 DAV:resource-id Property.............................12 5. UNBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 DAV:parent-set Property..............................13 5.1 Example: UNBIND . . . . . . . . . . . . . . . . . . . . . . . 19
6. REBIND Method . . . . . . . . . . . . . . . . . . . . . . . . 19
4 BIND METHOD............................................13 6.1 Example: REBIND . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Example: BIND........................................15 7. Additional Status Codes . . . . . . . . . . . . . . . . . . . 21
7.1 208 Already Reported . . . . . . . . . . . . . . . . . . . . . 21
5 UNBIND METHOD..........................................15 7.2 506 Loop Detected . . . . . . . . . . . . . . . . . . . . . . 23
5.1 Example: UNBIND......................................16 8. Security Considerations . . . . . . . . . . . . . . . . . . . 24
8.1 Privacy Concerns . . . . . . . . . . . . . . . . . . . . . . . 24
6 REBIND METHOD..........................................17 8.2 Redirect Loops . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1 Example: REBIND......................................18 8.3 Bindings, and Denial of Service . . . . . . . . . . . . . . . 24
8.4 Private Locations May Be Revealed . . . . . . . . . . . . . . 24
7 ADDITIONAL STATUS CODES................................19 8.5 DAV:parent-set and Denial of Service . . . . . . . . . . . . . 25
7.1 506 Loop Detected....................................19 9. Internationalization Considerations . . . . . . . . . . . . . 25
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
8 SECURITY CONSIDERATIONS................................20 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25
8.1 Privacy Concerns.....................................20 Normative References . . . . . . . . . . . . . . . . . . . . . 25
8.2 Redirect Loops.......................................21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 26
8.3 Bindings, and Denial of Service......................21 A. Change Log (to be removed by RFC Editor before publication) . 27
8.4 Private Locations May Be Revealed....................21 A.1 Since draft-ietf-webdav-bind-02 . . . . . . . . . . . . . . . 27
8.5 DAV:parent-set and Denial of Service.................21 B. Resolved issues (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . . 27
9 INTERNATIONALIZATION CONSIDERATIONS....................21 B.1 ED_references . . . . . . . . . . . . . . . . . . . . . . . . 27
B.2 2.3_COPY_SHARED_BINDINGS . . . . . . . . . . . . . . . . . . . 27
10 IANA CONSIDERATIONS..................................21 B.3 2.3_MULTIPLE_COPY . . . . . . . . . . . . . . . . . . . . . . 28
B.4 4_507_status . . . . . . . . . . . . . . . . . . . . . . . . . 28
11 INTELLECTUAL PROPERTY................................22 C. Open issues (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . . . . . . 28
12 ACKNOWLEDGEMENTS.....................................22 C.1 5.1_LOOP_STATUS . . . . . . . . . . . . . . . . . . . . . . . 28
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
13 REFERENCES...........................................22 Intellectual Property and Copyright Statements . . . . . . . . 31
14 AUTHORS' ADDRESSES...................................23
Clemm, et al. [Page 2] 1. Introduction
1 INTRODUCTION
This specification extends the WebDAV Distributed Authoring This specification extends the WebDAV Distributed Authoring Protocol
Protocol to enable clients to create new access paths to existing to enable clients to create new access paths to existing resources.
resources. This capability is useful for several reasons: This capability is useful for several reasons:
URIs of WebDAV-compliant resources are hierarchical and correspond URIs of WebDAV-compliant resources are hierarchical and correspond to
to a hierarchy of collections in resource space. The WebDAV a hierarchy of collections in resource space. The WebDAV Distributed
Distributed Authoring Protocol makes it possible to organize these Authoring Protocol makes it possible to organize these resources into
resources into hierarchies, placing them into groupings, known as hierarchies, placing them into groupings, known as collections, which
collections, which are more easily browsed and manipulated than a are more easily browsed and manipulated than a single flat
single flat collection. However, hierarchies require collection. However, hierarchies require categorization decisions
categorization decisions that locate resources at a single location that locate resources at a single location in the hierarchy, a
in the hierarchy, a drawback when a resource has multiple valid drawback when a resource has multiple valid categories. For example,
categories. For example, in a hierarchy of vehicle descriptions in a hierarchy of vehicle descriptions containing collections for
containing collections for cars and boats, a description of a cars and boats, a description of a combination car/boat vehicle could
combination car/boat vehicle could belong in either collection. belong in either collection. Ideally, the description should be
Ideally, the description should be accessible from both. Allowing accessible from both. Allowing clients to create new URIs that access
clients to create new URIs that access the existing resource lets the existing resource lets them put that resource into multiple
them put that resource into multiple collections. collections.
Hierarchies also make resource sharing more difficult, since Hierarchies also make resource sharing more difficult, since
resources that have utility across many collections are still resources that have utility across many collections are still forced
forced into a single collection. For example, the mathematics into a single collection. For example, the mathematics department at
department at one university might create a collection of one university might create a collection of information on fractals
information on fractals that contains bindings to some local that contains bindings to some local resources, but also provides
resources, but also provides access to some resources at other access to some resources at other universities. For many reasons, it
universities. For many reasons, it may be undesirable to make may be undesirable to make physical copies of the shared resources on
physical copies of the shared resources on the local server: to the local server: to conserve disk space, to respect copyright
conserve disk space, to respect copyright constraints, or to make constraints, or to make any changes in the shared resources visible
any changes in the shared resources visible automatically. Being automatically. Being able to create new access paths to existing
able to create new access paths to existing resources in other resources in other collections or even on other servers is useful for
collections or even on other servers is useful for this sort of this sort of case.
case.
The BIND method defined here provides a mechanism for allowing The BIND method defined here provides a mechanism for allowing
clients to create alternative access paths to existing WebDAV clients to create alternative access paths to existing WebDAV
resources. HTTP and WebDAV methods are able to work because there resources. HTTP [RFC2616] and WebDAV [RFC2518] methods are able to
are mappings between URIs and resources. A method is addressed to work because there are mappings between URIs and resources. A method
a URI, and the server follows the mapping from that URI to a is addressed to a URI, and the server follows the mapping from that
resource, applying the method to that resource. Multiple URIs may URI to a resource, applying the method to that resource. Multiple
be mapped to the same resource, but until now there has been no way URIs may be mapped to the same resource, but until now there has been
for clients to create additional URIs mapped to existing resources. no way for clients to create additional URIs mapped to existing
resources.
BIND lets clients associate a new URI with an existing WebDAV BIND lets clients associate a new URI with an existing WebDAV
resource, and this URI can then be used to submit requests to the resource, and this URI can then be used to submit requests to the
resource. Since URIs of WebDAV resources are hierarchical, and resource. Since URIs of WebDAV resources are hierarchical, and
correspond to a hierarchy of collections in resource space, the correspond to a hierarchy of collections in resource space, the BIND
BIND method also has the effect of adding the resource to a method also has the effect of adding the resource to a collection.
collection. As new URIs are associated with the resource, it As new URIs are associated with the resource, it appears in
appears in additional collections. additional collections.
Clemm, et al. [Page 3]
A BIND request does not create a new resource, but simply makes A BIND request does not create a new resource, but simply makes
available a new URI for submitting requests to an existing available a new URI for submitting requests to an existing resource.
resource. The new URI is indistinguishable from any other URI when The new URI is indistinguishable from any other URI when submitting a
submitting a request to a resource. Only one round trip is needed request to a resource. Only one round trip is needed to submit a
to submit a request to the intended target. Servers are required request to the intended target. Servers are required to enforce the
to enforce the integrity of the relationships between the new URIs integrity of the relationships between the new URIs and the resources
and the resources associated with them. Consequently, it may be associated with them. Consequently, it may be very costly for
very costly for servers to support BIND requests that cross server servers to support BIND requests that cross server boundaries.
boundaries.
This specification is organized as follows. Section 1.1 defines This specification is organized as follows. Section 1.1 defines
terminology used in the rest of the specification, while Section terminology used in the rest of the specification, while Section 2
1.3 overviews bindings. Section 3 defines the new properties overviews bindings. Section 3 defines the new properties needed to
needed to support multiple bindings to the same resource. Section support multiple bindings to the same resource. Section 4 specifies
4 specifies the BIND method, used to create multiple bindings to the BIND method, used to create multiple bindings to the same
the same resource. Section 5 specifies the UNBIND method, used to resource. Section 5 specifies the UNBIND method, used to remove a
remove a binding to a resource. Section 6 specifies the REBIND binding to a resource. Section 6 specifies the REBIND method, used
method, used to move a binding to another collection. to move a binding to another collection.
1.1 Terminology 1.1 Terminology
The terminology used here follows and extends that in the WebDAV The terminology used here follows and extends that in the WebDAV
Distributed Authoring Protocol specification [RFC2518]. Distributed Authoring Protocol specification [RFC2518].
This document uses XML DTD fragments as a purely notational 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 purely notational
convention. WebDAV request and response bodies cannot be validated convention. WebDAV request and response bodies cannot be validated
due to the specific extensibility rules defined in section 23 of due to the specific extensibility rules defined in section 23 of
[RFC2518] and due to the fact that all XML elements defined by this [RFC2518] and due to the fact that all XML elements defined by this
specification use the XML namespace name "DAV:". In particular: specification use the XML namespace name "DAV:". In particular:
- Element names use the "DAV:" namespace.
- Element ordering is irrelevant. o Element names use the "DAV:" namespace.
- Extension elements/attributes (elements/attributes not already
defined as valid child elements) may be added anywhere, except when o Element ordering is irrelevant.
explicitly stated otherwise.
o Extension elements/attributes (elements/attributes not already
defined as valid child elements) may be added anywhere, except
when explicitly stated otherwise.
URI Mapping URI Mapping
A relation between an absolute URI and a resource. For an absolute A relation between an absolute URI and a resource. For an
URI U and the resource it identifies R, the URI mapping can be absolute URI U and the resource it identifies R, the URI mapping
thought of as (U => R). Since a resource can represent items that can be thought of as (U => R). Since a resource can represent
are not network retrievable, as well as those that are, it is items that are not network retrievable, as well as those that are,
possible for a resource to have zero, one, or many URI mappings. it is possible for a resource to have zero, one, or many URI
Mapping a resource to an "http" scheme URI makes it possible to mappings. Mapping a resource to an "http" scheme URI makes it
submit HTTP protocol requests to the resource using the URI. possible to submit HTTP protocol requests to the resource using
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 [RFC2396]. Formally, as defined in section 3.3 of [RFC2396].
Clemm, et al. [Page 4]
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. So segment and the same resource, these are two distinct bindings.
for a collection C, a path segment S, and a resource R, the binding So for a collection C, a path segment S, and a resource R, the
can be thought of as C:(S -> R). Bindings create URI mappings, and binding can be thought of as C:(S -> R). Bindings create URI
hence allow requests to be sent to a single resource from multiple mappings, and hence allow requests to be sent to a single resource
locations in a URI namespace. For example, given a collection C from multiple locations in a URI namespace. For example, given a
(accessible through the URI http://www.example.com/CollX), a path collection C (accessible through the URI http://www.example.com/
segment S (equal to "foo.html"), and a resource R, then creating CollX), a path segment S (equal to "foo.html"), and a resource R,
the binding C: (S -> R) makes it possible to use the URI then creating the binding C: (S -> R) makes it possible to use the
http://www.example.com/CollX/foo.html to access R. URI http://www.example.com/CollX/foo.html to access R.
Collection Collection
A resource that contains, as part of its state, a set of bindings A resource that contains, as part of its state, a set of bindings
that identify internal member resources. that identify internal member resources.
Clemm, et al. [Page 5]
Internal Member URI Internal Member URI
The URI that identifies an internal member of a collection, and The URI that identifies an internal member of a collection, and
that consists of the URI for the collection, followed by a slash that consists of the URI for the collection, followed by a slash
character ('/'), followed by the path segment of the binding for character ('/'), followed by the path segment of the binding for
that internal member. that internal member.
1.2 Rationale for Distinguishing Bindings from URI Mappings 1.2 Rationale for Distinguishing Bindings from URI Mappings
In [RFC2518], the state of a collection is defined as containing a In [RFC2518], the state of a collection is defined as containing a
list of internal member URIs. If there are multiple mappings to a list of internal member URIs. If there are multiple mappings to a
collection, then the state of the collection is different when you collection, then the state of the collection is different when you
refer to it via a different URI. This is undesirable, since ideally refer to it via a different URI. This is undesirable, since ideally a
a collection's membership should remain the same, independent of collection's membership should remain the same, independent of which
which URI was used to reference it. URI was used to reference it.
The notion of binding is introduced to separate the final segment The notion of binding is introduced to separate the final segment of
of a URI from its parent collection’s contribution. This done, a a URI from its parent collection's contribution. This done, a
collection can be defined as containing a set of bindings, thus collection can be defined as containing a set of bindings, thus
permitting new mappings to a collection without modifying its permitting new mappings to a collection without modifying its
membership. The authors of this specification anticipate and membership. The authors of this specification anticipate and
recommend that future revisions of [RFC2518] will update the recommend that future revisions of [RFC2518] will update the
definition of the state of a collection to correspond to the definition of the state of a collection to correspond to the
definition in this document. definition in this document.
1.3 Method Preconditions and Postconditions 1.3 Method Preconditions and Postconditions
A "precondition" of a method describes the state on the server that A "precondition" of a method describes the state on the server that
must be true for that method to be performed. A "postcondition" of must be true for that method to be performed. A "postcondition" of a
a method describes the state on the server that must be true after method describes the state on the server that must be true after that
that method has completed. If a method precondition or method has completed. If a method precondition or postcondition for
postcondition for a request is not satisfied, the response status a request is not satisfied, the response status of the request MUST
of the request MUST be either 403 (Forbidden) if the request should be either 403 (Forbidden) if the request should not be repeated
not be repeated because it will always fail, or 409 (Conflict) if because it will always fail, or 409 (Conflict) if it is expected that
it is expected that the user might be able to resolve the conflict the user might be able to resolve the conflict and resubmit the
and resubmit the request. request.
In order to allow better client handling of 403 and 409 responses, In order to allow better client handling of 403 and 409 responses, a
a distinct XML element type is associated with each method distinct XML element type is associated with each method precondition
precondition and postcondition of a request. When a particular and postcondition of a request. When a particular precondition is
precondition is not satisfied or a particular postcondition cannot not satisfied or a particular postcondition cannot be achieved, the
be achieved, the appropriate XML element MUST be returned as the appropriate XML element MUST be returned as the child of a top-level
child of a top-level DAV:error element in the response body, unless DAV:error element in the response body, unless otherwise negotiated
otherwise negotiated by the request. In a 207 Multi-Status by the request. In a 207 Multi-Status response, the DAV:error
response, the DAV:error element would appear in the appropriate element would appear in the appropriate DAV:responsedescription
DAV:responsedescription element. element.
Clemm, et al. [Page 6] 2. Overview of Bindings
2 OVERVIEW OF BINDINGS
Bindings are part of the state of a collection. They define the Bindings are part of the state of a collection. They define the
internal members of the collection, and the names of those internal internal members of the collection, and the names of those internal
members. members.
Bindings are added and removed by a variety of existing HTTP Bindings are added and removed by a variety of existing HTTP methods.
methods. A method that creates a new resource, such as PUT, COPY, A method that creates a new resource, such as PUT, COPY, and MKCOL,
and MKCOL, adds a binding. A method that deletes a resource, such adds a binding. A method that deletes a resource, such as DELETE,
as DELETE, removes a binding. A method that moves a resource (e.g. removes a binding. A method that moves a resource (e.g. MOVE) both
MOVE) both adds a binding (in the destination collection) and adds a binding (in the destination collection) and removes a binding
removes a binding (in the source collection). The BIND method (in the source collection). The BIND method introduced here provides
introduced here provides a mechanism for adding a second binding to a mechanism for adding a second binding to an existing resource.
an existing resource. There is no difference between an initial There is no difference between an initial binding added by PUT, COPY,
binding added by PUT, COPY, or MKCOL, and additional bindings added or MKCOL, and additional bindings added with BIND.
with BIND.
It would be very undesirable if one binding could be destroyed as a It would be very undesirable if one binding could be destroyed as a
side effect of operating on the resource through a different side effect of operating on the resource through a different binding.
binding. In particular, the removal of one binding to a resource In particular, the removal of one binding to a resource (e.g. with a
(e.g. with a DELETE or a MOVE) MUST NOT disrupt another binding to DELETE or a MOVE) MUST NOT disrupt another binding to that resource,
that resource, e.g. by turning that binding into a dangling path e.g. by turning that binding into a dangling path segment. The
segment. The server MUST NOT reclaim system resources after server MUST NOT reclaim system resources after removing one binding,
removing one binding, while other bindings to the resource remain. while other bindings to the resource remain. In other words, the
In other words, the server MUST maintain the integrity of a server MUST maintain the integrity of a binding.
binding.
2.1 Bindings to Collections 2.1 Bindings to Collections
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 possible to complete an operation in spite of the presence of a loop.
loop. However, the 506 (Loop Detected) status code is defined in However, the 506 (Loop Detected) status code is defined in Section 7
Section 5 for use in contexts where an operation is terminated for use in contexts where an operation is terminated because a loop
because a loop was encountered. was encountered.
Creating a new binding to a collection makes each resource Creating a new binding to a collection makes each resource associated
associated with a binding in that collection accessible via a new with a binding in that collection accessible via a new URI, and thus
URI, and thus creates new URI mappings to those resources but no creates new URI mappings to those resources but no new bindings.
new bindings.
For example, suppose a new binding CollY is created for collection For example, suppose a new binding CollY is created for collection C1
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.
Clemm, et al. [Page 7]
+-------------------------+ +-------------------------+
| Root Collection | | Root Collection |
| bindings: | | bindings: |
| CollX CollY | | CollX CollY |
+-------------------------+ +-------------------------+
| / | /
| / | /
| / | /
+------------------+ +------------------+
| Collection C1 | | Collection C1 |
skipping to change at line 345 skipping to change at page 9, line 27
+------------------+ +------------------+
| \ | \
| \ | \
| \ | \
+-------------+ +-------------+ +-------------+ +-------------+
| Resource R1 | | Resource R2 | | Resource R1 | | Resource R2 |
+-------------+ +-------------+ +-------------+ +-------------+
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 to be added to Suppose a binding from "Binding-Name" to resource R to be added to a
a collection, C. Then if C-MAP is the set of URIs that were mapped 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, C before the BIND request, then for each URI "C-URI" in C-MAP, the
the URI "C-URI/Binding-Name" is mapped to resource R following the URI "C-URI/Binding-Name" is mapped to resource R following the BIND
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:
http://www.example.com/A/1/foo.html http://www.example.com/A/1/foo.html
http://example.com/A/one/foo.html http://example.com/A/one/foo.html
Note that if R is a collection, additional URI mappings are created Note that if R is a collection, additional URI mappings are created
to the descendents of R. Also, note that if a binding is made in to the descendents of R. Also, note that if a binding is made in
collection C to C itself (or to a parent of C), an infinite number collection C to C itself (or to a parent of C), an infinite number of
of mappings are introduced. mappings are introduced.
For example, if a binding from "myself" to C is then added to C, For example, if a binding from "myself" to C is then added to C, the
the following infinite number of additional mappings to C are following infinite number of additional mappings to C are introduced:
introduced:
http://www.example.com/A/1/myself http://www.example.com/A/1/myself
http://www.example.com/A/1/myself/myself http://www.example.com/A/1/myself/myself
... ...
Clemm, et al. [Page 8]
and the following infinite number of additional mappings to R are and the following infinite number of additional mappings to R are
introduced: introduced:
http://www.example.com/A/1/myself/foo.html http://www.example.com/A/1/myself/foo.html
http://www.example.com/A/1/myself/myself/foo.html http://www.example.com/A/1/myself/myself/foo.html
... ...
2.3 COPY and Bindings 2.3 COPY and Bindings
As defined in Section 8.8 of [RFC2518], COPY causes the resource As defined in Section 8.8 of [RFC2518], COPY causes the resource
identified by the Request-URI to be duplicated, and makes the new identified by the Request-URI to be duplicated, and makes the new
resource accessible using the URI specified in the Destination resource accessible using the URI specified in the Destination
header. Upon successful completion of a COPY, a new binding is header. Upon successful completion of a COPY, a new binding is
created between the last path segment of the Destination header, created between the last path segment of the Destination header, and
and the destination resource. The new binding is added to its the destination resource. The new binding is added to its parent
parent collection, identified by the Destination header minus its collection, identified by the Destination header minus its final
final segment. segment.
The following figure shows an example: Suppose that a COPY is The following figure shows an example: Suppose that a COPY is issued
issued to URI-3 for resource R (which is also mapped to URI-1 and to URI-3 for resource R (which is also mapped to URI-1 and URI-2),
URI-2), with the Destination header set to URI-X. After successful with the Destination header set to URI-X. After successful
completion of the COPY operation, resource R is duplicated to completion of the COPY operation, resource R is duplicated to create
create resource R', and a new binding has been created which resource R', and a new binding has been created which creates at
creates at least the URI mapping between URI-X and the new resource least the URI mapping between URI-X and the new resource (although
(although other URI mappings may also have been created). other URI mappings may also have been created).
URI-1 URI-2 URI-3 URI-X URI-1 URI-2 URI-3 URI-X
| | | | | | | |
| | | <---- URI Mappings ----> | | | | <---- URI Mappings ----> |
| | | | | | | |
+---------------------+ +------------------------+ +---------------------+ +------------------------+
| Resource R | | Resource R' | | Resource R | | Resource R' |
+---------------------+ +------------------------+ +---------------------+ +------------------------+
It might be thought that a COPY request with "Depth: 0" on a It might be thought that a COPY request with "Depth: 0" on a
collection would duplicate its bindings, since bindings are part of collection would duplicate its bindings, since bindings are part of
the collection's state. This is not the case, however. The the collection's state. This is not the case, however. The
definition of Depth in [RFC2518] makes it clear that a "Depth: 0" definition of Depth in [RFC2518] makes it clear that a "Depth: 0"
request does not apply to a collection's members. Consequently, a request does not apply to a collection's members. Consequently, a
COPY with "Depth: 0" does not duplicate the bindings contained by COPY with "Depth: 0" does not duplicate the bindings contained by the
the collection. collection.
If a COPY causes one or more existing resources to be updated, the If a COPY request causes an existing resource to be updated, the
bindings to those resources MUST be unaffected by the COPY. Using bindings to that resource MUST be unaffected by the COPY request.
the preceding example, suppose that a COPY is issued to URI-X for Using the preceding example, suppose that a COPY request is issued to
resource R', with the Destination header set to URI-2. The content URI-X for resource R', with the Destination header set to URI-2. The
and dead properties of resource R would be updated to be a copy of content and dead properties of resource R would be updated to be a
those of resource R', but the mappings from URI-1, URI-2, and URI-3 copy of those of resource R', but the mappings from URI-1, URI-2, and
to resource R remain unaffected. URI-3 to resource R remain unaffected. If because of multiple
bindings to a resource, more than one source resource updates a
single destination resource, the order of the updates is server
defined.
If a COPY request would cause a new resource to be created as a copy
of an existing resource, and that COPY request has already created a
copy of that existing resource, the COPY request instead creates
another binding to the previous copy, instead of creating a new
resource.
Clemm, et al. [Page 9]
2.4 DELETE and Bindings 2.4 DELETE and Bindings
When there are multiple bindings to a resource, a DELETE applied to When there are multiple bindings to a resource, a DELETE applied to
that resource MUST NOT remove any bindings to that resource other that resource MUST NOT remove any bindings to that resource other
than the one identified by the request URI. For example, suppose than the one identified by the request URI. For example, suppose the
the collection identified by the URI "/a" has a binding named "x" collection identified by the URI "/a" has a binding named "x" to a
to a resource R, and another collection identified by "/b" has a resource R, and another collection identified by "/b" has a binding
binding named "y" to the same resource R. Then a DELETE applied to named "y" to the same resource R. Then a DELETE applied to "/a/x"
"/a/x" removes the binding named "x" from "/a" but MUST NOT remove removes the binding named "x" from "/a" but MUST NOT remove the
the binding named "y" from "/b" (i.e. after the DELETE, "/y/b" binding named "y" from "/b" (i.e. after the DELETE, "/y/b" continues
continues to identify the resource R). In particular, although to identify the resource R). In particular, although Section 8.6.1
Section 8.6.1 of [RFC2518] states that during DELETE processing, a of [RFC2518] states that during DELETE processing, a server "MUST
server "MUST remove any URI for the resource identified by the remove any URI for the resource identified by the Request-URI from
Request-URI from collections which contain it as a member", a collections which contain it as a member", a server that supports the
server that supports the binding protocol MUST NOT follow this binding protocol MUST NOT follow this requirement.
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 membership of any other collection that is not itself a member of the
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 If a collection supports the UNBIND method (see Section 5), a DELETE
DELETE of an internal member of a collection MAY be implemented as of an internal member of a collection MAY be implemented as an UNBIND
an UNBIND request. In this case, applying DELETE to a Request-URI request. In this case, applying DELETE to a Request-URI has the
has the effect of removing the binding identified by the final effect of removing the binding identified by the final segment of the
segment of the Request-URI from the collection identified by the Request-URI from the collection identified by the Request-URI minus
Request-URI minus its final segment. Although [RFC2518] allows a its final segment. Although [RFC2518] allows a DELETE to be a
DELETE to be a non-atomic operation, when the DELETE operation is non-atomic operation, when the DELETE operation is implemented as an
implemented as an UNBIND, the operation is atomic. In particular, UNBIND, the operation is atomic. In particular, a DELETE on a
a DELETE on a hierarchy of resources is simply the removal of a hierarchy of resources is simply the removal of a binding to the
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
existing resource, the constraints specified for DELETE apply. existing resource, the constraints specified for DELETE apply.
If the destination collection of a MOVE request supports the REBIND If the destination collection of a MOVE request supports the REBIND
method (see Section 6), a MOVE of a resource into that collection method (see Section 6), a MOVE of a resource into that collection MAY
MAY be implemented as a REBIND request. Although [RFC2518] allows be implemented as a REBIND request. Although [RFC2518] allows a MOVE
a MOVE to be a non-atomic operation, when the MOVE operation is to be a non-atomic operation, when the MOVE operation is implemented
implemented as a REBIND, the operation is atomic. In particular, as a REBIND, the operation is atomic. In particular, applying a MOVE
applying a MOVE to a Request-URI and a Destination URI has the to a Request-URI and a Destination URI has the effect of removing a
effect of removing a binding to a resource (at the Request-URI), binding to a resource (at the Request-URI), and creating a new
and creating a new binding to that resource (at the Destination binding to that resource (at the Destination URI).
URI).
Clemm, et al. [Page 10] As an example, suppose that a MOVE is issued to URI-3 for resource R
As an example, suppose that a MOVE is issued to URI-3 for resource below (which is also mapped to URI-1 and URI-2), with the Destination
R below (which is also mapped to URI-1 and URI-2), with the header set to URI-X. After successful completion of the MOVE
Destination header set to URI-X. After successful completion of operation, a new binding has been created which creates the URI
the MOVE operation, a new binding has been created which creates mapping between URI-X and resource R. The binding corresponding to
the URI mapping between URI-X and resource R. The binding the final segment of URI-3 has been removed, which also causes the
corresponding to the final segment of URI-3 has been removed, which URI mapping between URI-3 and R to be removed. If resource R were a
also causes the URI mapping between URI-3 and R to be removed. If collection, old URI-3 based mappings to members of R would have been
resource R were a collection, old URI-3 based mappings to members removed, and new URI-X based mappings to members of R would have been
of R would have been removed, and new URI-X based mappings to created.
members of R would have been created.
>> Before Request: >> Before Request:
URI-1 URI-2 URI-3 URI-1 URI-2 URI-3
| | | | | |
| | | <---- URI Mappings | | | <---- URI Mappings
| | | | | |
+---------------------+ +---------------------+
| Resource R | | Resource R |
+---------------------+ +---------------------+
skipping to change at line 514 skipping to change at page 13, line 15
URI-1 URI-2 URI-X URI-1 URI-2 URI-X
| | | | | |
| | | <---- URI Mappings | | | <---- URI Mappings
| | | | | |
+---------------------+ +---------------------+
| Resource R | | Resource R |
+---------------------+ +---------------------+
Although [RFC2518] allows a MOVE on a collection to be a non-atomic Although [RFC2518] allows a MOVE on a collection to be a non-atomic
operation, a MOVE implemented as a REBIND MUST be atomic. Even operation, a MOVE implemented as a REBIND MUST be atomic. Even when
when the Request-URI identifies a collection, the MOVE operation the Request-URI identifies a collection, the MOVE operation involves
involves only removing one binding to that collection and adding only removing one binding to that collection and adding another.
another. There are no operations on bindings to any of its There are no operations on bindings to any of its children, so the
children, so the case of MOVE on a collection is the same as the case of MOVE on a collection is the same as the case of MOVE on a
case of MOVE on a non-collection resource. Both are atomic. non-collection resource. Both are atomic.
2.6 Determining Whether Two Bindings Are to the Same Resource 2.6 Determining Whether Two Bindings Are to the Same Resource
It is useful to have some way of determining whether two bindings It is useful to have some way of determining whether two bindings are
are to the same resource. Two resources might have identical to the same resource. Two resources might have identical contents
contents and properties, but not be the same resource (e.g. an and properties, but not be the same resource (e.g. an update to one
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, the client can be requests through two bindings are identical, the client can be
assured that the two bindings are to the same resource. assured that the two bindings are to the same resource.
Clemm, et al. [Page 11] The DAV:resource-id property is created, and its value assigned, when
The DAV:resource-id property is created, and its value assigned, the resource is created. The value of DAV:resource-id MUST NOT be
when the resource is created. The value of DAV:resource-id MUST changed. Even after the resource is no longer accessible through any
NOT be changed. Even after the resource is no longer accessible URI, that value MUST NOT be reassigned to another resource's
through any URI, that value MUST NOT be reassigned to another DAV:resource-id property.
resource's DAV: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 or a value to its DAV:resource-id property. For example, a PUT or a COPY
COPY that creates a new resource must assign a new, unique value to that creates a new resource must assign a new, unique value to the
the DAV:resource-id property of that new resource. DAV:resource-id property of that new resource.
On the other hand, any method that affects an existing resource On the other hand, any method that affects an existing resource MUST
MUST NOT change the value of its DAV:resource-id property. For NOT change the value of its DAV:resource-id property. For example, a
example, a PUT or a COPY that updates an existing resource must not PUT or a COPY that updates an existing resource must not change the
change the value of its DAV:resource-id property. A MOVE, since it value of its DAV:resource-id property. A MOVE, since it does not
does not create a new resource, but only changes the location of an create a new resource, but only changes the location of an existing
existing resource, must not change the value of the DAV:resource-id resource, must not change the value of the DAV:resource-id property.
property.
2.7 Discovering the Bindings to a Resource 2.7 Discovering the Bindings to a Resource
An OPTIONAL DAV:parent-set property on a resource provides a list An OPTIONAL DAV:parent-set property on a resource provides a list of
of the bindings that associate a collection and a URI segment with the bindings that associate a collection and a URI segment with that
that resource. If the DAV:parent-set property exists on a given resource. If the DAV:parent-set property exists on a given resource,
resource, it MUST contain a complete list of all bindings to that it MUST contain a complete list of all bindings to that resource that
resource that the client is authorized to see. When deciding the client is authorized to see. When deciding whether to support
whether to support the DAV:parent-set property, server implementers the DAV:parent-set property, server implementers / administrators
/ administrators should balance the benefits it provides against should balance the benefits it provides against the cost of
the cost of maintaining the property and the security risks maintaining the property and the security risks enumerated in
enumerated in Sections 8.4 and 8.5. Sections 8.4 and 8.5.
3 PROPERTIES 3. Properties
The bind feature introduces the following properties for a The bind feature introduces the following properties for a resource.
resource.
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 properties defined by this document. This allows a binding server to
to perform efficiently when a naive client, which does not perform efficiently when a naive client, which does not understand
understand the cost of asking a server to compute all possible live the cost of asking a server to compute all possible live properties,
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 The value of DAV:resource-id is a URI, and may use any registered URI
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 opaquelocktoken: scheme defined in
[RFC2518]). [RFC2518]).
Clemm, et al. [Page 12]
<!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
collection, and the segment identifies the binding name of that collection, and the segment identifies the binding name of that
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. For example, if collection C1 is mapped to both /CollX collection. For example, if collection C1 is mapped to both /CollX
and /CollY, and C1 contains a binding named "x.gif" to a resource and /CollY, and C1 contains a binding named "x.gif" to a resource R1,
R1, then either [/CollX, x.gif] or [/CollY, x.gif] can appear in then either [/CollX, x.gif] or [/CollY, x.gif] can appear in the
the DAV:parent-set of R1, but not both. But if C1 also had a DAV:parent-set of R1, but not both. But if C1 also had a binding
binding named "y.gif" to R1, then there would be two entries for C1 named "y.gif" to R1, then there would be two entries for C1 in the
in the DAV:binding-set of R1 (i.e. either both [/CollX, x.gif] and DAV:binding-set of R1 (i.e. either both [/CollX, x.gif] and [/CollX,
[/CollX, y.gif] or alternatively, both [/CollY, x.gif] and [/CollY, y.gif] or alternatively, both [/CollY, x.gif] and [/CollY, y.gif]).
y.gif]).
<!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 [RFC2396] PCDATA value: segment, as defined in section 3.3 of [RFC2396]
4 BIND METHOD 4. BIND Method
The BIND method modifies the collection identified by the Request- The BIND method modifies the collection identified by the
URI, by adding a new binding from the segment specified in the BIND Request-URI, by adding a new binding from the segment specified in
body to the resource identified in the BIND body. the BIND 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 request MUST fail. Note that it is especially difficult to maintain
maintain the integrity of cross-server bindings. Unless the server the integrity of cross-server bindings. Unless the server where the
where the resource resides knows about all bindings on all servers resource resides knows about all bindings on all servers to that
to that resource, it may unwittingly destroy the resource or make resource, it may unwittingly destroy the resource or make it
it inaccessible without notifying another server that manages a inaccessible without notifying another server that manages a binding
binding to the resource. For example, if server A permits creation to the resource. For example, if server A permits creation of a
of a binding to a resource on server B, server A must notify server binding to a resource on server B, server A must notify server B
B about its binding and must have an agreement with B that B will about its binding and must have an agreement with B that B will not
not destroy the resource while A's binding exists. Otherwise destroy the resource while A's binding exists. Otherwise server B
server B may receive a DELETE request that it thinks removes the may receive a DELETE request that it thinks removes the last binding
last binding to the resource and destroy the resource while A's to the resource and destroy the resource while A's binding still
binding still exists. Status code 507 (Cross-server Binding exists. The precondition DAV:cross-server-binding is defined below
Forbidden) is defined in Section 7.1 for cases where servers fail for cases where servers fail cross-server BIND requests because they
cross-server BIND requests because they cannot guarantee the cannot guarantee the integrity of cross-server bindings.
integrity of cross-server bindings.
By default, if there already is a binding for the specified segment By default, if there already is a binding for the specified segment
in the collection, the new binding replaces the existing binding. in the collection, the new binding replaces the existing binding.
This default binding replacement behavior can be overridden using the
Clemm, et al. [Page 13] Overwrite header defined in Section 9.6 of [RFC2518].
This default binding replacement behavior can be overridden using
the Overwrite header defined in Section 9.6 of [RFC2518].
Marshalling: Marshalling:
The request MAY include an Overwrite header. The request MAY include an Overwrite header.
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 was a new binding was created and 200 (OK) when an existing binding
replaced. was replaced.
If a response body for a successful request is included, it MUST be If a response body for a successful request is included, it MUST
a DAV:bind-response XML element. Note that this document does not be a DAV:bind-response XML element. Note that this document does
define any elements for the BIND response body, but the DAV:bind- not define any elements for the BIND response body, but the
response element is defined to ensure interoperability between DAV:bind-response element is defined to ensure interoperability
future extensions that do define elements for the BIND response between future extensions that do define elements for the BIND
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.
skipping to change at line 694 skipping to change at page 16, line 45
(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".
(DAV:cycle-allowed): If the DAV:href element identifies a (DAV:cycle-allowed): If the DAV:href element identifies a
collection, and if the request-URI identifies a collection that is collection, and if the request-URI identifies a collection that is
a member of that collection, the server MUST support cycles in the a member of that collection, the server MUST support cycles in the
URI namespace. URI namespace.
Clemm, et al. [Page 14]
(DAV:locked-update-allowed): If the collection identified by the (DAV:locked-update-allowed): If the collection identified by the
Request-URI is write-locked, then the appropriate token MUST be Request-URI is write-locked, then the appropriate token MUST be
specified in an If request header. specified in an If request header.
(DAV:locked-overwrite-allowed): If the collection already contains (DAV:locked-overwrite-allowed): If the collection already contains
a binding with the specified path segment, and if that binding is a binding with the specified path segment, and if that binding is
protected by a write-lock, then the appropriate token MUST be protected by a write-lock, then the appropriate token MUST be
specified in an If request header. specified in an If request header.
Postconditions: Postconditions:
(DAV:new-binding): The collection MUST have a binding that maps the (DAV:new-binding): The collection MUST have a binding that maps
segment specified in the DAV:segment element in the request body, the segment specified in the DAV:segment element in the request
to the resource identified by the DAV:href element in the request body, to the resource identified by the DAV:href element in the
body. request body.
4.1 Example: BIND 4.1 Example: BIND
>> Request: >> Request:
BIND /CollY HTTP/1.1 BIND /CollY HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:bind xmlns:D="DAV:"> <D:bind xmlns:D="DAV:">
<D:segment>bar.html</D:segment> <D:segment>bar.html</D:segment>
<D:href>http://www.example.com/CollX/foo.html</D:href> <D:href>http://www.example.com/CollX/foo.html</D:href>
</D:bind> </D:bind>
>> Response: >> Response:
HTTP/1.1 201 Created HTTP/1.1 201 Created
The server added a new binding to the collection, The server added a new binding to the collection, "http://
"http://www.example.com/CollY", associating "bar.html" with the www.example.com/CollY", associating "bar.html" with the resource
resource identified by the URI identified by the URI "http://www.example.com/CollX/foo.html".
"http://www.example.com/CollX/foo.html". Clients can now use the Clients can now use the URI "http://www.example.com/CollY/bar.html",
URI "http://www.example.com/CollY/bar.html", to submit requests to to submit requests to that resource.
that 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-URI, by removing the binding identified by the segment Request-URI, by removing the binding identified by the segment
specified in the UNBIND body. specified in 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
Clemm, et al. [Page 15]
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.
Marshalling: Marshalling:
The request body MUST be a DAV:unbind XML element. The request body MUST be a DAV:unbind XML element.
<!ELEMENT unbind (segment)> <!ELEMENT unbind (segment)>
If the request succeeds, the server MUST return 200 (OK) when the If the request succeeds, the server MUST return 200 (OK) when the
binding was successfully deleted. binding was successfully deleted.
If a response body for a successful request is included, it MUST be If a response body for a successful request is included, it MUST
a DAV:unbind-response XML element. Note that this document does be a DAV:unbind-response XML element. Note that this document
not define any elements for the UNBIND response body, but the does not define any elements for the UNBIND response body, but the
DAV:unbind-response element is defined to ensure interoperability DAV:unbind-response element is defined to ensure interoperability
between future extensions that do define elements for the UNBIND between future extensions that do define elements for the UNBIND
response body. response body.
<!ELEMENT unbind-response ANY> <!ELEMENT unbind-response ANY>
Preconditions: Preconditions:
(DAV:unbind-from-collection): The Request-URI MUST identify a (DAV:unbind-from-collection): The Request-URI MUST identify a
collection. collection.
(DAV:unbind-source-exists): The DAV:segment element MUST identify a (DAV:unbind-source-exists): The DAV:segment element MUST identify
binding in the collection identified by the Request-URI. a binding in the collection identified by the Request-URI.
(DAV:locked-update-allowed): If the collection identified by the (DAV:locked-update-allowed): If the collection identified by the
Request-URI is write-locked, then the appropriate token MUST be Request-URI is write-locked, then the appropriate token MUST be
specified in the request. specified in the request.
(DAV:protected-url-deletion-allowed): If the binding identified by (DAV:protected-url-deletion-allowed): If the binding identified by
the segment is protected by a write-lock, then the appropriate the segment is protected by a write-lock, then the appropriate
token MUST be specified in the request. token MUST be specified in the request.
Postconditions: Postconditions:
skipping to change at line 801 skipping to change at page 19, line 15
5.1 Example: UNBIND 5.1 Example: UNBIND
>> Request: >> Request:
UNBIND /CollX HTTP/1.1 UNBIND /CollX HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
Clemm, et al. [Page 16]
<D:unbind xmlns:D="DAV:"> <D:unbind xmlns:D="DAV:">
<D:segment>foo.html</D:segment> <D:segment>foo.html</D:segment>
</D:unbind> </D:unbind>
>> Response: >> Response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
The server removed the binding named "foo.html" from the The server removed the binding named "foo.html" from the collection,
collection, "http://www.example.com/CollX". A request to the "http://www.example.com/CollX". A request to the resource named
resource named "http://www.example.com/CollX/foo.html" will return "http://www.example.com/CollX/foo.html" will return a 404 (Not Found)
a 404 (Not Found) response. response.
6 REBIND METHOD 6. REBIND Method
The REBIND method removes a binding to a resource from one The REBIND method removes a binding to a resource from one
collection, and adds a binding to that resource into another collection, and adds a binding to that resource into another
collection. It is effectively an atomic form of a MOVE request. collection. It is effectively an atomic form of a MOVE request.
Marshalling: Marshalling:
The request MAY include an Overwrite header. The request MAY include an Overwrite header.
The request body MUST be a DAV:rebind XML element. The request body MUST be a DAV:rebind XML element.
<!ELEMENT rebind (segment, href)> <!ELEMENT rebind (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 was a new binding was created and 200 (OK) when an existing binding
replaced. was replaced.
If a response body for a successful request is included, it MUST be If a response body for a successful request is included, it MUST
a DAV:rebind-response XML element. Note that this document does be a DAV:rebind-response XML element. Note that this document
not define any elements for the REBIND response body, but the does not define any elements for the REBIND response body, but the
DAV:rebind-response element is defined to ensure interoperability DAV:rebind-response element is defined to ensure interoperability
between future extensions that do define elements for the REBIND between future extensions that do define elements for the REBIND
response body. response body.
<!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: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:href element in the request body is on another server from the DAV:href element in the request body is on another server from the
Clemm, et al. [Page 17]
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 line 888 skipping to change at page 20, line 50
identified by the Request-URI already contains a binding with the identified by the Request-URI already contains a binding with the
specified path segment, and if that binding is protected by a specified path segment, and if that binding is protected by a
write-lock, then the appropriate token MUST be specified in the write-lock, then the appropriate token MUST be specified in the
request. request.
(DAV:locked-source-collection-update-allowed): If the collection (DAV:locked-source-collection-update-allowed): If the collection
identified by the parent collection prefix of the DAV:href URI is identified by the parent collection prefix of the DAV:href URI is
write-locked, then the appropriate token MUST be specified in the write-locked, then the appropriate token MUST be specified in the
request. request.
(DAV:protected-source-url-deletion-allowed): If the DAV:href URI is (DAV:protected-source-url-deletion-allowed): If the DAV:href URI
protected by a write lock, then the appropriate token MUST be is protected by a write lock, then the appropriate token MUST be
specified in the request. specified in the request.
Postconditions: Postconditions:
(DAV:new-binding): The collection MUST have a binding that maps the (DAV:new-binding): The collection MUST have a binding that maps
segment specified in the DAV:segment element in the request body, the segment specified in the DAV:segment element in the request
to the resource that was identified by the DAV:href element in the body, to the resource that was identified by the DAV:href element
request body. in the request body.
(DAV:binding-deleted): The URL specified in the DAV:href element in (DAV:binding-deleted): The URL specified in the DAV:href element
the request body MUST NOT be mapped to a resource. in the request body MUST NOT be mapped to a resource.
6.1 Example: REBIND 6.1 Example: REBIND
>> Request: >> Request:
REBIND /CollX HTTP/1.1 REBIND /CollX HTTP/1.1
Host: www.example.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Clemm, et al. [Page 18]
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:rebind xmlns:D="DAV:"> <D:rebind xmlns:D="DAV:">
<D:segment>foo.html</D:segment> <D:segment>foo.html</D:segment>
<D:href>http://www.example.com/CollY/bar.html</D:href> <D:href>http://www.example.com/CollY/bar.html</D:href>
</D:rebind> </D:rebind>
>> Response: >> Response:
HTTP/1.1 200 OK HTTP/1.1 200 OK
The server added a new binding to the collection, The server added a new binding to the collection, "http://
"http://www.example.com/CollX", associating "foo.html" with the www.example.com/CollX", associating "foo.html" with the resource
resource identified by the URI identified by the URI "http://www.example.com/CollY/bar.html", and
"http://www.example.com/CollY/bar.html", and removes the binding removes the binding named "bar.html" from the collection identified
named "bar.html" from the collection identified by the URI by the URI "http://www.example.com/CollY". Clients can now use the
"http://www.example.com/CollY". Clients can now use the URI URI "http://www.example.com/CollX/foo.html" to submit requests to
"http://www.example.com/CollX/foo.html" to submit requests to that that resource, and requests on the URI "http://www.example.com/CollY/
resource, and requests on the URI bar.html" will fail with a 404 (Not Found) response.
"http://www.example.com/CollY/bar.html" will fail with a 404 (Not
Found) response.
7 ADDITIONAL STATUS CODES
7.1 506 Loop Detected
The 506 (Loop Detected) status code indicates that the server 7. Additional Status Codes
terminated an operation because it encountered an infinite loop
while processing a request with "Depth: infinity".
When this status code is the top-level status code for the 7.1 208 Already Reported
operation, it indicates that the entire operation failed.
When this status code occurs inside a multi-status response, it The 208 (Already Reported) status code can be used inside a
indicates only that a loop is being terminated, but does not DAV:propstat response element to indicate that information about the
indicate failure of the operation as a whole. resource has already been reported in a previous DAV:propstat element
in that response. The members of the 208 status resource are omitted
from the response.
For example, consider a PROPFIND request on /Coll (bound to For example, consider a PROPFIND request on /Coll (bound to
collection C), where the members of /Coll are /Coll/Foo (bound to collection C), where the members of /Coll are /Coll/Foo (bound to
resource R) and /Coll/Bar (bound to collection C). resource R) and /Coll/Bar (bound to collection C).
>> Request: >> Request:
PROPFIND /Coll/ HTTP/1.1 PROPFIND /Coll/ HTTP/1.1
Host: www.example.com Host: www.example.com
Depth: infinity Depth: infinity
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:displayname/> </D:prop> <D:prop> <D:displayname/> </D:prop>
</D:propfind> </D:propfind>
Clemm, et al. [Page 19]
>> Response: >> Response:
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
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>
skipping to change at line 994 skipping to change at page 23, line 32
<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: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:status>HTTP/1.1 506 Loop Detected</D:status> <D:propstat>
<D:prop>
<D:displayname>Loop Demo</D:displayname>
</D:prop>
<D:status>HTTP/1.1 208 Already Reported</D:status>
</D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
8 SECURITY CONSIDERATIONS A client can request the DAV:resourceid property in a PROPFIND
request to guarantee that they can accurately reconstruct the binding
structure of a collection with multiple bindings to a single
resource.
7.2 506 Loop Detected
The 506 (Loop Detected) status code indicates that the server
terminated an operation because it encountered an infinite loop while
processing a request with "Depth: infinity". This status indicates
that the entire operation failed.
8. Security Considerations
This section is provided to make WebDAV applications aware of the This section is provided to make WebDAV applications 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 protocol specification. In addition, bindings introduce several new
new security concerns and increase the risk of some existing security concerns and increase the risk of some existing threats.
threats. These issues are detailed below. These issues are detailed below.
8.1 Privacy Concerns 8.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 bindings on a trusted server may make it possible for a hostile agent
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.
Clemm, et al. [Page 20]
8.2 Redirect Loops 8.2 Redirect Loops
Although redirect loops were already possible in HTTP 1.1, the Although redirect 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 target are on the same server, the server may be able to detect BIND
BIND requests that would create loops. Servers are required to requests that would create loops. Servers are required to detect
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".
8.3 Bindings, and Denial of Service 8.3 Bindings, and Denial of Service
Denial of service attacks were already possible by posting URIs Denial of service attacks were already possible by posting URIs that
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 service attacks. If cross-server bindings are supported, clients can
can now create bindings at heavily used sites to target locations now create bindings at heavily used sites to target locations that
that were not designed for heavy usage. were not designed for heavy usage.
8.4 Private Locations May Be Revealed 8.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 anyone who has access to the DAV:parent-set property on the resource.
resource. Moving a binding may reveal its new location to anyone Moving a binding may reveal its new location to anyone with access to
with access to DAV:parent-set on its resource. DAV:parent-set on its resource.
8.5 DAV:parent-set and Denial of Service 8.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.
9 INTERNATIONALIZATION CONSIDERATIONS 9. Internationalization Considerations
All internationalization considerations mentioned in [RFC2518] also All internationalization considerations mentioned in [RFC2518] also
apply to this document. apply to this document.
10 IANA CONSIDERATIONS 10. IANA Considerations
All IANA considerations mentioned in [RFC2518] also apply to this All IANA considerations mentioned in [RFC2518] also apply to this
document. document.
Clemm, et al. [Page 21] 11. Acknowledgements
11 INTELLECTUAL PROPERTY
The following notice is copied from RFC 2026, Section 10.4, and
describes the position of the IETF concerning intellectual property
claims made against this document.
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use other technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on
the procedures of the IETF with respect to rights in standards-
track and standards-related documentation can be found in BCP-11.
Copies of claims of rights made available for publication 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 Secretariat.
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 practice
this standard. Please address the information to the IETF
Executive Director.
12 ACKNOWLEDGEMENTS
This draft is the collaborative product of the authors and Tyson This draft is the collaborative product of the authors and Tyson
Chihaya, Jim Davis, and Chuck Fay. This draft has benefited from Chihaya, Jim Davis, and Chuck Fay. This draft has benefited from
thoughtful discussion by Jim Amsden, Peter Carlson, Steve Carter, thoughtful discussion by Jim Amsden, Peter Carlson, Steve Carter, Ken
Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Spencer Dawkins, Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Spencer Dawkins, Mark
Mark Day, Rajiv Dulepet, David Durand, Roy Fielding, Yaron Goland, Day, Rajiv Dulepet, David Durand, Roy Fielding, Yaron Goland, Fred
Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Kaler, Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Kaler, Manoj
Manoj Kasichainula, Rohit Khare, Daniel LaLiberte, Steve Martin, Kasichainula, Rohit Khare, Daniel LaLiberte, Steve Martin, Larry
Larry Masinter, Jeff McAffer, Surendra Koduru Reddy, Max Rible, Sam Masinter, Jeff McAffer, Surendra Koduru Reddy, Max Rible, Sam Ruby,
Ruby, Bradley Sergeant, Nick Shelness, John Stracke, John Tigue, Bradley Sergeant, Nick Shelness, John Stracke, John Tigue, John
John Turner, Kevin Wiggen, and other members of the WebDAV working Turner, Kevin Wiggen, and other members of the WebDAV working group.
group.
13 REFERENCES
[RFC2026] S.Bradner, "The Internet Standards Process", RFC 2026, Normative References
October 1996.
[RFC2119] S.Bradner, "Key words for use in RFCs to Indicate [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
Requirement Levels", RFC 2119, March 1997. 3", BCP 9, RFC 2026, October 1996.
[RFC2277] H.Alvestrand, "IETF Policy on Character Sets and [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Languages." RFC 2277, January 1998. Requirement Levels", BCP 14, RFC 2119, March 1997.
Clemm, et al. [Page 22] [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
[RFC2396] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396,
Resource Identifiers (URI): Generic Syntax." RFC 2396, August 1998. August 1998.
[RFC2518] Y.Goland, E.Whitehead, A.Faizi, S.R.Carter, D.Jensen, [RFC2518] Goland, Y., Whitehead, E., Faizi, A., Carter, S. and D.
"HTTP Extensions for Distributed Authoring - WEBDAV", RFC 2518, Jensen, "HTTP Extensions for Distributed Authoring --
February 1999. WEBDAV", RFC 2518, February 1999.
[RFC2616] R.Fielding, J.Gettys, J.C.Mogul, H.Frystyk, L.Masinter, [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
P.Leach, and T.Berners-Lee, "Hypertext Transfer Protocol -- Masinter, L., Leach, P. and T. Berners-Lee, "Hypertext
HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[XML] T. Bray, J. Paoli, C.M. Sperberg-McQueen, "Extensible Markup [XML] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler,
Language (XML) 1.0 (Second Edition)" W3C Recommendation 6 October "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C
2000. http://www.w3.org/TR/2000/REC-xml-20001006. REC-xml, October 2000, <http://www.w3.org/TR/2000/
REC-xml-20001006>.
14 AUTHORS' ADDRESSES Authors' Addresses
Geoffrey Clemm Geoffrey Clemm
Rational Software Corporation IBM
20 Maguire Road 20 Maguire Road
Lexington, MA 02173-3104 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, Germany Muenster, NW 48159
Email: julian.reschke@greenbytes.de Germany
EMail: julian.reschke@greenbytes.de
Judy Slein Judy Slein
Xerox Corporation Xerox Corporation
800 Phillips Road, 105-50C 800 Phillips Road, 105-50C
Webster, NY 14580 Webster, NY 14580
Email: jslein@crt.xerox.com
EMail: jslein@crt.xerox.com
Jim Whitehead Jim Whitehead
UC Santa Cruz, Dept. of Computer Science UC Santa Cruz, Dept. of Computer Science
1156 High Street, Santa Cruz, CA 95064 1156 High Street
Email: ejw@cse.ucsc.edu Santa Cruz, CA 95064
EMail: ejw@cse.ucsc.edu
Appendix A. Change Log (to be removed by RFC Editor before publication)
A.1 Since draft-ietf-webdav-bind-02
Add and resolve issues "2.3_COPY_SHARED_BINDINGS" and
"2.3_MULTIPLE_COPY". Add issue "5.1_LOOP_STATUS" and proposed
resolution, but keep it open. Add issues "ED_references" and
"4_507_status". Started work on index. Rename document to "Binding
Extensions to Web Distributed Authoring and Versioning (WebDAV)".
Rename "References" to "Normative References". Close issue
"ED_references". CLose issue "4_507_status".
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 ED_references
Type: edit
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003OctDec/
0283.html>
julian.reschke@greenbytes.de (2003-12-09): (1) Distinguish normative
and informative references, (2) text referring to RFC2119 is missing,
(3) references to RFC2277, RFC2616 and XML not needed.
Resolution (2003-12-11): Editorial changes applied.
B.2 2.3_COPY_SHARED_BINDINGS
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003JulSep/
0010.html>
Peter.Nevermann@softwareag.com (2003-07-10): What if a copied
collection has two bindings to the same resource.
Resolution (2003-08-21): Recommend that only one resource with
multiple bindings to it be created by the COPY.
B.3 2.3_MULTIPLE_COPY
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003JulSep/
0124.html>
Peter.Nevermann@softwareag.com (2003-08-17): What two resources are
copied to the same resource by a single COPY.
Resolution (2003-08-21): Server decides order of updates.
B.4 4_507_status
Type: change
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2003OctDec/
0282.html>
julian.reschke@greenbytes.de (2003-12-09): Section 4 refers to a
definition of a 507 status code in Section 7.1, which doesn't exist.
Should this text be replaced by a reference to the
DAV:cross-server-binding precondition?
Resolution (2003-12-11): Change wording to refer to precondition
name.
Appendix C. Open issues (to be removed by RFC Editor before publication)
C.1 5.1_LOOP_STATUS
Type: change
julian.reschke@greenbytes.de (2002-10-11): Should the 506 status in a
PROPFIND be handled differently?
geoffrey.clemm@us.ibm.com (2003-08-03): Use new 208 status to report
cycles in PROPFIND.
julian.reschke@greenbytes.de (2003-11-16): Proposal: a) import DAV
request header definition from rfc2518bis (note that the definition
in the latest draft probably needs some more work) b) define a DAV
compliance class for the BIND spec c) clarify that 208 should only be
returned when the client specifies compliance to the BIND spec in the
PROPFIND request (otherwise fail the complete request).
Index
2
208 Already Reported (status code) 21
5
506 Loop Detected (status code) 23
B
BIND method 15
C
Condition Names
DAV:bind-into-collection (pre) 16
DAV:bind-source-exists (pre) 16
DAV:binding-allowed (pre) 16, 20
DAV:binding-deleted (post) 18, 21
DAV:can-overwrite (pre) 16, 20
DAV:cross-server-binding (pre) 16, 20
DAV:cycle-allowed (pre) 16, 20
DAV:locked-overwrite-allowed (pre) 16
DAV:locked-source-collection-update-allowed (pre) 20
DAV:locked-update-allowed (pre) 16, 18, 20
DAV:name-allowed (pre) 16, 20
DAV:new-binding (post) 17, 21
DAV:protected-source-url-deletion-allowed (pre) 20
DAV:protected-url-deletion-allowed (pre) 18
DAV:protected-url-modification-allowed (pre) 20
DAV:rebind-into-collection (pre) 20
DAV:rebind-source-exists (pre) 20
DAV:unbind-from-collection (pre) 18
DAV:unbind-source-exists (pre) 18
D
DAV:bind-into-collection precondition 16
DAV:bind-source-exists precondition 16
DAV:binding-allowed precondition 16, 20
DAV:binding-deleted postcondition 18, 21
DAV:can-overwrite precondition 16, 20
DAV:cross-server-binding precondition 16, 20
DAV:cycle-allowed precondition 16, 20
DAV:locked-overwrite-allowed precondition 16
DAV:locked-source-collection-update-allowed precondition 20
DAV:locked-update-allowed precondition 16, 18, 20
DAV:name-allowed precondition 16, 20
DAV:new-binding postcondition 17, 21
DAV:parent-set property 14
DAV:protected-source-url-deletion-allowed precondition 20
DAV:protected-url-deletion-allowed precondition 18
DAV:protected-url-modification-allowed precondition 20
DAV:rebind-into-collection precondition 20
DAV:rebind-source-exists precondition 20
DAV:resource-id property 14
DAV:unbind-from-collection precondition 18
DAV:unbind-source-exists precondition 18
M
Methods
BIND 15
REBIND 19
UNBIND 17
P
Properties
DAV:parent-set 14
DAV:resource-id 14
R
REBIND method 19
S
Status Codes
208 Already Reported 21
506 Loop Detected 23
U
UNBIND method 17
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property 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; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication 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 implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 

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