[Fwd: I-D ACTION:draft-reschke-webdav-locking-04.txt]


I have submitted another version of my experimental stand-alone locking
protocol document.  Revision 04
have the changes described below:

E.4  Since draft-reschke-webdav-locking-03

    Close issues "import-rfc3253-stuff", "008_URI_URL",
    Reformat condition name descriptions.  Add mention of condition
    failure signalling to "Changes" appendix.  Start edit of header
    descriptions (Depth, Timeout) and LOCK creation description.  Open
    and close issue "3.2_lockdiscovery_depth".  Start work on intro.

(The HTML versions have all changes highlighted, so it's easy to see 
what actually has been changing between revisions since the "import" of 
text from RFC2518).

As usual, edits are ongoing on
The current issues list is at

The next step will be to integrate GULP into the description of write locks.

Feedback appreciated, Julian

-------- Original Message --------
From: - Wed Jun 30 01:30:23 2004
X-UIDL: e921bc2a83b93cd597b37a22a3b82b83
X-Mozilla-Status: 0001
X-Mozilla-Status2: 18000000
Return-Path: <i-d-announce-bounces@ietf.org>
X-Flags: 0000
Delivered-To: GMX delivery to julian.reschke@gmx.de
Received: (qmail 16493 invoked by uid 65534); 29 Jun 2004 20:32:29 -0000
Received: from megatron.ietf.org (EHLO megatron.ietf.org) ( 
  by mx0.gmx.net (mx005) with SMTP; 29 Jun 2004 22:32:29 +0200
Received: from localhost.localdomain ([] 
helo=megatron.ietf.org)	by megatron.ietf.org with esmtp (Exim 4.32)	id 
1BfOLY-0005Tc-I7; Tue, 29 Jun 2004 15:32:48 -0400
Received: from odin.ietf.org ([] helo=ietf.org)	by 
megatron.ietf.org with esmtp (Exim 4.32) id 1BfOHL-0004bd-ON	for 
i-d-announce@megatron.ietf.org; Tue, 29 Jun 2004 15:28:27 -0400
Received: from CNRI.Reston.VA.US (localhost [])	by ietf.org 
(8.9.1a/8.9.1a) with ESMTP id PAA11375	for <i-d-announce@ietf.org>; Tue, 
29 Jun 2004 15:28:26 -0400 (EDT)
Message-Id: <200406291928.PAA11375@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 29 Jun 2004 15:28:26 -0400
Subject: I-D ACTION:draft-reschke-webdav-locking-04.txt
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>, 
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Antispam: 0 (Mail was not recognized as spam)

A New Internet-Draft is available from the on-line Internet-Drafts 

	Title		: Web Distributed Authoring and Versioning (WebDAV) Locking Protocol
	Author(s)	: J. Reschke
	Filename	: draft-reschke-webdav-locking-04.txt
	Pages		: 48
	Date		: 2004-6-29
This document specifies a set of methods and headers ancillary to
    HTTP/1.1 (RFC2616) and Distributed Authoring and Versioning (WebDAV,
    RFC2518) for the management of resource locking (collision
    avoidance).  It updates those sections from RFC2518 that specify
    WebDAV's locking features.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

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-reschke-webdav-locking-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-reschke-webdav-locking-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

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

Received on Wednesday, 30 June 2004 03:19:50 UTC