RE: Last Call: draft-ietf-webdav-rfc2518bis (HTTP Extensions for Distributed Authoring - WebDAV) to Proposed Standard

Ted Hardie <hardie@qualcomm.com> Fri, 19 January 2007 22:17 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H822o-0003Cs-VV; Fri, 19 Jan 2007 17:17:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H822o-0003Cn-5x for ietf@ietf.org; Fri, 19 Jan 2007 17:17:10 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H822l-0003OI-QB for ietf@ietf.org; Fri, 19 Jan 2007 17:17:10 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l0JMGUDV019080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Jan 2007 14:16:30 -0800
Received: from [129.46.225.123] (carbuncle.qualcomm.com [129.46.225.123]) by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l0JMGS1U021811; Fri, 19 Jan 2007 14:16:28 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06240603c1d6eef6b9d6@[129.46.225.123]>
In-Reply-To: <03E7D3E231BB7B4A915A6581D4296CC6035FAD4E@NSNOVPS00411.nacio.xythos.com>
References: <03E7D3E231BB7B4A915A6581D4296CC6035FAD4E@NSNOVPS00411.nacio.xythos.com>
Date: Fri, 19 Jan 2007 14:16:26 -0800
To: Kevin Wiggen <kwiggen@xythos.com>, Cullen Jennings <fluffy@cisco.com>, Manfred Baedke <manfred.baedke@greenbytes.de>, Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: ietf@ietf.org, WebDav <w3c-dist-auth@w3.org>
Subject: RE: Last Call: draft-ietf-webdav-rfc2518bis (HTTP Extensions for Distributed Authoring - WebDAV) to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

At 1:36 PM -0800 1/19/07, Kevin Wiggen wrote:
>I think what the spec needs is some love and attention.  If enough of us (and I will volunteer to READ and COMMENT) spend time on this, I think we can come to some sort of resolution.  I would hate to see the work done by the working group, Geoff, Julian, Lisa, etc go to waste.
 
I would also hate to see the work of this working group go to waste.  But I do not
believe that an additional two months, starting with a document that is not
up to date or the product of working group discussion, is at all a practical
time estimate.  As its Area Advisor, I gave this working group a six month
time line to finish its work eighteen months ago.  The last three months of
that period saw more significant activity than the working group had had
in the previous year.  Close to the deadline, Cullen asked that the WG be
extended as there were a few final issues that needed resolution. 

We are now almost a year on from that point.  Suggesting that an additional
two months would resolve things is, bluntly, completely contrary to the
experience of this WG. 

The first draft of this document was issued  *five years ago*.  If it is better
than 2518, it is time to push it out the door and making a new line in the sand. 
Too much of what to do with webdav is now "lore" in the heads of the
current implementors and unavailable without sifting through the WG
archives.  I believe getting this document out will help, even if it does not solve
the problem completely or meet its original goal (to get to Draft Standard).

That doesn't preclude there ever being a 2518ter or a Draft Standard here.
But with the current inputs, we are well past the point of diminishing returns.
Getting this document out as a Proposed Standard seems to me, both personally
and as the working group's area advisor, the best balance of retaining the work
that has been done and setting the stage for eventual further work.

				Ted Hardie



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf