Proposal to do away with netconf attributes in data model payloads

[Andy Bierman <abierman@cisco.com>]

Hi Juergen,

Would this idea make you like edit-config any better?

What if we formalized the edit-config verb as a node under
<config> instead of putting it in the data model?

I.e., instead of
 
 <edit-config>
    ...
    <config>
       <foo operation="create"> ... </foo>
       <goo operation="modify"> ... </goo>
    </config>
  </edit-config>

    where <config> is the standard container

we have:

  <edit-config>
    ...
    <config>
      <create>
        <foo> ... </foo>
      </create>
      <modify>
         <goo> ... </goo>
      </modify>
    </config>
  </edit-config>

 where <create>, <modify>, <merge>, <replace> and <delete>
 are the standard containers.  The verb applies to the
 innermost nest-level specified in the data model content.
 Each of these containers can appear zero or one times (in any
 order) within a <config> element.  The agent will execute
 them in the order they appear.

In addition, the same technique could be used to eliminate the
need to have an xpath attribute in the data model:

  <get-config>
    ...
    <config>
      <filter value="xpath-expr-for-foo">
        <foo/> 
      </filter>
      <filter value="xpath-expr-for-goo">
         <goo> ... </goo>
      </filter>
    </config>
  </get-config>

<filter> can appear zero or more times.  Data like <foo>
can appear instead of <filter>.

----------------------------------------------------------------

Separate proposal:

I wouldn't even mind if we put the 'config' in the
element path, so we had:

  <edit>
    <config>
      ... normal edit-config parmameters like <error-option> ...
      <config-data>  (container renamed from <config>)
        <create>  ... </create>
      </config-data>
    </config>
  </edit>

 This way <config> could be a 'choice' in the XSD, and
 we could add other 'filters' later.  For <get> the
 choice is between <config> or <all>:

  <get>
    <config>
      ... get-config specific params
      <config-data>
         ...
      </config-data>
    </config>
  </get>

OR

  <get>
    <all>
      ... get-all specific params
      <data>
         ...
      </data>
    </all>
  </get>

Andy


--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>