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 operating system updates, or in the long run to replace them. In practice these OS updates are sometimes delayed or deferred, and I think the hope is partly that such problems would occur less often with tzdist.
Privacy ought to easier for this usage of tzdist, as network observers shouldn't be able to learn more about full tzdata updates than they can for any other OS update.
Consider an internet-connected bedside alarm clock
Given your comments, I'd think that any such alarm clock should get the entire tz database, just as an OS update would. This would preserve privacy better than having the alarm clock query only about updates to America/Los_Angeles and Europe/Paris.
_______________________________________________ ietf-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-privacy
