Minutes 2017 01 25

Meeting Materials	Attending
WebEx Recording password: WcsEmDx3	Andy Bierman, Alexander Clemm, Ambika Tripathy, Einar Nilsen-Nygaard, Eric Voit, Tim Jenkins, Balazs Lengyel, Mehmet Ersue, Alberto Gonzalez

Presented list of potential errors for RPCs & Notifications
Don't want to overload RPC error. Perhaps we could place this information in Error App Tag strings instead of returned data. Take this to the mailing list to determine the right way to communicate these types of errors.
No changes to the asserted list of error types other than everyone agreeing that warnings would not be provided.

Balazs presented: Instance vs Extension vs Deviation
Since draft release, NETMOD members have pointed out that deviations can be used for this function (including attributes)
Failing of YANG compiler here is a not a result of drawbacks in YANG languages
Group is split between Deviations, and Instance data. Will resolve on NETMOD mailer.
Vote for your favorite on NETMOD

At this point, no votes against the charter change, voting closes Jan 27th.
Mehmet will float some charter text if things close this way.
Notifications 2.0 will be picked back up after the vote result (if charter change is accepted).
Perhaps a topic for out meeting in two weeks.

Do we want to add "changes only" option for periodic subscriptions for this draft, rather than a futures?
Sentiment is in-favor. However there are complexities we still need to address before we add to the draft:

Do we send the full schema tree always with no leafs have changed at the end of the period?
Do we send patch mechanisms on the schema tree?
Do we want to send null notification updates if nothing has changed across the entire subscription?

If null notifications are not sent, then the behavior will be quite close to on-change in terms of transaction volumes between devices.

Provide feedback