IETF Calendar and Scheduling Working Committee

Board discussionSan Francisco 2/99

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

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

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

CalendarObject Model

Calendar

Event

To-do

Journal

ComponentProperties

Timezone

CalendarProperties

FreeBusy

AlarmAlarm

CalendarComponents

CalendarMail Transport Model

CalendarUser (CU)

Calendar UserAgent (CUA)

Mail UserAgent (MUA)

Mail TransferAgent (MTA)

Transport

CalendarUser (CU)

Calendar ExchangeProtocol (CXP) Calendar User

Agent (CUA)

Mail UserAgent (MUA)

Mail TransferAgent (MTA)

Transport

CalendarSystem Model

CalendarUser (CU)

Calendar UserAgent (CUA)

CalendarUser (CU)

CalendarExchangeProtocol

Calendar

Calendar

CalendarService

Aggregate CUA

CalendarAccessProtocol(CAP)

CAP

CalendarExchangeMedium

Calendar User Agent/Calendar-Boundary Interactions

CUA-1 creates an entry in a calendar that it owns (doesn’t 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

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

Graphic representation

Com pany Acalendar store

Com pany Bcalendar store

IR IP - a llowsCalendar store to

ta lk direct tocalendar store

M ary and Bob want to set up a meeting. Each one uses ad ifferent ca lendar product. They a lso want to invite o ther groupsthat may use d ifferent types of ca lendar products or no ca lendar

product a t a ll. M ary in itia tes the process.

Company Bcalendar store

Various othercalendar

stores

Subselect and

enter title hereCalendar Client A

uses ICalendarbased syntax

M ary atCompany

A

Subselect and entertitle here

Calendar Client Buses M IME based

syntax

Bob atCompany

B

John has nocalendarproduct