1. Calendaring and Scheduling (C & S) Branch Hendrix Sr. Principal Technology Specialist Central Region - US Microsoft Corporation

2. Agenda  Today’s C & S problems across workgroups, across orgs, etc. across workgroups, across orgs, etc.  Existing IETF efforts iCMS, iCalendar, iTIP, iMIP, iRIP, CAP, SCAP iCMS, iCalendar, iTIP, iMIP, iRIP, CAP, SCAP  C & S will be a leveraged investment Other applications will integrate Other applications will integrate Developed applications Developed applications

3. Show of hands  How many of you have C & S systems deployed today?  How many of you have more than 1 C & S system deployed today?  How many of you have 2 or more C & S systems interoperating today?  How many of you have developed applications that leverage the C & S systems?  How many of you have looked at IETF C & S efforts and or products?

4. Today’s C & S problems  Common aspects most solutions deployed today are proprietary most solutions deployed today are proprietary leads to lack of interop leads to lack of interop lack of common security lack of common security limited community access limited community access  Some solutions exist point to point gateways point to point gateways expensive, typically not as feature rich as connected products expensive, typically not as feature rich as connected products not always “out of the box” not always “out of the box”

5. Specific Problem area  Security How do I offer extranet/Internet users calendaring access? How do I offer extranet/Internet users calendaring access? Today - This usually means anonymous access or proprietary security which entails creating user accounts somewhere Today - This usually means anonymous access or proprietary security which entails creating user accounts somewhere Direction? - It appears that Public Key technology & LDAP directory services might offer some advantages Direction? - It appears that Public Key technology & LDAP directory services might offer some advantages

6. Specific Problem area  If not using the browser, then how is access to C & S systems provided? Today - give the recipient your systems client software & an account Today - give the recipient your systems client software & an account Direction? - IETF efforts on C & S; LDAP directory services; Public Key Direction? - IETF efforts on C & S; LDAP directory services; Public Key  How do I make C & S developed applications more universal? Today - most interfaces are non- standard, solution is platform specific Today - most interfaces are non- standard, solution is platform specific Direction? - IETF efforts on C & S Direction? - IETF efforts on C & S

7. IETF efforts  iCMS abstract model of the objects & protocols necessary for info exchange abstract model of the objects & protocols necessary for info exchange  iCalendar - (IETF last call soon) Core Object Specification Core Object Specification  iTIP - (IETF last call soon) Transport-Independent Interoperability Protocol Transport-Independent Interoperability Protocol  iMIP - (IETF last call soon) Message-based Interoperability Protocol Message-based Interoperability Protocol

8. IETF efforts (cont.)  iRIP Real-time Interoperability Protocol Real-time Interoperability Protocol  CAP Calendar access protocol Calendar access protocol  SCAP Simple calendar access protocol (web) Simple calendar access protocol (web)

9. iCMS - Calendar Model Spec iCalendar Object Model iCAPiTIP Transport to Other systems and clients Client & Admin to Server iRIPiMIP E-mail basedSession

10. iCalendar - Core Object Spec.  Defines the format  Specifies MIME type: text/calendar  Hierarchy (e.g.) Calendar To-doeventjournalfreebusytimezoneproperty alarmproperty BEGIN:VCALENDAR PRODID:-//Microsoft//Outlook MIMEDIR//EN VERSION:2.0 METHOD:PUBLISH BEGIN:VEVENT DTSTART:19980814T200000Z DTEND:19980814T210000Z TRANSP:OPAQUE SEQUENCE:0 DTSTAMP:19980814T180247Z SUMMARY:Sample iCal Appointment PRIORITY:5 END:VEVENT END:VCALENDAR

11. iTIP - Transport-Independent Interoperability Protocol  “Specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems”  Application Protocol defines the content of the iCalendar objects being exchanged defines the content of the iCalendar objects being exchanged  Transport Protocol defines how the iCalendar objects are sent between sender and receiver defines how the iCalendar objects are sent between sender and receiver  Defined methods Publish, Request, Reply, Add, Cancel, Refresh, Counter, Decline-Counter Publish, Request, Reply, Add, Cancel, Refresh, Counter, Decline-Counter

12. iMIP - Message-based Interoperability Protocol  Specifies binding from iTIP to Internet e-mail based transports  Security (related documents still need to be advanced) via RFC-1847 compliant encryption via RFC-1847 compliant encryption RFC-1847 is Security Multiparts for MIME RFC-1847 is Security Multiparts for MIME

13. iRIP Real-time Interoperability Protocol  Specifies a binding from iTIP to a real-time transport  Forward real-time requests on behalf of users/clients  Does not support client access functions like: browsing, retrieval, & search  utilizes TCP/IP port 5228  Calendars are URI, hence e.g. irip://calendar.example.com/branchh e.g. irip://calendar.example.com/branchh  Authentication is via SASL supports Proxy Access, Anonymous Access, plain text password supports Proxy Access, Anonymous Access, plain text password

14. CAP - Calendar Access Protocol  Requirements doc is being generated  no work on protocols at this time  Defines calendar admin & object management  Support both connected and synchronized operations

15. SCAP - Simple Calendar Access Protocol  Individual submission currently, not a workgroup effort  HTTP as transport  XML to encode calendar objects

16. Why is C & S so important?  Many other products/services would like to leverage vs. duplicate Real-time conferencing Real-time conferencing Data sharing, voice, audio, etc. Data sharing, voice, audio, etc. End Users would like to instigate various activities based upon a common schedule End Users would like to instigate various activities based upon a common schedule Other form factors devices need commonality (Phones, Palm & Handheld devices, etc.) Other form factors devices need commonality (Phones, Palm & Handheld devices, etc.)

17. Why is C & S so Important?  Lots of in-house built applications can leverage Events publishing Events publishing Resource booking Resource booking

18. Key Technologies that are important to C & S systems  Directory Services LDAP LDAP  Security Public Key (X.509v3) Public Key (X.509v3)  Protocols & Object definitions IETF efforts IETF efforts

19. Discussion