RFC 4324 on Calendar Access Protocol (CAP)

rfc-editor@rfc-editor.org Wed, 21 December 2005 19:12 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep9Nt-000375-Sc; Wed, 21 Dec 2005 14:12:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ep9Nr-000370-DK for ietf-announce@megatron.ietf.org; Wed, 21 Dec 2005 14:12:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03573 for <ietf-announce@ietf.org>; Wed, 21 Dec 2005 14:11:15 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ep9QX-0001tO-9Q for ietf-announce@ietf.org; Wed, 21 Dec 2005 14:15:05 -0500
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jBLJAhw00841; Wed, 21 Dec 2005 11:10:43 -0800 (PST)
Message-Id: <200512211910.jBLJAhw00841@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Wed, 21 Dec 2005 11:10:43 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4324 on Calendar Access Protocol (CAP)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc4324.txt"><ftp://ftp.isi.edu/in-notes/rfc4324.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce