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

[Thomas Nadeau <[e-mail]>]

	Hi all,

	Apologies for not following up on this until now. I started my new gig about a week ago and have been going full tilt.  Anyways, I'd like to make a final consensus call on this matter so that we can move the draft forward. 

	After some decent discussion around the matter at hand, there appears to be sufficient consensus to move forward with the proposal below. I also see that Martin just posted an updated that aligns with this, so I think we are all set to move forward.

	--Tom




> 
> 	I would like to call consensus on this matter. I've received %100 supporting comments for the proposal from the WG with no one not liking the proposal. The only comments received were from Martin and Benoit with regard to enhancing the description around the timezone-name typedef.  Document editors, please take those two comments into account and make the changes necessary. You might want to propose the text on the list before publishing as it should be a fairly minor change, but just to make sure it covers the comments received.
> 
> 	--Tom
> 
> 
>> 
>> 	Netmod WG:
>> 
>> 	The working group chairs have considered the discussion concerning 
>> the timezone-location leaf in draft-ietf-netmod-system-mgmt-10 and
>> draft-ietf-netmod-iana-timezones-03. In particular, we would like
>> like to call consensus on the matter regarding that surfaced during
>> the IETF last call with regard to the the practicability of maintaining a 
>> YANG module with an enumeration of timezone names. We believe there is
>> consensus in the working group to move forward with the following 
>> resolution:
>> 
>> - The YANG module in draft-ietf-netmod-system-mgmt-11 gets
>> extended to introduce a new typedef for timezone names, e.g.
>> something that looks like:
>> 
>> typedef timezone-name {
>>  type string;
>>  description
>>   "A timezone name as used by the Time Zone Database, sometimes
>>    referred to as the 'Olson Database'.";
>>  reference
>>   "RFC 6557: Procedures for Maintaining the Time Zone Database";
>> }
>> 
>> The timezone-location leaf will be changed to use this type,
>> the import of iana-timezones will be removed and the references
>> to I-D.ietf-netmod-iana-timezones will be removed.
>> 
>> - The draft-ietf-netmod-iana-timezones-00 document will be pulled
>> back and work on this draft will stop.  The I-D is declared dead.
>> 
>> - Since there is nothing to do for IANA, there will be no IANA request 
>> needed in this regard for draft-ietf-netmod-system-mgmt-11. 
>> 
>> 	We note that further alternatives can be added to the timezone
>> choice in the future should the two mechanisms currently in place
>> turn out to be insufficient in practice.
>> 
>> 	We would like to give the WG sufficient time to raise any additional concerns or 
>> issues with regard to this issue and our path for resolving the issue at hand, and so we 
>> will accept comments/discussion on this matter until 8AM EDT on Tuesday, January 28, 2014.
>> As Juergen has been closely involved with the matter, I will adjudicate any issues
>> arising from this comment period.
>> 
>> 	Thanks,
>> 
>> 	Tom
>> 
>> 
>> 
>> 
>