Hi, Daixinning <[email protected]> wrote: > Hi, > > RFC7950 has defined a terminology "data tree", shown as below: > o data tree: An instantiated tree of any data modeled with YANG, > e.g., configuration data, state data, combined configuration and > state data, RPC or action input, RPC or action output, or > notification. > > I have a question on this issue, that is, > Whether the content of the <config> node in <edit-config> is a "data > tree"
No, the "config" is modelled as "anyxml" so it just an "XML blob". >, and does it need to follow the constraints of the "data tree" > (e.g., The container node exists an most one instance in the data > tree). > For example, the netconf message content is like this > > <edit-config> > <target><running/></target> > <config> > <system xmlns=" urn:ietf:params:xml:ns:yang:ietf-system"> > <contact>[email protected]</contact> > </system> > <system xmlns=" urn:ietf:params:xml:ns:yang:ietf-system"> > <hostname>Ubuntu-test-01</hostname> > </system> > </config> > </edit-config> > > These two <system> tags is disobeyed the constraint or not? No. /martin _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
