Xerox Corporation

800 Phillips Road, 105-50C WebsterNY14580 jslein@crt.xerox.com

Dept. of Information and Computer Science

IrvineCA92697-3425 ejw@ics.uci.edu

CourseNet Systems

170 Capp Street San FranciscoCA94110 jrd3@alum.mit.edu

Rational Software Corporation

20 Maguire Road LexingtonMA02173-3104 gclemm@rational.com

FileNet Corporation

3565 Harbor Boulevard Costa MesaCA92626-1420 cfay@filenet.com

IBM Research

P.O. Box 704 Yorktown HeightsNY10598 ccjason@us.ibm.com

WEBDAV Working Group This is one of a pair of specifications that extend the WebDAV Distributed Authoring Protocol to enable clients to create new access paths to existing resources. The two protocol extensions have very different characteristics that make them useful for different sorts of applications. The present specification defines bindings, and the BIND method for creating them. Creating a new binding to a resource indirectly creates one or more new URIs mapped to that resource, which can then be used to access it. Servers are required to insure the integrity of any bindings that they allow to be created. The related specification, RFC xxxx, defines redirect reference resources. A redirect reference resource is a resource whose default response is an HTTP/1.1 302 (Found) status code, redirecting the client to a different resource, the target resource. A redirect reference makes it possible to access the target resource indirectly, through any URI mapped to the redirect reference resource. There are no integrity guarantees associated with redirect reference resources. Distribution of this document is unlimited. Please send comments to the Distributed Authoring and Versioning (WebDAV) working group at w3c-dist-auth@w3.org, which may be joined by sending a message with subject "subscribe" to w3c-dist-auth-request@w3.org. Discussions of the WEBDAV working group are archived at URL: http://lists.w3.org/Archives/Public/w3c-dist-auth/.

Since this document describes a set of extensions to the WebDAV Distributed Authoring Protocol , itself an extension to the HTTP/1.1 protocol, the augmented BNF used here to describe protocol elements is exactly the same as described in Section 2.1 of . Since this augmented BNF uses the basic production rules provided in Section 2.2 of , these rules apply to this document as well. 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 .

This is one of a pair of specifications that extend the WebDAV Distributed Authoring Protocol to enable clients to create new access paths to existing resources. This capability is useful for several reasons: URIs of WebDAV-compliant resources are hierarchical and correspond to a hierarchy of collections in resource space. The WebDAV Distributed Authoring Protocol makes it possible to organize these resources into hierarchies, placing them into groupings, known as collections, which are more easily browsed and manipulated than a single flat collection. However, hierarchies require categorization decisions that locate resources at a single location in the hierarchy, a drawback when a resource has multiple valid categories. For example, in a hierarchy of vehicle descriptions containing collections for cars and boats, a description of a combination car/boat vehicle could belong in either collection. Ideally, the description should be accessible from both. Allowing clients to create new URIs that access the existing resource lets them put that resource into multiple collections. Hierarchies also make resource sharing more difficult, since resources that have utility across many collections are still forced into a single collection. For example, the mathematics department at one university might create a collection of information on fractals that contains bindings to some local resources, but also provides access to some resources at other universities. For many reasons, it may be undesirable to make physical copies of the shared resources on the local server: to conserve disk space, to respect copyright constraints, or to make any changes in the shared resources visible automatically. Being able to create new access paths to existing resources in other collections or even on other servers is useful for this sort of case. The BIND method defined here provides a mechanism for allowing clients to create alternative access paths to existing WebDAV resources. HTTP and WebDAV methods are able to work because there are mappings between URIs and resources. A method is addressed to a URI, and the server follows the mapping from that URI to a resource, applying the method to that resource. Multiple URIs may be mapped to the same resource, but until now there has been no way for clients to create additional URIs mapped to existing resources. 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. Since URIs of WebDAV resources are hierarchical, and correspond to a hierarchy of collections in resource space, the BIND method also has the effect of adding the resource to a collection. As new URIs are associated with the resource, it appears in additional collections. The companion specification, RFC xxxx, defines redirect reference resources, a different mechanism for creating alternative access paths to existing resources. A redirect reference is a resource in one collection whose purpose is to forward requests to another resource (its target), usually in a different collection. In this way, it provides access to the target resource from another collection. It redirects most requests to the target resource using the HTTP 302 (Moved Temporarily) status code, thereby providing a form of mediated access to the target resource. Bindings and redirect reference resources have very different characteristics: A BIND request does not create a new resource, but simply makes available a new URI for submitting requests to an existing resource. The new URI is indistinguishable from any other URI when submitting a request to a resource. Only one round trip is needed to submit a request to the intended target. Servers are required to enforce the integrity of the relationships between the new URIs and the resources associated with them. Consequently, it may be very costly for servers to support BIND requests that cross server boundaries. A redirect reference is a resource, and so can have properties of its own. Properties of the redirect reference can contain such information as who created the reference, when, and why. Since redirect references are implemented using HTTP 302 responses, it generally takes two round trips to submit a request to the intended resource. Servers are not required to enforce the integrity of redirect references. Redirect references work equally well for local resources and for resources that reside on a different server from the reference. The remainder of this specification is organized as follows. Section 3 defines terminology used in the rest of the specification, while Section 4 briefly overviews bindings. Section 5 specifies the BIND method, used to create bindings. Sections 6 through 9 discuss the relationships between bindings and other HTTP and WebDAV methods. Sections 10 and 11 define mechanisms for tracking bindings. Sections 12 through 14 define the new status codes, properties, and XML elements needed to support bindings. Section 15 discusses compliance and capability discovery. Security concerns, internationalization issues, and IANA considerations are described in Sections 16 through 18. The remaining sections provide other supporting information.

