1) IANA does have the ability to register time zones and they said they want that role.
2) They do NOT want to be a time zone 'server', just a registration place.
After emaling IANA and Ted I sent an email to CALSCH (where emails must go per 2445 for iCal registration processes) saying the next revision of the draft will remove all HTTP and FTP references making the draft an IANA registration process only. Something IANA says they want to do.
And as soon as the ID submissions are allowed again (after meeting) I will submit a new additional 2nd draft: tz-server-00.
And it would have been nice if Ted would have told me (the author of the independent draft) rather than talking to Lisa. In my last email to Ted I reminded him it was not a CALSIFY draft. Ted also talked to me in email about 'other ways' to do this, he was not specific. I want to move this draft forward. All communications need to be done with all knowledgeable persons.
My 2nd 'SERVER' idea that is independent of the registration draft is to allow vendors to set up servers to allow any client that gets an iTIP message generated by their products to get the latest TZ information. So when you send an iTIP invitation to a user they will have the the ability to get the latest TZ information as used by that vendor, and not a snapshot of what was valid the time it was sent. As many in the U.S. know, our TZ info may be changing soon. All static VTIMEZONE entries sent with iCal object may be inaccurate soon for the US.
10 min: Timezone Registry Requirements -- new agenda item
- Although this is not a WG chartered item, Ted Hardie (our Area Director) and I discussed this
draft briefly, and we need to hear from implementors whether it's a requirement to have a TZ registry
and if so does it need to be available in a format that's conducive to clients automatically updating
their timezone descriptions.
- I've also been told that IANA doesn't have the ability to do a registry with the features
specified in this document.
Doug Royer | http://INET-Consulting.com -------------------------------|-----------------------------
begin:vcard fn:Doug Royer n:Royer;Doug org:INET-Consulting.com adr:;;1795 W. Broadway St #266;Idaho Falls;ID;83402;U.S.A email;internet:Doug@xxxxxxxxx title:CEO tel;work:208-881-0380 tel;fax:866-494-8574 note;quoted-printable:AOL: SupportUnix=0D=0A= MSN: Support@xxxxxxxxxxxxxxxxxxx=0D=0A= Yahoo: Help4Unix x-mozilla-html:TRUE url:http://Royer.com version:2.1 end:vcard
Description: S/MIME Cryptographic Signature