[CalendarServer-changes] [5029] CalendarServer/trunk/doc/Extensions
source_changes at macosforge.org
source_changes at macosforge.org
Wed Feb 3 08:55:57 PST 2010
Revision: 5029
http://trac.macosforge.org/projects/calendarserver/changeset/5029
Author: cdaboo at apple.com
Date: 2010-02-03 08:55:57 -0800 (Wed, 03 Feb 2010)
Log Message:
-----------
Minor update.
Modified Paths:
--------------
CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt
CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml
Modified: CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt
===================================================================
--- CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt 2010-02-03 06:30:50 UTC (rev 5028)
+++ CalendarServer/trunk/doc/Extensions/caldav-privateevents.txt 2010-02-03 16:55:57 UTC (rev 5029)
@@ -3,11 +3,10 @@
Calendar Server Extension C. Daboo
Apple
- December 18, 2007
+ February 3, 2010
Private Calendar Components in CalDAV
- icalendar-privateevents-01
Abstract
@@ -34,7 +33,7 @@
4.2.2.1. Changing the X-CALENDARSERVER-ACCESS value . . . . 5
4.2.2.2. X-CALENDARSERVER-ACCESS set to PUBLIC . . . . . . 5
4.2.2.3. X-CALENDARSERVER-ACCESS set to PRIVATE . . . . . . 5
- 4.2.2.4. X-CALENDARSERVER-ACCESS set to CONIFDENTIAL . . . 6
+ 4.2.2.4. X-CALENDARSERVER-ACCESS set to CONFIDENTIAL . . . 6
4.2.2.5. X-CALENDARSERVER-ACCESS set to RESTRICTED . . . . 6
4.2.3. Changes to WebDAV Privileges when
X-CALENDARSERVER-ACCESS is used . . . . . . . . . . . 7
@@ -52,15 +51,16 @@
+
Daboo [Page 1]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
1. Introduction
Internet calendaring and scheduling standards are defined by
- iCalendar [RFC2445] and iTIP [RFC2446]. The CalDAV [RFC4791]
+ iCalendar [RFC5445] and iTIP [RFC5446]. The CalDAV [RFC4791]
standard defines a way to access calendar data stored on a server.
CalDAV uses WebDAV ACLs [RFC3744] to allow a calendar user to grant
rights to other users to see the calendar data stored on the server.
@@ -110,7 +110,7 @@
Daboo [Page 2]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
1. None right now.
@@ -166,7 +166,7 @@
Daboo [Page 3]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
store or when sent via an iTIP message. When used on a CalDAV
@@ -222,7 +222,7 @@
Daboo [Page 4]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
4.2.1.1. Example: Using OPTIONS for the Discovery of Private Event
@@ -278,12 +278,12 @@
Daboo [Page 5]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
indicated in the DAV:owner property on the calendar resource.
-4.2.2.4. X-CALENDARSERVER-ACCESS set to CONIFDENTIAL
+4.2.2.4. X-CALENDARSERVER-ACCESS set to CONFIDENTIAL
In addition to normal WebDAV access control, a calendar user
authorized as a principal that is not the DAV:owner of the calendar
@@ -334,7 +334,7 @@
Daboo [Page 6]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
+-----------+-------------------------------------------------------+
@@ -390,7 +390,7 @@
Daboo [Page 7]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
| CONFIDENTIAL | The DAV:write privilege MUST be denied to all |
@@ -446,7 +446,7 @@
Daboo [Page 8]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
| | REPORT - | Any CALDAV:calendar-data |
@@ -502,7 +502,7 @@
Daboo [Page 9]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
| | REPORT - | Normal ACLs apply. |
@@ -558,7 +558,7 @@
Daboo [Page 10]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
5. Security Considerations
@@ -604,9 +604,9 @@
7. Normative References
[I-D.desruisseaux-caldav-sched]
- Desruisseaux, B., "Scheduling Extensions to CalDAV",
- draft-desruisseaux-caldav-sched-03 (work in progress),
- January 2007.
+ Daboo, C. and B. Desruisseaux, "CalDAV Scheduling
+ Extensions to WebDAV", draft-desruisseaux-caldav-sched-08
+ (work in progress), August 2009.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
@@ -614,20 +614,11 @@
Daboo [Page 11]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
Requirement Levels", BCP 14, RFC 2119, March 1997.
- [RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and
- Scheduling Core Object Specification (iCalendar)",
- RFC 2445, November 1998.
-
- [RFC2446] Silverberg, S., Mansour, S., Dawson, F., and R. Hopson,
- "iCalendar Transport-Independent Interoperability Protocol
- (iTIP) Scheduling Events, BusyTime, To-dos and Journal
- Entries", RFC 2446, November 1998.
-
[RFC3744] Clemm, G., Reschke, J., Sedlar, E., and J. Whitehead, "Web
Distributed Authoring and Versioning (WebDAV)
Access Control Protocol", RFC 3744, May 2004.
@@ -636,15 +627,28 @@
"Calendaring Extensions to WebDAV (CalDAV)", RFC 4791,
March 2007.
+ [RFC5445] Watson, M., "Basic Forward Error Correction (FEC)
+ Schemes", RFC 5445, March 2009.
+ [RFC5446] Korhonen, J. and U. Nilsson, "Service Selection for Mobile
+ IPv4", RFC 5446, February 2009.
+
+
Appendix A. Acknowledgments
This specification is the result of discussions between the Apple
- calendar server and client teams.
+ calendar server and client teams. Also thanks to Filip Navara for
+ comments.
Appendix B. Change History
+ Changes since -01
+
+ 1. Fixed typo.
+
+ 2. Updated to new 5545 and 5546 specs.
+
Changes since -00
1. Added security text on how to deal with unrecognized values.
@@ -664,13 +668,9 @@
-
-
-
-
Daboo [Page 12]
- CalDAV Private Calendar Components December 2007
+ CalDAV Private Calendar Components February 2010
Author's Address
Modified: CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml
===================================================================
--- CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml 2010-02-03 06:30:50 UTC (rev 5028)
+++ CalendarServer/trunk/doc/Extensions/caldav-privateevents.xml 2010-02-03 16:55:57 UTC (rev 5029)
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM 'rfc2629.dtd' [
<!ENTITY rfc2119 PUBLIC '' 'bibxml/reference.RFC.2119.xml'>
-<!ENTITY rfc2445 PUBLIC '' 'bibxml/reference.RFC.2445.xml'>
-<!ENTITY rfc2446 PUBLIC '' 'bibxml/reference.RFC.2446.xml'>
<!ENTITY rfc3744 PUBLIC '' 'bibxml/reference.RFC.3744.xml'>
<!ENTITY rfc4791 PUBLIC '' 'bibxml/reference.RFC.4791.xml'>
+<!ENTITY rfc5445 PUBLIC '' 'bibxml/reference.RFC.5445.xml'>
+<!ENTITY rfc5446 PUBLIC '' 'bibxml/reference.RFC.5446.xml'>
<!ENTITY I-D.desruisseaux-caldav-sched PUBLIC '' 'bibxml3/reference.I-D.desruisseaux-caldav-sched.xml'>
]>
<?rfc toc="yes"?>
@@ -17,7 +17,7 @@
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc private="Calendar Server Extension"?>
-<rfc ipr="none" docName='icalendar-privateevents-01'>
+<rfc ipr="none" docName='icalendar-privateevents-02'>
<front>
<title abbrev="CalDAV Private Calendar Components">Private Calendar Components in CalDAV</title>
<author initials="C." surname="Daboo" fullname="Cyrus Daboo">
@@ -36,7 +36,7 @@
<uri>http://www.apple.com/</uri>
</address>
</author>
- <date year='2007'/>
+ <date />
<abstract>
<t>
This document defines an extension to CalDAV that enables a client to mark events with an access classification (e.g., "private") so that other calendar users have restricted rights to view the data in the calendar component.
@@ -46,7 +46,7 @@
<middle>
<section title='Introduction'>
<t>
- Internet calendaring and scheduling standards are defined by <xref target="RFC2445">iCalendar</xref> and <xref target="RFC2446">iTIP</xref>. The <xref target="RFC4791">CalDAV</xref> standard defines a way to access calendar data stored on a server. CalDAV uses <xref target="RFC3744">WebDAV ACLs</xref> to allow a calendar user to grant rights to other users to see the calendar data stored on the server. This is an "all or nothing" behavior, i.e. if another user is granted the DAV:read privilege to a calendar component, then that user can read all the calendar data in the calendar resource stored on the server.
+ Internet calendaring and scheduling standards are defined by <xref target="RFC5445">iCalendar</xref> and <xref target="RFC5446">iTIP</xref>. The <xref target="RFC4791">CalDAV</xref> standard defines a way to access calendar data stored on a server. CalDAV uses <xref target="RFC3744">WebDAV ACLs</xref> to allow a calendar user to grant rights to other users to see the calendar data stored on the server. This is an "all or nothing" behavior, i.e. if another user is granted the DAV:read privilege to a calendar component, then that user can read all the calendar data in the calendar resource stored on the server.
</t>
<t>
It is often the case that a calendar user wants to give "restricted" access to portions of the calendar data. e.g., allow another calendar user to see only the start and end times of an event, but not other information (such as summary, description, location, attendee list etc). There is currently no way to do that with CalDAV.
@@ -192,7 +192,7 @@
<t>There are no additional restrictions beyond normal WebDAV access control applied to the calendar resource for this access restriction. Note that in this case the server will explicitly set WebDAV ACLs to prevent access to the data by any principal other than the one indicated in the DAV:owner property on the calendar resource.
</t>
</section>
- <section title="X-CALENDARSERVER-ACCESS set to CONIFDENTIAL" anchor="confidential">
+ <section title="X-CALENDARSERVER-ACCESS set to CONFIDENTIAL" anchor="confidential">
<t>In addition to normal WebDAV access control, a calendar user authorized as a principal that is not the DAV:owner of the calendar resource can retrieve or match on only the following iCalendar properties (assuming these properties actually occur in the calendar object):
</t>
<texttable>
@@ -529,10 +529,10 @@
<back>
<references title='Normative References'>
&rfc2119;
- &rfc2445;
- &rfc2446;
&rfc3744;
&rfc4791;
+ &rfc5445;
+ &rfc5446;
&I-D.desruisseaux-caldav-sched;
</references>
<!--
@@ -541,10 +541,16 @@
-->
<section title='Acknowledgments'>
<t>
- This specification is the result of discussions between the Apple calendar server and client teams.
+ This specification is the result of discussions between the Apple calendar server and client teams. Also thanks to Filip Navara for comments.
</t>
</section>
<section title='Change History'>
+ <t>Changes since -01
+ <list style='numbers'>
+ <t>Fixed typo.</t>
+ <t>Updated to new 5545 and 5546 specs.</t>
+ </list>
+ </t>
<t>Changes since -00
<list style='numbers'>
<t>Added security text on how to deal with unrecognized values.</t>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20100203/65a82dc6/attachment-0001.html>
More information about the calendarserver-changes
mailing list