The terminology used here follows and extends that in the WebDAV Distributed Authoring Protocol specification . Definitions of the terms resource, Uniform Resource Identifier (URI), and Uniform Resource Locator (URL) are provided in . URI Mapping A relation between an absolute URI and a resource. For an absolute URI U and the resource it identifies R, the URI mapping can be thought of as (U => R). Since a resource can represent items that are not network retrievable, as well as those that are, it is possible for a resource to have zero, one, or many URI mappings. Mapping a resource to an "http" scheme URL makes it possible to submit HTTP protocol requests to the resource using the URL. Path Segment Informally, the characters found between slashes ("/") in a URI. Formally, as defined in section 3.3 of . Binding 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 different collections contain a binding between the same path segment and the same resource, these are two distinct bindings. So for a collection C, a path segment S, and a resource R, the binding can be thought of as C:(S -> R). Bindings create URI mappings, and hence allow requests to be sent to a single resource from multiple locations in a URI namespace. For example, given collection C, accessible through the URI http://www.srv.com/coll/, path segment S, equal to "foo.html", and resource R, creating the binding C: (S -> R) makes it possible to use the URI http://www.srv.com/coll/foo.html to access R. The following figure illustrates a more complex example of how bindings create URI mappings.

+-----------------------------+ | root collection | |-----------------------------| | bindings: | | | | Coll1 Coll2 Coll3 | | | | \ | +---|-------|--------\--------+ | | \ | | \ +-------------------+ +----------------------+ | collection C1 | | collection C2 | |-------------------| |----------------------| | bindings: | | bindings: | | | | | | foo bar | | foo | | | \ | | / | +--|------\---------+ +-/--------------------+ | \ / | \ / | \ / | \ / +--------------+ +---------------+ | resource R1 | | resource R2 | +--------------+ +---------------+

Since there are two bindings in the root collection, Coll1 and Coll2, to collection C1, the single binding C1:(foo -> R1) between foo and resource R1 in collection C1 creates two URI mappings, /Coll1/foo and /Coll2/foo, to resource R1. Each of these URI mappings can be used to submit requests to R1. The binding C1:(bar -> R2) between bar and resource R2 in collection C1 and the binding C2:(foo -> R2) between foo and resource R2 in collection C2 create altogether 3 URI mappings to resource R2: /Coll1/bar, /Coll2/bar, and /Coll3/foo. All 3 URI mappings can be used to submit requests to resource R2. Collection A resource that contains, as part of its state, a set of bindings that identify member resources. Internal Member URI Informally, the complete set of URLs by which a collection member is known. Formally, the URI U of a URI mapping (U => R), created by a binding that is contained in a collection. The following figure illustrates the relationship between bindings and internal member URIs in a collection:

+-----------------------------+ | root collection | |-----------------------------| | internal member URIs: | | | | /Coll1/ | | /Coll2/ | | /Coll3/ | |-----------------------------| | bindings: | | | | Coll1 Coll2 Coll3 | | | | \ | +---|-------|--------\--------+ | | \ | | \ +----------------------+ +----------------------+ | collection C1 | | collection C2 | |----------------------| |----------------------| | internal member URIs:| | internal member URIs:| | | | | | /Coll1/foo | | /Coll3/foo | | /Coll2/foo | |----------------------| | /Coll1/bar | | bindings: | | /Coll2/bar | | | |----------------------| | foo | | bindings: | | / | | | +-/--------------------+ | foo bar | / | | \ | / +--|------\------------+ / | \ / | \ / | \ / | \ / +--------------+ +---------------+ | resource R1 | | resource R2 | +--------------+ +---------------+

