Re: CalDAV draft Informal Last-Call

Quick update.  We will submit the CalDAV draft for Last Call when
Internet-Draft posting will resume after the next IETF meeting.
That will give more time to people to review the draft.

Cheers,
Bernard

Bernard Desruisseaux wrote:
> 
> We submitted CalDAV draft -10 to the IETF yesterday. The draft has
> not been officially announced yet, but it is already available for
> you to review at the following URL:
> 
> http://ietf.webdav.org/caldav/draft-dusseault-caldav-10.txt
> 
> We would like to submit the CalDAV draft for Last Call in time for
> the 65th IETF Meeting in Dallas (i.e., really soon!). Before we do
> so, we would like to get as much feedback as possible from the
> participants of the "ietf-caldav" mailing list as well as from the
> members of the WebDAV and Calsify Working Groups.
> 
> Once officially announced the draft should be available at:
> 
>   http://www.ietf.org/internet-drafts/draft-dusseault-caldav-10.txt
> 
> Previous versions of the draft are available at:
> 
>   http://ietfreport.isoc.org/idref/draft-dusseault-caldav/
> 
> Discussion on CalDAV is taking place on the "ietf-caldav" mailing list:
> 
>   mailto:ietf-caldav@osafoundation.org
> 
> which is archived at:
> 
>   http://lists.osafoundation.org/mailman/listinfo/ietf-caldav
> 
> Reports on the 4 CalDAV Interoperability Events organized by the
> Calendaring and Scheduling Consortium (CalConnect) can be found at:
> 
>   http://www.calconnect.org/ioppast.html
> 
> Finally, additional information on CalDAV can also be found at:
> 
>   http://ietf.webdav.org/caldav/
> 
> Please review draft -10 and send us feedback/questions/comments.
> 
> Thanks for you help!
> 
> Cheers,
> Bernard
> 
> -- 
> 
> C.1.  Changes in -10
> 
>    a.  Added new section about support for X- items when storing data.
> 
>    b.  Added new precondition to allow servers to reject queries on
>        unsupported X- items, and a new example.
> 
>    c.  Added new text about always supporting X- in calendar-data.
> 
>    d.  Created new section for PUT, COPY and MOVE preconditions.
> 
>    e.  Report examples re-done with full listing of calendar data in
>        Appendix.
> 
>    f.  Removed description of using UID, SUMMARY etc as resource name.
> 
>    g.  Indicate that calendar object resource may contain only
>        overridden components.
> 
>    h.  Add security consideration about not expose details in resource
>        names.
> 
>    i.  Add constraint that free-busy-query can only be run on a
>        collection.
> 
>    j.  Add preconditions for calendar-timezone property/elements in
>        MKCALENDAR, PROPPATCH and calendar-query REPORT.
> 
>    k.  Fix principal-match example.
> 
> 
>