BTW Benoit’s note below and the WebEx should serve as the official 
notification to the WG that we will be having this interim meeting.  It was 
officially registered with the WG meeting tracker too.  Despite this, someone 
pointed out the other day that I’d not officially announced it.  Consider this 
the official announcement of the meeting on September 10, 2015. 

        The rough agenda is to discuss any and all alternatives to the Open 
Config proposal, and then compare/contrast the differences.  The goal of the 
meeting is to present a way forward to the WG between choosing to adopt this 
proposal or not, in whole or part, or to recommend in whole or part, the 
alternatives. 

        —Tom



> On Aug 7, 2015:11:21 AM, at 11:21 AM, Benoit Claise <[email protected]> wrote:
> 
> Dear all,
> 
> Let me set the stage for this future interim.
> 
> First of (and let me repeat), I'm happy that the operators gathered and 
> collectively worked on YANG models and related requirements.
> 
> The previous two interim meetings in June on the openconfig issues 
> (draft-openconfig-netmod-opstate-01 
> <http://datatracker.ietf.org/doc/draft-openconfig-netmod-opstate/> and 
> draft-openconfig-netmod-model-structure-00 
> <http://datatracker.ietf.org/doc/draft-openconfig-netmod-model-structure/>) 
> were successful in the sense that the requirements are now understood.
> 
> Unfortunately, some key players were not in Prague and we could not finalize 
> the discussion.
> How to represent the operational state is one important guidance from RFC 
> 6087bis that we must be providing to all existing and future YANG models (and 
> not only in the IETF). 
> 
> We need to bring closure on that topic, and this is the plan for that interim 
> meeting in September.
> 
> http://datatracker.ietf.org/doc/draft-openconfig-netmod-opstate/ 
> <http://datatracker.ietf.org/doc/draft-openconfig-netmod-opstate/> has been 
> updated. Please comment on this version.
> Also, any alternate proposals must be prepared for that interim in September. 
> They must be prepared with the same level of rigour as 
> draft-openconfig-netmod-opstate., i.e. must have the same level of details.
> 
> In the meeting in September, the goal is to take a decision. 
> 
> Regards, Benoit (OPS AD)
> 
>> 
>> Hello,
>> NETMOD Working Group invites you to join this WebEx meeting.
>>  
>> NETMOD Interm meeting on OpenConfig
>> Thursday, September 10, 2015 
>> 11:00 am  |  Eastern Daylight Time (New York, GMT-04:00)  |  1 hr 
>>  
>> Join WebEx meeting 
>> <https://ietf.webex.com/ietf/j.php?MTID=m54c7bcbed84a08dc78fba128d500f8c0>
>> Meeting number:      645 732 277 
>> Meeting password:    1234
>>  
>> Join by phone
>> 1-877-668-4493 Call-in toll free number (US/Canada)
>> 1-650-479-3208 Call-in toll number (US/Canada)
>> Access code: 645 732 277
>> Toll-free calling restrictions 
>> <http://www.webex.com/pdf/tollfree_restrictions.pdf>
>>  
>> Add this meeting 
>> <https://ietf.webex.com/ietf/j.php?MTID=m17086d6b9810a2722c5dc8c64ec795b9> 
>> to your calendar.
>>  
>> Can't join the meeting? Contact support. <https://ietf.webex.com/ietf/mc>
>>  
>> IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
>> information sent during the session to be recorded, which may be 
>> discoverable in a legal matter. By joining this session, you automatically 
>> consent to such recordings. If you do not consent to being recorded, discuss 
>> your concerns with the host or do not join the session.
>> 
>> 
>> _______________________________________________
>> netmod mailing list
>> [email protected] <mailto:[email protected]>
>> https://www.ietf.org/mailman/listinfo/netmod 
>> <https://www.ietf.org/mailman/listinfo/netmod>
> 
> _______________________________________________
> netmod mailing list
> [email protected] <mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/netmod 
> <https://www.ietf.org/mailman/listinfo/netmod>

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to