The URIs of all URI mappings created by a collection's bindings are internal member URIs of the collection. However, for a given request, only the URIs from those URI mappings that incorporate the Request-URI are treated as internal member URIs. This is done to prevent large amounts of duplicate information from being returned for operations on collections. The problem would occur if a PROPFIND on a collection to which there are multiple URI mappings returned information for every URI mapping. For example, in above, if a PROPFIND request with "Depth infinity" is submitted to collection C1 using the Request-URI /Coll1/, only the URI mappings starting with the Request-URI would be listed as internal member URIs. The response would include only /Coll1/ itself and the internal member URIs /Coll1/foo and /Coll1/bar. It would not include /Coll2/, /Coll2/foo, or /Coll2/bar, even though the URI /Coll2/ does map to the collection, and /Coll2/foo and /Coll2/bar are internal member URIs of the collection. In , a collection is defined as containing a list of internal member URIs, where an internal member URI is the URI of the collection, plus a single path segment. This definition combines the two concepts of binding and URI mapping that are separated in this specification. As a result, this specification redefines a collection's state to be a set of bindings, and redefines an internal member URI to be the URI of a URI mapping derived from a binding. After this redefinition, an internal member URI can be used when reading without loss of meaning. For purposes of interpretation, when discusses a collection "containing" an internal member URI, this should be read as the collection containing a binding whose mapping to a URI creates an internal member URI, in this sense "containing" the internal member URI. The authors of this specification anticipate and recommend that future revisions of perform a full reconciliation of terms between these two specifications.

Consider again collection C1 in . If we had only the notion of URI mappings, we would be forced to say that C1's membership was defined by the list of internal member URIs. If these URIs identify the membership, and are part of the state of the collection, then the act of making the collection available via a new URI has the effect of changing the collection's membership, hence changing the collection's state. This is undesirable, since ideally a collection's membership should remain the same, if suddenly a new URI can be used to access the collection. What is needed is a way to separate the final segment of a URI from the collection's URI contribution. The notion of binding is introduced to separate the final segment of a URI from its parent collection's contribution. This done, a collection can be defined as containing a set of bindings, thus permitting new mappings to a collection without modifying its membership. We introduce the concept of URI mapping to combine together the collection's URI and a binding's segment to create a full URI that can be used in protocol requests. Finally, the internal member URI, first defined in , is redefined here to maintain backward compatibility with that specification.

Bindings are part of the state of a collection. In general, there is a one-to-many correspondence between a collection's bindings and its internal member URIs, as illustrated in above. The URI segment associated with a resource by one of a collection's bindings is also the final segment of one or more of the collection's internal member URIs. The final segment of each internal member URI identifies one of the bindings that is part of the collection's state. Bindings are not unique to advanced collections, although the BIND method for explicitly creating bindings is introduced here. Existing methods that create resources, such as PUT, MOVE, COPY, and MKCOL, implicitly create bindings. There is no difference between implicitly created bindings and bindings created with BIND. The identity of a binding C:(S -> R) is determined by the URI segment (in its collection) and the resource that the binding associates. If the resource goes out of existence (as a result of some out-of-band operation), the binding also goes out of existence. If the URI segment comes to be associated with a different resource, the original binding ceases to exist and another binding is created. It would be very undesirable if one binding could be destroyed as a side effect of operating on the resource through a different binding. It is not acceptable for moving a resource through one binding to disrupt another binding, turning that binding into a dangling path segment. Nor is it acceptable for a server, after removing one binding, to reclaim the system resources associated with its resource while other bindings to the resource remain. Implementations MUST ensure the integrity of bindings.

