Hi Lester and others,
Many slave devices do not rely on having a power consuming clock actually on board and instead access a master time source on the system, so the need for a full calendar system is avoided, but instead the time service needs to handle DST changes and this is where tzdist provides a documented standard to provide that area of the service.
As this discussion has demonstrated IoT is so widely varied that it is difficult to characterize a single set of requirements. There are a great many environments:
A great many devices will only be updated very rarely. They do not have Internet access and will be in inconvenient places, like the ground in an oil field in Alaska. Some will have downtime windows, like devices used in battle conditions. Some devices won't be put into service for years, and when they are, they'll be expected to function properly.
In all of these cases, I suspect that either TZ can accommodate them with what's there today, or there is no standard change that will accommodate them at all.
Eliot