130 likes | 211 Views
Agenda. 5 minutes: WG Overview, announcements 10 minutes: Document plans 30 minutes: Interoperability Experience 10 minutes: Timezone Registry work Links: See http://ietf.webdav.org/calsify Agenda Bash? Speak now… Scribes?. Charter goals review.
E N D
Agenda • 5 minutes: WG Overview, announcements • 10 minutes: Document plans • 30 minutes: Interoperability Experience • 10 minutes: Timezone Registry work • Links: See http://ietf.webdav.org/calsify • Agenda Bash? Speak now… • Scribes?
Charter goals review • Publish the interoperability issues and document the usage of iCalendar. • Revise the Calendaring and Scheduling standards for improved interoperability. • Clarify the registration process for iCalendar extensions. • Advance the Calendaring and Scheduling standards to Draft Standard. • Work on transition (upgrade or versioning) mechanisms for calendar data exchange.
Announcements • Following PROTO WG process in development • Increases role of WG chair in shepherding docs through IESG process • Proposed updates to RFC 2026 and RFC 2418 • Moving to Draft Standard may leave some early products as "sub-standard" • CalDAV status will be on list but CalDAV *not* in scope • SIP calendar events proposal individual I-D (also not in scope) • Notice of planned US timezone changes (DST) • See http://ietf.webdav.org/calsify for links
RFC-2445bis Strategy • Simplify and clarify iCalendar • Reduce ambiguity • Greater interoperability • Greater acceptance • Move to draft standard
Other WG documents planned • Pat Egen, Jeff McCullough: Interop documentation to support Draft Standard • Cyrus Daboo: iTIP bis • Alexey Melnikov: iMIP bis
Gathering Interoperability Data • Calconnect posted questionnaires to IETF mailing lists • Recurrences • Timezones • Calconnect is hosting Interoperability events • Solicit Input
Interoperability problem areas • Recurrences • Range Parameter • Rescheduling overlapping entries • Unbounded Rules • Awkward Rules
Timezones • Timezones • Most calendar applications only provide support for a finite set of time zones. • Support for arbitrary timezones is not realistic • Have servers match up with submitted timezone • Support internally
Compiling Use Case Data • Basic • Recurrence • Timezone • Scheduling (iTIP)
Areas with few implementations • vToDos component • vJournal component • Geo property • BySeconds RRule property • Counter proposing a meeting (iTIP) • Delegation of event to someone else (iTIP)
Timezone DBs Today • Olson Timezone database • Volunteers, email list "registration" • Almost a service (FTP) though not tailored for seeing only TZ changes • Existing software • Many TZ dbs in software are based on Olson • Many languages have built-in TZ dbs and logic (java, Python) • OS include TZ dbs (Windows, Linux, Mac) • Some, but not all, calendar client implementations have their own TZ dbs
I-D on Timezone Registry • Individual submission (not WG chartered) but we can provide input • A timezone service (more than just a registry) • Ownership issues -- IANA doesn't do live services • Political issues -- e.g. who reviews whether TZs are legit • Technical issues -- e.g. scale and security • Inviting comment: requirements, document determination, implementation experience • Experimental?
Questions? • http://ietf.webdav.org/calsify