The BIND method creates a new binding between the resource identified by the Request-URI and the final segment of the Destination header (minus any trailing slash). This binding is added to the collection identified by the Destination header minus its trailing slash (if present) and final segment. The Destination header is defined in Section 9.3 of . If a server cannot guarantee the binding behavior specified here, including the guarantee of the integrity of the binding, the BIND request MUST fail. Note: It is especially difficult to maintain the integrity of cross-server bindings. Unless the server where the resource resides knows about all bindings on all servers to that resource, it may unwittingly destroy the resource or move it without notifying another server that manages a binding to the resource. For example, if server A permits creation of a binding to a resource on server B, server A must notify server B about its binding and must have an agreement with B that B will not destroy the resource while A's binding exists. Otherwise server B may receive a DELETE request that it thinks removes the last binding to the resource and destroy the resource while A's binding still exists. Status code 507 (Cross-server Binding Forbidden) is defined in Section 12.2 for cases where servers must fail cross-server BIND requests because they cannot guarantee the integrity of cross-server bindings. If the Destination header does not contain a path segment (i.e., it consists simply of a slash "/"), the BIND operation MUST fail and report a 400 (Bad Request) status code. A binding consists of a (collection, segment, resource) triple, and the Destination header is required to specify the collection and segment of this triple. If the Destination header minus its final path segment does not identify a collection, the BIND operation MUST fail and report a 400 (Bad Request) status code. Note: Section 5.1 of defines a consistent namespace to be one such that "for every URL in the HTTP hierarchy there exists a collection that contains that URL as an internal member," but does not require namespaces to be consistent. There can exist URIs that map to resources, but do not depend on the existence of collections for the mapping. For example, the URI http://www.svr.com/x/y.html may map to resource R even if the URI http://www.svr.com/x/ does not map to any resource. This specification does not support the creation of such URI mappings. The BIND method can be used only in consistent sections of a namespace. After successful processing of a BIND request, it MUST be possible for clients to use the URI in the Destination header to submit requests to the resource identified by the Request-URI. By default, if the Destination header identifies an existing binding, the new binding replaces the existing binding. This default binding replacement behavior can be overridden using the Overwrite header defined in Section 9.6 of .

Bindings to collections can result in loops. If a server wants to prevent a loop from being created, it MAY fail the BIND request with a 403 (Forbidden) status code. If a server allows a loop to be created, it MUST detect the loop when processing "Depth: infinity" requests that encounter the loop. It is sometimes possible to complete an operation in spite of the presence of a loop. However, the 506 (Loop Detected) status code is defined in Section 12.1 for use in contexts where an operation is terminated because a loop was encountered. Creating a new binding to a collection makes each resource associated with a binding in that collection accessible via a new URI, and thus creates new URI mappings to those resources but no new bindings. For example, suppose a new binding COLLX is created for collection C1 in the figure below. It immediately becomes possible to access resource R1 using the URI /COLLX/x.gif and to access resource R2 using the URI /COLLX/y.jpg, but no new bindings for these child resources were created. This is because bindings are part of the 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 C1 is needed to make its children accessible using /COLLX/x.gif and /COLLX/y.jpg.

+-------------------------+ | Root Collection | | (properties) | | bindings: | | coll1 COLLX | +-------------------------+ | / | / | / +------------------+ | Collection C1 | | (properties) | | bindings: | | x.gif y.jpg | +------------------+ | \ | \ | \ +-------------+ +-------------+ | Resource R1 | | Resource R2 | +-------------+ +-------------+

Suppose a BIND request causes a binding from "Binding-Name" to resource R to be added to a collection, C. Then if C-MAP is the set of URI's that were mapped to C before the BIND request, then for each URI "C-URI" in C-MAP, the URI "C-URI/Binding-Name" is mapped to resource R following the BIND request. 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 collection C to C itself (or to a parent of C), an infinite number of mappings is introduced.

For example, if a binding from "foo.html" to R is added to a collection C, and if the following URI's are mapped to C:

http://www.fuzz.com/A/1 http://fuzz.com/A/one

then the following new mappings to R are introduced:

http://www.fuzz.com/A/1/foo.html http://fuzz.com/A/one/foo.html

If a binding from "myself" to C is then added to C, the following infinite number of additional mappings to C are introduced:

http://www.fuzz.com/A/1/myself http://www.fuzz.com/A/1/myself/myself ...

and the following infinite number of additional mappings to R are introduced:

http://www.fuzz.com/A/1/myself/foo.html http://www.fuzz.com/A/1/myself/myself/foo.html ...

201 (Created): The binding was successfully created. 400 (Bad Request): The client set an invalid value for the Destination header or Request-URI. 403 (Forbidden): This server has a policy that forbids creation of bindings that would result in loops. 412 (Precondition Failed): The Overwrite header is "F", and a binding already exists for the Destination header. 507 (Cross-Server Binding Forbidden): The server is unable to create the requested binding because it would bind a segment in a collection on one server to a resource on a different server.

>> Request: BIND /pub/i-d/draft-webdav-protocol-08.txt HTTP/1.1 Host: www.ics.uci.edu Destination: http://www.ics.uci.edu/~whitehead/dav/spec08.txt

>> Response: HTTP/1.1 201 Created

