[caldav] Fwd: Protocol Action: 'CalDAV Scheduling Extensions to WebDAV' to Proposed Standard (draft-desruisseaux-caldav-sched-12.txt)

Bernard Desruisseaux <bernard.desruisseaux@oracle.com> Mon, 16 April 2012 18:03 UTC

Return-Path: <bernard.desruisseaux@oracle.com>
X-Original-To: caldav@ietfa.amsl.com
Delivered-To: caldav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F72F21F8693 for <caldav@ietfa.amsl.com>; Mon, 16 Apr 2012 11:03:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WD6PD23raMXs for <caldav@ietfa.amsl.com>; Mon, 16 Apr 2012 11:03:56 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id 051BE21F8649 for <caldav@ietf.org>; Mon, 16 Apr 2012 11:03:55 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q3GI3soC005329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 16 Apr 2012 18:03:55 GMT
Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q3GI3rCI010425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Apr 2012 18:03:54 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3GI3rlM026885; Mon, 16 Apr 2012 13:03:53 -0500
Received: from [10.191.112.178] (/10.191.112.178) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 16 Apr 2012 11:03:52 -0700
Message-ID: <4F8C5F03.4090104@oracle.com>
Date: Mon, 16 Apr 2012 23:33:47 +0530
From: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: ietf-caldav@osafoundation.org, IETF CalDAV <caldav@ietf.org>
References: <20120416171010.14008.4530.idtracker@ietfa.amsl.com>
In-Reply-To: <20120416171010.14008.4530.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20120416171010.14008.4530.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------040802010004080801060002"
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
X-CT-RefId: str=0001.0A090207.4F8C5F0B.0054,ss=1,re=0.000,fgs=0
Subject: [caldav] Fwd: Protocol Action: 'CalDAV Scheduling Extensions to WebDAV' to Proposed Standard (draft-desruisseaux-caldav-sched-12.txt)
X-BeenThere: caldav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <caldav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/caldav>, <mailto:caldav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/caldav>
List-Post: <mailto:caldav@ietf.org>
List-Help: <mailto:caldav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/caldav>, <mailto:caldav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Apr 2012 18:03:58 -0000

FYI

-------- Original Message --------
Subject: 	Protocol Action: 'CalDAV Scheduling Extensions to WebDAV' to 
Proposed Standard (draft-desruisseaux-caldav-sched-12.txt)
Date: 	Mon, 16 Apr 2012 10:10:10 -0700
From: 	The IESG <iesg-secretary@ietf.org>;
To: 	IETF-Announce <ietf-announce@ietf.org>;
CC: 	RFC Editor <rfc-editor@rfc-editor.org>;



The IESG has approved the following document:
- 'CalDAV Scheduling Extensions to WebDAV'
   (draft-desruisseaux-caldav-sched-12.txt) as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Barry Leiba.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-desruisseaux-caldav-sched/




Technical Summary
     Scheduling is a core function of a calendaring system and this
     extension defines the process by which CalDAV clients and servers
     can use iCalendar (RFC 5545) and iTIP (RFC 5546) to accomplish that
     in a manner that ensures data consistency between organizer and
     attendee views of a scheduled event.

Working Group Summary
     Discussion has taken place on the CalDAV mailing list over a long
     period of time as the document has evolved. There has been an
     "informal" last call on the document. In addition, there are now
     several implementations of the protocol in various client/server
     CalDAV products. Further discussions and interoperability testing
     has occurred in the Calendaring and Scheduling Consortium.

Document Quality
     This document has been discussed and reviewed on the CalDAV
     (<ietf-caldav@osafoundation.org>) mailing list. The original draft
     was developed in 2006, with a substantial re-working in 2007.
     Experienced calendar/CalDAV developers have been involved in its
     development, and new implementors have appeared over time too. There
     are already many deployed implementations of this protocol (many
     documented here http://caldav.calconnect.org/implementations.html),
     with feedback from those deployments having been incorporated into
     the specification. The specification has been the subject of regular
     interoperability tests at Calendaring and Scheduling Consortium
     events.

Personnel
    The Document Shepherd is Mike Douglass.
    The Responsible Area Director is Peter Saint-Andre.

RFC Editor Note
     Introduction, last paragraph:
     OLD
         Discussion of this Internet-Draft is taking place on the mailing
         lists at<https://www.ietf.org/mailman/listinfo/caldav>  and
         <http://lists.osafoundation.org/pipermail/ietf-caldav>;.
     NEW
         This specification has been under development for a number of years,
         and most current implementations of CalDAV support it.  With the
         publication of this document, it is expected that all new CalDAV
         implementations will support it by default.  Interoperability tests
         have been performed regularly.  Significant issues with incompatible
         CalDAV implementations are not anticipated.