ietf-ivy-wg / network-inventory-yang

Other
0 stars 3 forks source link

Unclear boundary for Ivy work #35

Open nigel-r-davis opened 5 months ago

nigel-r-davis commented 5 months ago

It is clear that we do not have a tight enough definition of the boundary on the Ivy work. We need to understand what is in scope and what not. It is not practical to list all things in scope, so instead we need rules against which we can evaluate whether something is in scope or out of scope.

Clearly, there are some things we would all agree are in scope and other things we would agree are out of scope. Identifying the inherent properties of those things will help.

But there are things that we do not agree about and even if we had a complete definition, there are things on the boundary or that straddle the boundary.

I emailed the list with some thoughts on how to organize things on a "map" to help us define the boundary.

I have attempted to sketch a map of things (over simplified in many places) that includes some questions and some sketch definitions. I would be happy to discuss this on our next call. IvyBoundary.pptx

nigel-r-davis commented 4 months ago

I have updated the slide pack to reflect what I presented. IvyBoundary.pptx

nigel-r-davis commented 4 months ago

I think the next action is: