diff options
Diffstat (limited to 'vnfs/TestVNF/netconftemplates/netconftemplates/notifications@2008-07-14.yin')
-rw-r--r-- | vnfs/TestVNF/netconftemplates/netconftemplates/notifications@2008-07-14.yin | 99 |
1 files changed, 99 insertions, 0 deletions
diff --git a/vnfs/TestVNF/netconftemplates/netconftemplates/notifications@2008-07-14.yin b/vnfs/TestVNF/netconftemplates/netconftemplates/notifications@2008-07-14.yin new file mode 100644 index 00000000..3633d0f1 --- /dev/null +++ b/vnfs/TestVNF/netconftemplates/netconftemplates/notifications@2008-07-14.yin @@ -0,0 +1,99 @@ +<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="notifications" + xmlns="urn:ietf:params:xml:ns:yang:yin:1" + xmlns:ncEvent="urn:ietf:params:xml:ns:netconf:notification:1.0" + xmlns:yang="urn:ietf:params:xml:ns:yang:ietf-yang-types"> + <namespace uri="urn:ietf:params:xml:ns:netconf:notification:1.0"/> + <prefix value="ncEvent"/> + <import module="ietf-yang-types"> + <prefix value="yang"/> + </import> + <organization> + <text>IETF NETCONF WG</text> + </organization> + <contact> + <text>netconf@ops.ietf.org</text> + </contact> + <description> + <text>Conversion of the 'ncEvent' XSD in the +NETCONF Notifications RFC.</text> + </description> + <reference> + <text>RFC 5277.</text> + </reference> + <revision date="2008-07-14"> + <description> + <text>RFC 5277 version.</text> + </description> + </revision> + <typedef name="streamNameType"> + <type name="string"/> + <description> + <text>The name of an event stream.</text> + </description> + </typedef> + <container name="notification"> + <config value="false"/> + <description> + <text>internal struct to start a notification</text> + </description> + <leaf name="eventTime"> + <type name="yang:date-and-time"/> + <mandatory value="true"/> + </leaf> + </container> + <rpc name="create-subscription"> + <description> + <text>The command to create a notification subscription. It +takes as argument the name of the notification stream +and filter. Both of those options limit the content of +the subscription. In addition, there are two time-related +parameters, startTime and stopTime, which can be used to +select the time interval of interest to the notification +replay feature.</text> + </description> + <input> + <leaf name="stream"> + <type name="streamNameType"/> + <default value="NETCONF"/> + <description> + <text>An optional parameter that indicates which stream of events +is of interest. If not present, then events in the default +NETCONF stream will be sent.</text> + </description> + </leaf> + <anyxml name="filter"> + <description> + <text>An optional parameter that indicates which subset of all +possible events is of interest. The format of this +parameter is the same as that of the filter parameter +in the NETCONF protocol operations. If not present, +all events not precluded by other parameters will +be sent.</text> + </description> + </anyxml> + <leaf name="startTime"> + <type name="yang:date-and-time"/> + <description> + <text>A parameter used to trigger the replay feature and +indicates that the replay should start at the time +specified. If start time is not present, this is not a +replay subscription.</text> + </description> + </leaf> + <leaf name="stopTime"> + <type name="yang:date-and-time"/> + <description> + <text>An optional parameter used with the optional replay +feature to indicate the newest notifications of +interest. If stop time is not present, the notifications +will continue until the subscription is terminated. +Must be used with startTime.</text> + </description> + </leaf> + </input> + </rpc> +</module> +</data> +</rpc-reply> |