The server created a new binding, associating "spec08.txt" with the resource identified by the URL "http://www.ics.uci.edu/pub/i-d/draft- webdav-protocol-08.txt". Clients can now use the URI in the Destination header, "http://www.ics.uci.edu/~whitehead/dav/spec08.txt", to submit requests to that resource. As part of this operation, the server added the binding "spec08.txt" to collection /~whitehead/dav/.

The DELETE method was originally defined in . This section redefines the behavior of DELETE in terms of bindings, an abstraction not available when writing . states that "the DELETE method requests that the origin server delete the resource identified by the Request-URI." Because did not distinguish between bindings and resources, the intent of its definition of DELETE is unclear. The definition presented here is a clarification of the definition in . The DELETE method requests that the server remove the binding between the resource identified by the Request-URI and the binding name, the last path segment of the Request-URI. The binding MUST be removed from its parent collection, identified by the Request-URI minus its trailing slash (if present) and final segment. Once a resource is unreachable by any URI mapping, the server MAY reclaim system resources associated with that resource. If DELETE removes a binding to a resource, but there remain URI mappings to that resource, the server MUST NOT reclaim system resources associated with the resource. Although allows a DELETE to be a non-atomic operation, the DELETE operation defined here is atomic. In particular, a DELETE on a hierarchy of resources is simply the removal of a binding to the collection identified by the Request-URI, and so is a single (and therefore atomic) operation. Section 8.6.1 of states that during DELETE processing, a server "MUST remove any URI for the resource identified by the Request-URI from collections which contain it as a member." Servers that support bindings MUST NOT follow this requirement.

As defined in Section 8.8 of , COPY causes the resource identified by the Request-URI to be duplicated, and makes the new resource accessible using the URI specified in the Destination header. Upon successful completion of a COPY, a new binding is created between the last path segment of the Destination header, and the destination resource. The new binding is added to its parent collection, identified by the Destination header minus its trailing slash (if present) and final segment. Figure 4 below shows an example: Suppose that a COPY is issued to URI 3 for resource R (which is also mapped to URI 1 and URI 2), with the Destination header set to URIX. After successful completion of the COPY operation, resource R is duplicated to create resource R', and a new binding has been created which creates at least the URI mapping between URIX and the new resource (although other URI mappings may also have been created).

URI 1 URI 2 URI 3 URIX | | | | | | | <---- URI Mappings ----> | | | | | +---------------------+ +------------------------+ | Resource R | | Resource R' | +---------------------+ +------------------------+

It might be thought that a COPY request with "Depth: 0" on a collection would duplicate its bindings, since bindings are part of the collection's state. This is not the case, however. The definition of Depth in makes it clear that a "Depth: 0" request does not apply to a collection's members. Consequently, a COPY with "Depth: 0" does not duplicate the bindings contained by the collection.

The MOVE method has the effect of creating a new binding to a resource (at the Destination), and removing an existing binding (at the Request- URI). The name of the new binding is the last path segment of the Destination header, and the new binding is added to its parent collection, identified by the Destination header minus its trailing slash (if present) and final segment. As an example, suppose that a MOVE is issued to URI 3 for resource R below (which is also mapped to URI 1 and URI 2), with the Destination header set to URIX. After successful completion of the MOVE operation, a new binding has been created which creates at least the URI mapping between URIX and resource R (although other URI mappings may also have been created). The binding corresponding to the final segment of URI 3 has been removed, which also causes the URI mapping between URI 3 and R to be removed.

>> Before Request: URI 1 URI 2 URI 3 | | | | | | <---- URI Mappings | | | +---------------------+ | Resource R | +---------------------+ >> After Request: URI 1 URI 2 URIX | | | | | | <---- URI Mappings | | | +---------------------+ | Resource R | +---------------------+

Although allows a MOVE on a collection to be a non-atomic operation, the MOVE operation defined here MUST be atomic. Even when the Request-URI identifies a collection, the MOVE operation involves only removing one binding to that collection and adding another. There are no operations on bindings to any of its children, so the case of MOVE on a collection is the same as the case of MOVE on a non-collection resource. Both are atomic.

This section describes the interaction of bindings with those HTTP methods not yet explicitly discussed. The semantics of the methods GET, HEAD, PUT, POST and OPTIONS are specified in . The semantics of PROPFIND, PROPPATCH, and MKCOL are specified in . For these methods, no new complexities are introduced by allowing explicit creation of multiple bindings to the same resource. When applied to static resources (that is, resources that are not CGI scripts, Active Server Pages, etc.), they obey the following rule: A method submitted through one URI mapping, on success, MUST produce the same results as the same method, with the same headers and entity body, submitted through any other URI mapping to the same resource. When applied to dynamic resources, it is not possible to state any such rule. For any method, a dynamic resource may be sensitive to the URI mapping used to access it. The resource may produce different results depending upon which URI mapping was used to submit the request. Nevertheless, servers MAY allow new bindings to dynamic resources to be created using BIND.

