IETF Calendar and Scheduling Working Committee

1
IETF Calendar and Scheduling Working Committee

• Board discussion
• San Francisco 2/99

2
Model

• Calendar is associated with a calendar user (CU)
• Calendar is a collection of calendar properties
  and calendar entries
• Calendar properties are attributes associated
  with the calendar as a whole
• Entries are a collection of properties associated
  with a date
• Entries examples events, to-dos, journals
• Property is a named value

3
Calendar User (CU)

• An individual, group, resource or room
  addressable in a calendar domain
• May be represented by a Calendar User Agent (CUA)
• CU may add, delete, modify (ie, manipulate)
  calendar properties or entries (ie, calendar
  content) within its own calendar..subject to
  access control
• CU may manipulate calendar content associated
  with another calendar user..subject to the access
  control of the other calendar

4
Property

• A named value
• Strongly typed
• Maybe further qualified by property parameters
• May be multi-valued
• May have multiple instances
• May be logically grouped
• Calendar and component specific

5
CalendarObject Model
Calendar
Component Properties
Calendar Components
To-do
Calendar Properties
Event
Alarm
Alarm
Journal
Timezone
FreeBusy
6
CalendarMail Transport Model
Calendar User (CU)
Calendar User (CU)
Calendar Exchange Protocol (CXP)
7
CalendarSystem Model
Calendar User (CU)
Calendar User Agent (CUA)
Calendar Exchange Protocol
Calendar
Calendar Access Protocol (CAP)
Calendar
Calendar Exchange Medium
Calendar Service
CAP
Calendar User (CU)
Aggregate CUA
8
Calendar User Agent/Calendar-Boundary Interactions

• CUA-1 creates an entry in a calendar that it owns
  (doesnt involve CUA, CXP)
• CUA-1 creates an entry in own calendar and
  requests a copy be created in one or more other
  CUAs calendar called a group scheduled entry
  (e.g., EVENT-REQUEST)
• CUA-1 can make updates to a group scheduled entry
  that it owns (e.g., EVENT-REPLACE, EVENT-CANCEL,
  EVENT-DELEGATE) that will require interactions
  with CUA-2..CUA-n
• CUA-2 can make certain updates to a group
  scheduled entry that it does not own that will
  require interaction with CUA-1 (e.g.,
  EVENT-REPLY, EVENT-COUNTER, EVENT-DELEGATE)
• CUA-2 can make other updates to group scheduled
  entry that it does not own that will not require
  interaction with CUA-1

9
Other Protocols in use with the CAP protocol

• IMIP
• Icalendar Messaging-based Interoperability
  protocol
• to send calendars as a message over email
• IRIP
• Internet Real-Time Interoperability Protocol
• Allow calendar stores to talk direct to other
  calendar stores, real time
• ITIP
• iCalendar Transport-Independent Interoperability
  Protocol
• added semantics for group scheduling methods

10
Graphic representation