Standard Netconf Content Brainstorming on getting there IETF 70

Outline Context Two Approaches Top Down Bottom Up Example Hierarchy Requirements on first content

Context We can consider the NETCONF solution to consist of three bits Netconf protocol Method of specifying content Content There are currently many options for defining Netconf content XML Schema Relax NG XML Schema + extensions Relax NG + extensions Yang Owl RDF Etc. All methods describe the same XML going over the wire, just in different ways Therefore there is no reason to not start defining standard NETCONF content now We can always rewrite the specifications later when the selection has been made and standardized on.

Two approaches – Bottom Up Pick a single working group, work with them to define some NETCONF content to configure and manage their technology. Pros Allows us to get started right away Cons May end up with mash up of unrelated content definitions

Two approaches – Top Down First design the general hierarchy of how data models will fit together and some base elements which technologies should base themselves off Interfaces Entities Applications Etc. Pros End up with well organized content which is easier to understand and to filter maximizes consistency whenever possible Cons Requires up front work which might delay us

Example Hierarchy System System-level data Interfaces Physical Entities Applications NETCONF

Requirements on first Content Need to make sure the content we start off with is configurable Is there some way to get us going faster? Tie to typical CLI configuration model? Use other existing data model Or do we need to start from scratch?