It is useful to have some way of determining whether two bindings are to the same resource. Two different resources might have identical contents and identical values for the properties defined in . Although the DAV:bindings property defined in Section 13.1 provides this information, it is an optional property. The REQUIRED DAV:resourceid property defined in Section 13.2 is a resource identifier, which MUST be unique across all resources for all time. If the values of DAV:resourceid returned by PROPFIND requests through two bindings are identical, the client can be assured that the two bindings are to the same resource. The DAV:resourceid property is created, and its value assigned, when the resource is created. The value of DAV:resourceid MUST NOT be changed. Even after the resource is no longer accessible through any URI, that value MUST NOT be reassigned to another resource's DAV:resourceid property. Any method that creates a new resource MUST assign a new, unique value to its DAV:resourceid property. For example, a PUT that creates a new resource must assign a new, unique value to its DAV:resourceid property. A COPY, since it creates a new resource at the Destination URI, must assign a new, unique value to its DAV:resourceid property. On the other hand, any method that affects an existing resource MUST NOT change the value of its DAV:resourceid property. For example, a PUT that updates an existing resource must not change the value of its DAV:resourceid property. A MOVE, since it does not create a new resource, but only changes the location of an existing resource, must not change the value of its DAV:resourceid property.

The value of DAV:resourceid is a URI and may use any URI scheme that guarantees the uniqueness of the value across all resources for all time. The resourceid URI scheme defined here is an example of an acceptable URI scheme. The resourceid URI scheme requires the use of the Universal Unique Identifier (UUID) mechanism, as described in . UUID generators may choose between two methods of creating the identifiers. They can either generate a new UUID for every identifier they create or they can create a single UUID and then add extension characters. If the second method is selected, then the program generating the extensions MUST guarantee that the same extension will never be used twice with the associated UUID. resourceid-URI = "resourceid:" UUID [Extension] ; The UUID production is the string representation of a UUID, as defined in . Note that white space (LWS) is not allowed between elements of this production. Extension = path ; path is defined in Section 3.3 of .

An OPTIONAL DAV:bindings property on a resource provides a list of the bindings that associate URI segments with that resource. If the DAV:bindings property exists on a given resource, it MUST contain a complete list of all bindings to that resource. A PROPFIND requesting DAV:bindings MUST return only those bindings that the client is authorized to see. By retrieving this property, a client can discover the bindings that point to the resource and the collections that contain bindings to the resource. Rationale: A number of scenarios require clients to navigate from a resource to the bindings that point to it, and to the collections that contain those bindings. This capability is particularly important for Document Management Systems. Their clients may need to determine, for any object in the DMS, what collections contain bindings to that object. This information can be used for upward navigation through a hierarchy or to discover related documents in other collections. Risks: When deciding whether to support the DAV:bindings property, server implementers / administrators should balance the benefits it provides against the cost of maintaining the property and the security risks enumerated in Sections 16.4 and 16.5.

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". When this status code is the top-level status code for the operation, it indicates that the entire operation failed. When this status code occurs inside a multistatus response, it indicates only that a loop is being terminated, but does not indicate failure of the operation as a whole. For example, consider a PROPFIND request on the following collection:

Coll-1 (bound to collection C) Foo (bound to resource R) Bar (bound to collection C)

>> Request: PROPFIND /Coll-1/ HTTP/1.1 Host: www.somehost.com Depth: infinity Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:propfind xmlns:D="DAV:"> <D:prop> <D:displayname/> </D:prop> </D:propfind>

>> Response: HTTP/1.1 207 Multi-Status Content-Type: text/xml; charset="utf-8" Content-Length: xxx <?xml version="1.0" encoding="utf-8" ?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>http://www.somehost.com/Coll-1/</D:href> <D:propstat> <D:prop> <D:displayname>Loop Demo</D:displayname> </D:prop> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://www.somehost.com/Coll-1/Foo</D:href> <D:propstat> <D:prop> <D:displayname>Bird Inventory</D:displayname> <</D:prop> <D:status>HTTP/1.1 200 OK</D:status> </D:propstat> </D:response> <D:response> <D:href>http://www.somehost.com/Coll-1/Bar</D:href> <D:propstat> <D:prop> <D:displayname/> </D:prop> <D:status>HTTP/1.1 506 Loop Detected</D:status> </D:propstat> </D:response> </D:multistatus>

