W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2003

RE: I-D ACTION:draft-ietf-webdav-redirectref-protocol-04.txt

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 12 Sep 2003 10:03:12 +0200
To: <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIECDIHAA.julian.reschke@gmx.de>


One note regarding the draft progress: I'm still resolving editorial issues
raised during the "last call" in 2000. This draft hasn't got the
dependencies on the BIND spec anymore. The next steps will be

- to clarify that redirect refs do not have (authorable) content, and
- to replace MKRESOURCE by a more specific method.



<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Thursday, September 11, 2003 3:19 PM
> To: IETF-Announce:
> Cc: w3c-dist-auth@w3.org
> Subject: I-D ACTION:draft-ietf-webdav-redirectref-protocol-04.txt
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
> This draft is a work item of the WWW Distributed Authoring and
> Versioning Working Group of the IETF.
> 	Title		: WebDAV Redirect Reference Resources
> 	Author(s)	: J. Slein, et. al.
> 	Filename	: draft-ietf-webdav-redirectref-protocol-04.txt
> 	Pages		: 66
> 	Date		: 2003-9-10
> 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 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.
> The related specification [B], 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.
> Distribution of this document is unlimited. Please send comments to
> the Distributed Authoring and Versioning (WebDAV) working group at
> w3c-dist-auth@w3.org [1], which may be joined by sending a message
> with subject 'subscribe' to w3c-dist-auth-request@w3.org [2].
> Discussions of the WEBDAV working group are archived at URL:

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-webdav-redirectref-protocol-04.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-ietf-webdav-redirectref-protocol-04.txt".

NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Received on Friday, 12 September 2003 04:06:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:28 UTC