Minutes 2017 09 20

Meeting Materials	Attending
WebEx Recording password: 3uMRxxMU	Tianran Zhou, Igor, Xufeng Liu, Eric Voit, Zhengguangying (Walker), Andy Bierman, Henk Birkholz, Alex Clemm

Reviewed the scope proposals (hyperlinked below)

Needs to add the identity of "UDP" to the subscribed-notifications draft.
- Is it better to make the subscribed-notifications draft have the encoding as a string so that we don't need to rev the model for this?
There is already an encoding for Binary CBOR. This is a front-runner for the encoding. Needs a determination of whether to attempt both.
- Concern that we have too many options, need a way to differentiate
- Something to discuss on the NETCONF mailing list as a whole? When to do this?
- Simplicity of one way to do this should be considered
- CBOR has efficiency for transporting numbers

Does this just work with XPATH? At this point, don't have other filter examples to examine, so the safe assumption is yes. But if the response codes for interface 2 could be done in a generic way to indicate YANG subtrees supported by each
intersections between 1 & 4 are outside the scope of the draft
API #2 needs to handle even slow mobility of subtrees.
- Eric note: perhaps this could be done by an augmented subscription modified state change notification which lists the subtrees being handled by each Publication Server. (If we go down this path, we should likewise add this too subscription started, and the elements returned from the RPC . And also a dynamic-subscription should allow a unidirectional push.

One element which needs scoping is the binding of the high level SUPA definition to the YANG RPCs and Notifications which comprise our set of external actions. This includes:
- Automated provisioning toolkit for subscriptions, event streams, and driving one way notifications.
- Need to define the universe of actions to bind to existing work:
  - One time push of push-update,
  - set up of a subscription,
  - issue another existing notification
- Need to define the language of the condition
Further scoping to identify the Notifications, RPCs, and Configured Subscription provisioning invokable from SUPA. I.e., we need to understand the requested bindings more closely.

Next Meeting Agenda