The server is unable to create the requested binding because it would bind a segment in a collection on one server to a resource on a different server.

bindings DAV: Enables clients to discover, for any resource, what bindings point to it and what collections contain those bindings. This is an optional property. If present on a given resource, it is a read-only property, maintained by the server, and contains a complete list of all bindings to that resource. List of href / segment pairs for all of the bindings that associate URI segments with the resource. The href is an absolute URI for one URI mapping of the collection containing the binding. Since there may be multiple URI mappings for this collection, it is necessary to select one (preferably the URI mapping contained in the Request-URI of the BIND request) for use in the DAV:bindings property. The segment is the URI segment that identifies the binding within that collection.

<!ELEMENT bindings ((href, segment)*)>

resourceid DAV: Enables clients to determine whether two bindings are for the same resource. URI that is guaranteed unique across all resources for all time. It may be of the resourceid URI scheme defined in Section 10.1 or any other URI scheme that guarantees this uniqueness.

<!ELEMENT resourceid (href)>

segment DAV: The segment that names a binding, used in the DAV:bindings property. segment ; as defined in section 3.3 of .

<!ELEMENT segment (#PCDATA)>

Sections 9.1 and 15 of describe the use of compliance classes with the DAV header in responses to OPTIONS, to indicate which parts of the WebDAV Distributed Authoring protocol the resource supports. This specification defines an OPTIONAL extension to . It defines a new compliance class, called bindings, for use with the DAV header in responses to OPTIONS requests. If a resource does support bindings, its response to an OPTIONS request may indicate that it does, by listing the new BIND method as one it supports, and by listing the new bindings compliance class in the DAV header. When responding to an OPTIONS request, any type of resource can include bindings in the value of the DAV header. Doing so indicates that the server permits a binding at the request URI.

>> Request: OPTIONS /somecollection/someresource HTTP/1.1 HOST: somehost.org

>> Response: HTTP/1.1 200 OK Date: Tue, 20 Jan 1998 20:52:29 GMT Connection: close Accept-Ranges: none Allow: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE, MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, BIND Public: OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE, COPY, MOVE, MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK, BIND, MKREF, ORDERPATCH DAV: 1, 2, bindings

The DAV header in the response indicates that the resource /somecollection/someresource is level 1 and level 2 compliant, as defined in . In addition, /somecollection/someresource supports bindings. The Allow header indicates that BIND requests can be submitted to /somecollection/someresource. The Public header shows that other Request-URIs on the server support additional methods.

This section is provided to make WebDAV applications aware of the security implications of this protocol. All of the security considerations of HTTP/1.1 and the WebDAV Distributed Authoring Protocol specification also apply to this protocol specification. In addition, bindings introduce several new security concerns and increase the risk of some existing threats. These issues are detailed below.

In a context where cross-server bindings are supported, creating bindings on a trusted server may make it possible for a hostile agent to induce users to send private information to a target on a different server.

Although redirect loops were already possible in HTTP 1.1, the introduction of the BIND method creates a new avenue for clients to create loops accidentally or maliciously. If the binding and its target are on the same server, the server may be able to detect BIND requests that would create loops. Servers are required to detect loops that are caused by bindings to collections during the processing of any requests with "Depth: infinity".

Denial of service attacks were already possible by posting URLs that were intended for limited use at heavily used Web sites. The introduction of BIND creates a new avenue for similar denial of service attacks. If cross-server bindings are supported, clients can now create bindings at heavily used sites to target locations that were not designed for heavy usage.

If the DAV:bindings property is maintained on a resource, the owners of the bindings risk revealing private locations. The directory structures where bindings are located are available to anyone who has access to the DAV:bindings property on the resource. Moving a binding may reveal its new location to anyone with access to DAV:bindings on its resource.

If the server maintains the DAV:bindings property in response to bindings created in other administrative domains, it is exposed to hostile attempts to make it devote resources to adding bindings to the list.

This specification follows the practices of in encoding all human-readable content using XML and in the treatment of names. Consequently, this specification complies with the IETF Character Set Policy . WebDAV applications MUST support the character set tagging, character set encoding, and the language tagging functionality of the XML specification. This constraint ensures that the human-readable content of this specification complies with . As in , names in this specification fall into three categories: names of protocol elements such as methods and headers, names of XML elements, and names of properties. Naming of protocol elements follows the precedent of HTTP, using English names encoded in USASCII for methods and headers. The names of XML elements used in this specification are English names encoded in UTF-8. For error reporting, follows the convention of HTTP/1.1 status codes, including with each status code a short, English description of the code (e.g., 423 Locked). Internationalized applications will ignore this message, and display an appropriate message in the user's language and character set. This specification introduces no new strings that are displayed to users as part of normal, error-free operation of the protocol. For rationales for these decisions and advice for application implementors, see .

This document uses the namespaces defined by for properties and XML elements. All other IANA considerations mentioned in also apply to this document. In addition, this document defines the new resourceid URI Scheme in Section 10.1 and the new HTTP/1.1 status codes 506 and 507in Section 12.

To be supplied by the RFC Editor.

To be supplied by the RFC Editor.

This draft has benefited from thoughtful discussion by Jim Amsden, Peter Carlson, Steve Carter, Tyson Chihaya, Ken Coar, Ellis Cohen, Dan Connolly, Bruce Cragun, Spencer Dawkins, Mark Day, Rajiv Dulepet, David Durand, Roy Fielding, Yaron Goland, Fred Hitt, Alex Hopmann, James Hunt, Marcus Jager, Chris Kaler, Manoj Kasichainula, Rohit Khare, Daniel LaLiberte, Steve Martin, Larry Masinter, Jeff McAffer, Surendra Koduru Reddy, Max Rible, Sam Ruby, Bradley Sergeant, Nick Shelness, John Stracke, John Tigue, John Turner, Kevin Wiggen, and others.

University of California, Irvine, Information and Computer Science

Irvine CA 92697-3425 US +1 949 824 1715 fielding@ics.uci.edu

World Wide Web Consortium, MIT Laboratory for Computer Science

545 Technology Square Cambridge MA 02139 US +1 617 258 8682 jg@w3.org

Compaq Computer Corporation, Western Research Laboratory

250 University Avenue Palo Alto CA 94301 US mogul@wrl.dec.com

World Wide Web Consortium, MIT Laboratory for Computer Science

545 Technology Square Cambridge MA 02139 US +1 617 258 8682 frystyk@w3.org

Xerox Corporation

3333 Coyote Hill Road Palo Alto CA 94034 US masinter@parc.xerox.com

Microsoft Corporation

1 Microsoft Way Redmond WA 98052 US paulle@microsoft.com

World Wide Web Consortium, MIT Laboratory for Computer Science

545 Technology Square Cambridge MA 02139 US +1 617 258 8682 timbl@w3.org

The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as "HTTP/1.1", and is an update to RFC 2068. International Organization for Standardization

http://www.iso.ch

Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864 -

General keyword In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: 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 RFC 2119. Note that the force of these words is modified by the requirement level of the document in which they are used. UNINETT

P.O.Box 6883 Elgeseter N-7002 TRONDHEIM NORWAY +47 73 59 70 94 Harald.T.Alvestrand@uninett.no

Applications Internet Engineering Task Force character encoding World Wide Web Consortium

MIT Laboratory for Computer Science, NE43-356 545 Technology Square Cambridge MA 02139 +1(617)258-8682 timbl@w3.org

Department of Information and Computer Science

University of California, Irvine Irvine CA 92697-3425 +1(949)824-1715 fielding@ics.uci.edu

Xerox PARC

3333 Coyote Hill Road Palo Alto CA 94034 +1(415)812-4333 masinter@parc.xerox.com

Applications uniform resource URI A Uniform Resource Identifier (URI) is a compact string of characters for identifying an abstract or physical resource. This document defines the generic syntax of URI, including both absolute and relative forms, and guidelines for their use; it revises and replaces the generic definitions in RFC 1738 and RFC 1808. This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. This document does not define a generative grammar for URI; that task will be performed by the individual specifications of each URI scheme. This paper describes a "superset" of operations that can be applied to URI. It consists of both a grammar and a description of basic functionality for URI. To understand what is a valid URI, both the grammar and the associated description have to be studied. Some of the functionality described is not applicable to all URI schemes, and some operations are only possible when certain media types are retrieved using the URI, regardless of the scheme used. Microsoft Corporation

yarong@microsoft.com

Dept. Of Information and Computer Science, University of California, Irvine

ejw@ics.uci.edu

Netscape

asad@netscape.com

Novell

srcarter@novell.com

Novell

dcjensen@novell.com

World Wide Web Consortium

MIT Laboratory for Computer Science 545 Technology Square Cambridge MA 02139 US + 1 617 253 2613 + 1 617 258 5999 timbl@w3.org http://www.w3c.org

<!--============= XML Elements from Section 14 ================--> <!ELEMENT segment (#PCDATA)> <!--============= Property Elements from Section 13 ===========--> <!ELEMENT bindings ((href, segment)*)> <!ELEMENT resourceid (href)>