diff options
Diffstat (limited to 'vnfs/TestVNF/netconftemplates/netconftemplates/yang@2017-02-20.yin')
| -rw-r--r-- | vnfs/TestVNF/netconftemplates/netconftemplates/yang@2017-02-20.yin | 91 |
1 files changed, 91 insertions, 0 deletions
diff --git a/vnfs/TestVNF/netconftemplates/netconftemplates/yang@2017-02-20.yin b/vnfs/TestVNF/netconftemplates/netconftemplates/yang@2017-02-20.yin new file mode 100644 index 00000000..7a4d5846 --- /dev/null +++ b/vnfs/TestVNF/netconftemplates/netconftemplates/yang@2017-02-20.yin @@ -0,0 +1,91 @@ +<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1"> + <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring"><?xml version="1.0" encoding="UTF-8"?> +<module name="yang" + xmlns="urn:ietf:params:xml:ns:yang:yin:1" + xmlns:yang="urn:ietf:params:xml:ns:yang:1" + xmlns:md="urn:ietf:params:xml:ns:yang:ietf-yang-metadata"> + <namespace uri="urn:ietf:params:xml:ns:yang:1"/> + <prefix value="yang"/> + <import module="ietf-yang-metadata"> + <prefix value="md"/> + <revision-date date="2016-08-05"/> + </import> + <organization> + <text>libyang</text> + </organization> + <contact> + <text>Web: &lt;https://github.com/CESNET/libyang/&gt; +Author: Radek Krejci &lt;rkrejci@cesnet.cz&gt;</text> + </contact> + <description> + <text>This is a kind of fake model with no data, typedefs or anything +else. libyang uses this module to implement various YANG attributes +defined in RFC 6020.</text> + </description> + <revision date="2017-02-20"> + <description> + <text>Added metadata for NETCONF's edit-config manipulation with ordered +lists and leaf-lists.</text> + </description> + <reference> + <text>RFC 7950: The YANG 1.1 Data Modeling Language</text> + </reference> + </revision> + <revision date="2016-02-11"> + <description> + <text>Initial revision</text> + </description> + <reference> + <text>RFC 6020: YANG - A Data Modeling Language for +the Network Configuration Protocol (NETCONF)</text> + </reference> + </revision> + <md:annotation name="insert"> + <type name="enumeration"> + <enum name="first"/> + <enum name="last"/> + <enum name="before"/> + <enum name="after"/> + </type> + <description> + <text>In user ordered leaf-list, the attribute can be used to control +where in the leaf-list the entry is inserted. It can be used during +the NETCONF &lt;edit-config&gt; &quot;create&quot; operations to insert a new list or +leaf-list entry, or during &quot;merge&quot; or &quot;replace&quot; operations to insert +a new list or leaf-list entry or move an existing one. + +If the value is &quot;before&quot; or &quot;after&quot;, the &quot;value&quot;/&quot;key&quot; attribute +MUST also be used to specify an existing entry in the list or leaf-list. + +If no &quot;insert&quot; attribute is present in the &quot;create&quot; operation, it +defaults to &quot;last&quot;.</text> + </description> + <reference> + <text>RFC7950 section 7.8.6. and section 7.7.9.</text> + </reference> + </md:annotation> + <md:annotation name="value"> + <type name="string"/> + <description> + <text>In user ordered leaf-list, the attribute must be used if the attribute +insert is used and specifies before/after which existing instance the +new instance should be inserted.</text> + </description> + <reference> + <text>RFC7950 section 7.7.9.</text> + </reference> + </md:annotation> + <md:annotation name="key"> + <type name="string"/> + <description> + <text>In user ordered list, the attribute must be used if the attribute +insert is used and specifies before/after which existing instance the +new instance should be inserted.</text> + </description> + <reference> + <text>RFC7950 section 7.8.6.</text> + </reference> + </md:annotation> +</module> +</data> +</rpc-reply> |