Julian Reschke | 2 Jul 18:12 2008
Picon
Picon

getting WebDAV SEARCH ready for the IESG


Hi,

we recently made some progress on getting WebDAV SEARCH ready for 
publication.

We received some feedback from Chris Newman, and the latest edits on the 
draft 
(<http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html>,

<http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest-from-previous.diff.html>) 
take those into account.

Unless there's new feedback, I'm planning to submit this as draft 16, 
which, if all goes well, will then by last called.

Feedback appreciated,

Julian

Julian Reschke | 7 Jul 18:19 2008
Picon
Picon

Re: New Version Notification for draft-reschke-webdav-search-16


Hi,

I have submitted a new version of the SEARCH draft, containing editorial 
fixes and clarifications, as recently discussed on the DASL mailing list.

The plan is to get this draft last-called.

BR, Julian

IETF I-D Submission Tool wrote:
> A new version of I-D, draft-reschke-webdav-search-16.txt has been successfuly submitted by Julian
Reschke and posted to the IETF repository.
> 
> Filename:	 draft-reschke-webdav-search
> Revision:	 16
> Title:		 Web Distributed Authoring and Versioning (WebDAV) SEARCH
> Creation_date:	 2008-07-07
> WG ID:		 Independent Submission
> Number_of_pages: 62
> 
> Abstract:
> This document specifies a set of methods, headers, properties and
> content-types composing WebDAV SEARCH, an application of the HTTP/1.1
> protocol to efficiently search for DAV resources based upon a set of
> client-supplied criteria.Editorial Note (To be removed by RFC Editor before publication)
> 
> Please send comments to the Distributed Authoring and Versioning
> (WebDAV) DASL mailing list at <mailto:www-webdav-dasl <at> w3.org>, which
> may be joined by sending a message with subject "subscribe" to
(Continue reading)

Julian Reschke | 14 Jul 21:14 2008
Picon
Picon

Re: Last Call: draft-reschke-webdav-search (Web Distributed Authoring and Versioning (WebDAV) SEARCH) to Proposed Standard


(FYI)

The IESG wrote:
> The IESG has received a request from an individual submitter to consider 
> the following document:
> 
> - 'Web Distributed Authoring and Versioning (WebDAV) SEARCH '
>    <draft-reschke-webdav-search-17.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf <at> ietf.org mailing lists by 2008-08-11. Exceptionally, 
> comments may be sent to iesg <at> ietf.org instead. In either case, please 
> retain the beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-reschke-webdav-search-17.txt
> 
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=8611&rfc_flag=0
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

Julian Reschke | 20 Jul 14:37 2008
Picon
Picon

Dublin Meeting: discuss future WebDAV related work?


Hi,

(cross-posted to vcarddav, webdav-acl and webdav mailing lists...)

It might be interesting to discuss a few strictly WebDAV related topics 
in Dublin. As there's no posted agenda for vcarddav, I was wondering 
whether it would make sense to gather people interested in this for a 
separate discussion.

Potential topics:

