Hi all,

In the call on Oct 20 we primarily discussed how deviations are captured in the 
Packages draft and compared it to YANG library.

We felt that deviations in packages should be primarily used by server 
implementations to report deviations, and that they should be avoided by 
standards bodies. If an SDO publishes a package that contains another standard 
package plus some deviations, then it makes it impossible for a server to ever 
support both of those packages together.  Jan Lindblad is putting together some 
proposed wording to capture this.

There was a fair bit of debate about whether to have some technically redundant 
information in packages about deviations (i.e. show the associations between 
modules and modules that contain deviations for the former modules). The 
feeling in the end was to avoid that redundant information. It could be out of 
sync and would mean there are 2 ways to discover/manage deviations. Tools can 
easily take a "single truth" and output various summaries, associations, etc if 
needed (i.e. show what module each deviation file is applying deviations to, or 
show which deviation files are applying deviations to a given module).  Note 
that Library has redundant information about deviations (the ro deviation* 
leaf-list is not technically necessary from what we can tell) but we aren't 
proposing to change that at this time.

We *do* need the nbc-changes leaf in packages though. Some NBC changes can't be 
discovered by tools.

For next meeting we need to discuss interactions between NBC indicators and 
deviations.

Rgds,
Jason


-----Original Appointment-----
From: NETMOD Working Group <[email protected]>
Sent: Thursday, August 27, 2020 6:07 PM
To: NETMOD Working Group; [email protected]
Subject: [netmod] Webex meeting changed: NETMOD YANG Version Discussions
When: October 20, 2020 9:00 AM-10:00 AM America/New_York.
Where: https://ietf.webex.com/ietf/j.php?MTID=ma7627a2ae7b770537cff5f5b89293c70



NETMOD Working Group changed the Webex meeting information.


When it's time, join the Webex meeting here.


Meeting number (access code): 171 069 0374

Meeting password: semver?


Occurs every Tuesday effective Tuesday, September 1, 2020 until Tuesday, August 
24, 2021 from 9:00 AM to 10:00 AM, (UTC-04:00) Eastern Time (US & Canada)
9:00 am  |  (UTC-04:00) Eastern Time (US & Canada)  |  1 hr



Join 
meeting<https://ietf.webex.com/ietf/j.php?MTID=ma7627a2ae7b770537cff5f5b89293c70>



Tap to join from a mobile device (attendees only)
+1-650-479-3208,,1710690374##<tel:%2B1-650-479-3208,,*01*1710690374%23%23*01*> 
Call-in toll number (US/Canada)


Join by phone
1-650-479-3208 Call-in toll number (US/Canada)
Global call-in 
numbers<https://ietf.webex.com/ietf/globalcallin.php?MTID=m5914d38cfac744cced3593159cb7f971>



Join from a video system or application
Dial [email protected]<%20sip:[email protected]>
You can also dial 173.243.2.68 and enter your meeting number.



Join using Microsoft Lync or Microsoft Skype for Business
Dial [email protected]<%20sip:[email protected]>



Need help? Go to http://help.webex.com


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

Reply via email to