Adding TestVNF netconf server

[demo.git] / vnfs / TestVNF / netconftemplates / netconftemplates / ietf-yang-metadata@2016-08-05.yin

diff --git a/vnfs/TestVNF/netconftemplates/netconftemplates/ietf-yang-metadata@2016-08-05.yin b/vnfs/TestVNF/netconftemplates/netconftemplates/ietf-yang-metadata@2016-08-05.yin
new file mode 100644 (file)
index 0000000..6b87e82
--- /dev/null
+++ b/vnfs/TestVNF/netconftemplates/netconftemplates/ietf-yang-metadata@2016-08-05.yin
@@ -0,0 +1,89 @@
+<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">&lt;?xml version="1.0" encoding="UTF-8"?&gt;
+&lt;module name="ietf-yang-metadata"
+        xmlns="urn:ietf:params:xml:ns:yang:yin:1"
+        xmlns:md="urn:ietf:params:xml:ns:yang:ietf-yang-metadata"&gt;
+  &lt;namespace uri="urn:ietf:params:xml:ns:yang:ietf-yang-metadata"/&gt;
+  &lt;prefix value="md"/&gt;
+  &lt;organization&gt;
+    &lt;text&gt;IETF NETMOD (NETCONF Data Modeling Language) Working Group&lt;/text&gt;
+  &lt;/organization&gt;
+  &lt;contact&gt;
+    &lt;text&gt;WG Web:   &amp;lt;https://datatracker.ietf.org/wg/netmod/&amp;gt;
+
+WG List:  &amp;lt;mailto:netmod@ietf.org&amp;gt;
+
+WG Chair: Lou Berger
+          &amp;lt;mailto:lberger@labn.net&amp;gt;
+
+WG Chair: Kent Watsen
+          &amp;lt;mailto:kwatsen@juniper.net&amp;gt;
+
+Editor:   Ladislav Lhotka
+          &amp;lt;mailto:lhotka@nic.cz&amp;gt;&lt;/text&gt;
+  &lt;/contact&gt;
+  &lt;description&gt;
+    &lt;text&gt;This YANG module defines an 'extension' statement that allows
+for defining metadata annotations.
+
+Copyright (c) 2016 IETF Trust and the persons identified as
+authors of the code.  All rights reserved.
+
+Redistribution and use in source and binary forms, with or
+without modification, is permitted pursuant to, and subject to
+the license terms contained in, the Simplified BSD License set
+forth in Section 4.c of the IETF Trust's Legal Provisions
+Relating to IETF Documents
+(http://trustee.ietf.org/license-info).
+
+This version of this YANG module is part of RFC 7952
+(http://www.rfc-editor.org/info/rfc7952); see the RFC itself
+for full legal notices.&lt;/text&gt;
+  &lt;/description&gt;
+  &lt;revision date="2016-08-05"&gt;
+    &lt;description&gt;
+      &lt;text&gt;Initial revision.&lt;/text&gt;
+    &lt;/description&gt;
+    &lt;reference&gt;
+      &lt;text&gt;RFC 7952: Defining and Using Metadata with YANG&lt;/text&gt;
+    &lt;/reference&gt;
+  &lt;/revision&gt;
+  &lt;extension name="annotation"&gt;
+    &lt;argument name="name"/&gt;
+    &lt;description&gt;
+      &lt;text&gt;This extension allows for defining metadata annotations in
+YANG modules.  The 'md:annotation' statement can appear only
+at the top level of a YANG module or submodule, i.e., it
+becomes a new alternative in the ABNF production rule for
+'body-stmts' (Section 14 in RFC 7950).
+
+The argument of the 'md:annotation' statement defines the name
+of the annotation.  Syntactically, it is a YANG identifier as
+defined in Section 6.2 of RFC 7950.
+
+An annotation defined with this 'extension' statement inherits
+the namespace and other context from the YANG module in which
+it is defined.
+
+The data type of the annotation value is specified in the same
+way as for a leaf data node using the 'type' statement.
+
+The semantics of the annotation and other documentation can be
+specified using the following standard YANG substatements (all
+are optional): 'description', 'if-feature', 'reference',
+'status', and 'units'.
+
+A server announces support for a particular annotation by
+including the module in which the annotation is defined among
+the advertised YANG modules, e.g., in a NETCONF &amp;lt;hello&amp;gt;
+message or in the YANG library (RFC 7950).  The annotation can
+then be attached to any instance of a data node defined in any
+YANG module that is advertised by the server.
+
+XML encoding and JSON encoding of annotations are defined in
+RFC 7952.&lt;/text&gt;
+    &lt;/description&gt;
+  &lt;/extension&gt;
+&lt;/module&gt;
+</data>
+</rpc-reply>