(1) Extended MKCOL (as proposed by Cyrus in 
<http://tools.ietf.org/html/draft-ietf-vcarddav-webdav-mkcol-00>)

(2) Current principal property for WebDAV ACL (W. Sanchez: 
<http://tools.ietf.org/html/draft-sanchez-webdav-current-principal-01>, 
already in the hands of the IESG)

(3) Synchronization (as proposed by Cyrus in 
<http://tools.ietf.org/html/draft-daboo-webdav-sync-00>)

(4) Making PROPFIND + friends more powerful (my proposal in 
<http://greenbytes.de/tech/webdav/draft-reschke-http-get-location-01.html>)

(5) RFC3744bis:

   (a) incorporating errata 
(<http://greenbytes.de/tech/webdav/draft-reschke-rfc3744bis-issues.html>, 
<http://greenbytes.de/tech/webdav/draft-reschke-rfc3744bis-latest.html>)
(Continue reading)

Werner Baumann | 20 Jul 18:32 2008
Picon

clandestine move of draft-daboo-webdav-mkcol


Correct me if I'm wrong:

2007-11-12 C. Daboo posted 
<http://tools.ietf.org/html/draft-daboo-webdav-mkcol-00> and announced 
it on <w3c-dist-auth <at> w3.org>

 From 2007-11-12 to 2007-12-01 four people (including the author of the 
draft) posted ten contributions to the discussion. There was no 
consensus. The latest contribution from the author dates 2007-11-19.

There was no further public discussion about that draft.

Exception:
<http://lists.w3.org/Archives/Public/w3c-dist-auth/2008AprJun/0011.html> 
refers to this draft and got no answer from the author of the draft.

2008-05-14 the draft expired.

2008-05-14, the same day, the draft was recycled (with small changes) as 
<http://tools.ietf.org/html/draft-ietf-vcarddav-webdav-mkcol-00>.

The recycled draft is assigned to Vcarddav working group, though the 
draft claims to be *not* specific to any WebDAV-extension.

The recycled draft was not announced on <w3c-dist-auth <at> w3.org> nor on 
<vcarddav <at> ietf.org>.

There was no announcement of an intended move on <w3c-dist-auth <at> w3.org>. 
But obviously this move was intended (posting it with a new name at the 
(Continue reading)

Cyrus Daboo | 20 Jul 18:53 2008

Re: clandestine move of draft-daboo-webdav-mkcol


Hi Werner,

--On July 20, 2008 6:32:21 PM +0200 Werner Baumann 
<werner.baumann <at> onlinehome.de> wrote:

> 2007-11-12 C. Daboo posted
> <http://tools.ietf.org/html/draft-daboo-webdav-mkcol-00> and announced it
> on <w3c-dist-auth <at> w3.org>
>
>  From 2007-11-12 to 2007-12-01 four people (including the author of the
> draft) posted ten contributions to the discussion. There was no
> consensus. The latest contribution from the author dates 2007-11-19.
>

Sorry it looks like a post to w3c dist did not happen when the draft was 
moved over to the IETF vcarddav working group which agreed back in March to 
adopt this document as part of its charter. That was my fault - an 
oversight not an attempt to be sneaky.

In any case, discussion of this draft is still open. The recent update did 
address some of the comments made earlier.

So why don't we restart debate on this. If you want to post new comments or 
forward your original comments back to this list and the vcarddav list 
(<mailto:vcarddav <at> ietf.org>), please do so and we can move forward.

--

-- 
Cyrus Daboo

(Continue reading)

M.Jung | 21 Jul 13:07 2008
Picon

AW: Dublin Meeting: discuss future WebDAV related work?


Hi,

When we find a timeslot on Monday I also like to present and discuss a transaction model for WebDAV using
DeltaV. 

Is Monday 1.00 p.m. ok for everybody?

Cheers, 
Martin

-----Urspr√ľngliche Nachricht-----
Von: w3c-dist-auth-request <at> w3.org [mailto:w3c-dist-auth-request <at> w3.org] Im Auftrag von Julian Reschke
Gesendet: Sonntag, 20. Juli 2008 14:37
An: vcarddav <at> ietf.org; WebDAV; acl <at> webdav.org
Betreff: Dublin Meeting: discuss future WebDAV related work?

Hi,

(cross-posted to vcarddav, webdav-acl and webdav mailing lists...)

It might be interesting to discuss a few strictly WebDAV related topics 
in Dublin. As there's no posted agenda for vcarddav, I was wondering 
whether it would make sense to gather people interested in this for a 
separate discussion.

Potential topics:

(1) Extended MKCOL (as proposed by Cyrus in 
<http://tools.ietf.org/html/draft-ietf-vcarddav-webdav-mkcol-00>)
(Continue reading)

Julian Reschke | 21 Jul 13:19 2008
Picon
Picon

Re: AW: Dublin Meeting: discuss future WebDAV related work?


M.Jung <at> dlr.de wrote:
> Hi,
> 
> When we find a timeslot on Monday I also like to present and discuss a transaction model for WebDAV using
DeltaV. 
> 
> Is Monday 1.00 p.m. ok for everybody?
> 
> Cheers, 
> Martin

Monday 1pm would work for me.

NOTE: keep in mind that this is not a WG meeting, nor a BOF. We probably 
will not even have a meeting room, so presentations are likely to be a 
problem.

BR, Julian

Julian Reschke | 22 Jul 15:11 2008
Picon
Picon

Re: Last Call: draft-sanchez-webdav-current-principal (WebDAV Current Principal Extension) to Proposed Standard


(FYI)

The IESG wrote:
> The IESG has received a request from an individual submitter to consider 
> the following document:
> 
> - 'WebDAV Current Principal Extension '
>    <draft-sanchez-webdav-current-principal-01.txt> as a Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send substantive comments to the
> ietf <at> ietf.org mailing lists by 2008-08-19. Exceptionally, 
> comments may be sent to iesg <at> ietf.org instead. In either case, please 
> retain the beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-sanchez-webdav-current-principal-01.txt
> 
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17246&rfc_flag=0
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
> 

(Continue reading)

Julian Reschke | 25 Jul 15:07 2008
Picon
Picon

Last Call comments on draft-sanchez-webdav-current-principal-01

Hi,

this is a good proposal and I support publication as a Proposed Standard.

Below are some comments, mostly editorial:

> Abstract
> 
>    This specification defines a new WebDAV property that allows clients
>    to quickly determine the principal corresponding to the current
>    authenticated user.

Nit: Expand WebDAV acronym on first use.

>    Some clients have a need to determine the [RFC3744] principal that a
>    server is associating with the currently authenticated HTTP user.
>    While [RFC3744] defines a DAV:current-user-privilege-set property for
>    retrieving the privileges granted to that principal, there is no
>    recommended way to do identify the principal in question, which is
>    necessary to perform other useful operations.  For example, a client
>    may wish to determine which groups the current user is a member of,
>    or modify a property of the principal resource associated with the
>    current user.

Nit: say "WebDAV ACL" instead of "[RFC3744]" most of the time.

>    The DAV:principal-match REPORT provides some useful functionality,
>    but there are common situations where the results from that query can
>    be ambiguous (e.g. not only is an individual user principal returned,
>    but also every group principal that the user is a member of, and
(Continue reading)


Gmane