datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

WebDAV Bindings
draft-ietf-webdav-binding-protocol-02

Document type: Expired Internet-Draft (webdav WG)
Document stream: IETF
Last updated: 1999-12-22
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-webdav-binding-protocol

Abstract

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.

Authors

James Davis <davis@dri.cornell.edu>
John Crawford <J.S.Crawford@ukc.ac.uk>
Judith Slein <jslein@crt.xerox.com>
Charles Fay <cfay@filenet.com>
Geoffrey Clemm <geoffrey.clemm@rational.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)