CALSIFY WG meeting notes

• Official Meeting notes
• Chat log
• Links

Next steps post meeting?

• Work with Chris and Bernard on what to work on first for 2445
• Make sure Alexey and Cyrus have what they need to provide their drafts

The timezone discussion seemed, to me, for the first time, to be consistently impressing people with how much of a problem timezones are. Timezone databases proliferate in OS, language libraries, clients and servers. There is no truly authoritative source for timezone information at all -- the Olson database is the closest thing we have to that and apparently one only needs to track their mailing list for a short while to understand how much human control and vigilance is needed to maintain that. Some other consensuses I thought I detected:

• It isn't enough to just create an IANA registry. We don't know how IANA would even be able to evaluate submissions of timezone data changes.
• A timezone service is thought to be useful.
• We don't know yet how to scale a timezone data service or how centralized or distributed we could or should make it.

Adding my own opinions:

• We had only one implementor who had experience with clients using a service to update TZ definitions. More experience would be a great help.

At some point I need to follow up with people who were interested in working on timezones -- including Pete Resnick, Elliott Lear, Patrik Faltstrom, Chris Newman and Doug Royer. Possibly foster new WG?

Remote UI BOF

• Agenda
• Draft

My notes:

• Discussions of exchanging widgets -- GUI presentation data -- over a protocol
• Pete suggested XMPP was a hammer for this nail
• Aki suggested SIP was a hammer for this nail
• The W3C guys think that the GUI description language stuff is already worked out or are confident it will be worked out in the W3C. I don't know what that is or how mature it is.
• Calling a protocol "lightweight" usually turns out to be ironic. Heh. However in this case LRDP seems to be more a framework, like SASL. That's not necessarily a good thing. IMH Experience, the W3C (and others) has at times been enamored of a great deal more pluggability and extensibility than is actually good for interoperability.

SIEVE WG

• Much advancement among the various drafts -- three going to WG last call very soon -- basic work clearly very well understood.
• Remember to get on mailing list so I can let Grant and Brian know when these last calls happen. Unless somebody else at OSAF is already on sieve?