[Ietf-caldav] [Fwd: RFC 4324 on Calendar Access Protocol (CAP)]
Doug Royer <Doug@Royer.com> Wed, 21 December 2005 20:44 UTC
Return-Path: <Doug@Royer.com>
X-Original-To: ietf-caldav@osafoundation.org
Delivered-To: ietf-caldav@osafoundation.org
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by leilani.osafoundation.org (Postfix) with ESMTP id 6332E7F727; Wed, 21 Dec 2005 12:44:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 995331422F1; Wed, 21 Dec 2005 12:46:24 -0800 (PST)
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17679-05; Wed, 21 Dec 2005 12:46:24 -0800 (PST)
Received: from S2.cableone.net (s2.cableone.net [24.116.0.228]) by laweleka.osafoundation.org (Postfix) with ESMTP id EE1631422EF; Wed, 21 Dec 2005 12:46:23 -0800 (PST)
Received: from [192.168.168.10] (unverified [24.119.163.152]) by S2.cableone.net (CableOne SMTP Service S2) with ESMTP id 39844119 for multiple; Wed, 21 Dec 2005 13:04:05 -0700
Message-ID: <43A9B047.8020807@Royer.com>
Date: Wed, 21 Dec 2005 12:43:03 -0700
From: Doug Royer <Doug@Royer.com>
Organization: IntelliCal.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>, CalDAV DevList <ietf-caldav@osafoundation.org>, Calsify <ietf-calsify@osafoundation.org>, www-rdf-calendar@w3.org
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms070604030705000102070002"
X-SpamDetect: *: 1.250000 NakedCR=2.0,Aspam=-0.8
X-NakedCr: Body contained naked cr characters
X-NotAscii: charset=utf-8;
X-IP-stats: Incoming Outgoing Last 0, First 1, in=6, out=6, spam=0 Known=true
X-External-IP: 24.119.163.152
X-Abuse-Info: Send abuse complaints to abuse@cableone.net
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
X-Spam-Status: No, hits=0.0 tagged_above=-50.0 required=4.0 tests=
X-Spam-Level:
Subject: [Ietf-caldav] [Fwd: RFC 4324 on Calendar Access Protocol (CAP)]
X-BeenThere: ietf-caldav@osafoundation.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "ietf-calendar@imc.org" <ietf-calendar@imc.org>
List-Id: Discussions on Calendar Access protocol based on WebDAV <ietf-caldav.osafoundation.org>
List-Unsubscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=unsubscribe>
List-Archive: <http://lists.osafoundation.org/pipermail/ietf-caldav>
List-Post: <mailto:ietf-caldav@osafoundation.org>
List-Help: <mailto:ietf-caldav-request@osafoundation.org?subject=help>
List-Subscribe: <http://lists.osafoundation.org/mailman/listinfo/ietf-caldav>, <mailto:ietf-caldav-request@osafoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2005 20:44:55 -0000
CAP is out !! Thanks EVERYONE for their help!! -------- Original Message -------- Subject: RFC 4324 on Calendar Access Protocol (CAP) Date: Wed, 21 Dec 2005 11:10:43 -0800 From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org CC: rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 4324 Title: Calendar Access Protocol (CAP) Author(s): D. Royer, G. Babics, S. Mansour Status: Experimental Date: December 2005 Mailbox: Doug@IntelliCal.com, george.babics@oracle.com, smansour@ebay.com Pages: 131 Characters: 254638 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-royer-calsch-cap-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc4324.txt The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. ... -- Doug Royer | http://INET-Consulting.com -------------------------------|----------------------------- We Do Standards - You Need Standards