Cyrus Daboo wrote:
it does make sense to provide a
full set of tz data option in the protocol to allow clients to get the entire
set of current data without exposing which specific time zone(s) they are
actually interested in (which would also remove the need for them to use etags).
Yes.
Daniel Kahn Gillmor wrote:
Given that the all-tzdata-as-a-software-update mechanism is already
available, I sort of assumed that this draft was intended for systems
that don't already have such a mechanism.
My impression is that the tzdist protocol is also intended to supplement those
Lester Caine wrote:
some devices such as central heating controllers
would not need a processor capable of the sort of processing power
needed to handle that
Even the lowliest central heating controller can easily handle the entire tz
database, if only to discard unneeded parts as they're
Cyrus Daboo wrote:
I will try and propose some text for a Privacy Considerations section
Although we will need such a section, the tzdist privacy issues dkg raised
shouldn't be addressed merely by adding a section that says in essence, yes,
admittedly tzdist's privacy stinks, but at least
