• This presentation is derived from the Technology Preview material

• Names and some technical details have been removed in accordance with CalConnect rules involving in-progress work

• This is a public document and may be quoted and distributed in accordance with CalConnect policies

CalConnect members have produced a Technical Demonstration of key calendaring and scheduling technologies being developed by CalConnect.

This serves as a technology “preview” only and does not in any way represent final protocols or products that may or may not ship.

This is a follow-up to the demo at Roundtable X (September 2007).

Our goal is to solicit feedback from members and invited guests on the presentation itself as well as the technologies being demonstrated.

We also hope to show how CalConnect is successfully achieving its goal of improving calendaring and scheduling standards.

Today we will demonstrate:

• CalDAV Scheduling

• Realtime Internet Scheduling

• Internet freebusy lookups using freebusy URLs

Each presentation will consist of:

• Introductory slides

• Live demonstration

CalDAV Scheduling:

• The CalDAV access protocol (RFC4791) is based on WebDAV and iCalendar standards

• In the CalDAV scheduling specification (still a draft), users on the same server system only schedule with each other

• There are several server and client implementations available

Realtime Internet Scheduling:

• Allows scheduling between users on different server systems (e.g. between organizations)

• The protocol uses HTTP to transport iCalendar scheduling messages

• We will be demonstrating the basic exchange of scheduling messages

• The security and discovery pieces are still to do (TC-REALTIME)

Freebusy URL:

• This is a way to do simple exchange and publishing of freebusy information

• TC-FREEBUSY is working on a specification

• It uses simple HTTP GET/PUT operations with discoverability

How it works:

• Several users on one CalDAV server (can be using different clients) schedule with each other

• One user is the “Organizer”, others are “Attendees”

One is the Organizer, others are Attendees. Each stores their calendars on the Server.

There are two parts to scheduling:

1. Freebusy lookup

2. Sending invitations and receiving replies

Freebusy results are returned immediately.

Invitation replies are sent only after users inspect and accept or decline.

Each user has an “Outbox” and an “Inbox”. The “Outbox” is used to trigger freebusy lookup or send invites or replies. The “Inbox” is where invites or replies are delivered. Clients monitor the “Inbox” for incoming scheduling messages.

Sequence of diagrams showing free-busy lookup

1

Organizer sends freebusy request to server

2

Server calculates freebusy data for attendees

3

Server returns aggregated freebusy data to organizer

1

Organizer sees freebusy for everyone

2

Can adjust meeting time to avoid conflicts

Sequence of diagrams showing invitations being sent out, replies returned.

1

Organizer sends invite request to server

2

Server copies the request into attendees' Inbox

3

Attendee checks the server

4

Attendee retrieves the invite from the server

1

Attendee replies to the server

2

Server copies the reply into organizer’s Inbox

3

Organizer checks the server

4

Organizer retrieves the reply from the server

Demo Participants

Demo Participants