Re: [netmod] consensus all: timezone-location and draft-ietf-netmod-iana-timezones-03

[Juergen Schoenwaelder <[e-mail]>]

On Sat, Feb 01, 2014 at 10:56:54AM +0100, Ladislav Lhotka wrote:
> 
> From the network management point of view, it is important to be able to set the behaviour of the system clock properly. I would consider the module to be outdated only if it makes this impossible, and then it should be updated.
> 

Having two definitions of timezone names that are not synced is the
worst of all solutions. I want 3rd party NETCONF implementations to
function on open systems where the packaging and maintenance of the
timezone database is separate from the packaging and maintenance of
the NETCONF implementation.

We started with the idealistic idea there could be a maintained
enumeration and it turns out this is not realistic to establish and
likely also difficult to implement on open systems. So we are going
with a string which I believe will work just fine for a large part of
the world. If we find out later that this is not workable, we can add
additional objects to report which time zone names are available. At
this point in time, we have to ship things.

I leave it to Tom to determine concensus. But I note that concensus
can be rough.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>