1 <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1">
2 <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">module yang {
3 namespace "urn:ietf:params:xml:ns:yang:1";
6 import ietf-yang-metadata {
8 revision-date 2016-08-05;
14 "Web: <https://github.com/CESNET/libyang/>
15 Author: Radek Krejci <rkrejci@cesnet.cz>";
17 "This is a kind of fake model with no data, typedefs or anything
18 else. libyang uses this module to implement various YANG attributes
19 defined in RFC 6020.";
23 "Added metadata for NETCONF's edit-config manipulation with ordered
24 lists and leaf-lists.";
26 "RFC 7950: The YANG 1.1 Data Modeling Language";
32 "RFC 6020: YANG - A Data Modeling Language for
33 the Network Configuration Protocol (NETCONF)";
36 md:annotation "insert" {
44 "In user ordered leaf-list, the attribute can be used to control
45 where in the leaf-list the entry is inserted. It can be used during
46 the NETCONF <edit-config> \"create\" operations to insert a new list or
47 leaf-list entry, or during \"merge\" or \"replace\" operations to insert
48 a new list or leaf-list entry or move an existing one.
50 If the value is \"before\" or \"after\", the \"value\"/\"key\" attribute
51 MUST also be used to specify an existing entry in the list or leaf-list.
53 If no \"insert\" attribute is present in the \"create\" operation, it
54 defaults to \"last\".";
56 "RFC7950 section 7.8.6. and section 7.7.9.";
58 md:annotation "value" {
61 "In user ordered leaf-list, the attribute must be used if the attribute
62 insert is used and specifies before/after which existing instance the
63 new instance should be inserted.";
65 "RFC7950 section 7.7.9.";
70 "In user ordered list, the attribute must be used if the attribute
71 insert is used and specifies before/after which existing instance the
72 new instance should be inserted.";
74 "RFC7950 section 7.8.6.";