Michal Vasko | ad92811 | 2015-11-25 15:52:10 +0100 | [diff] [blame] | 1 | <?xml version="1.0" encoding="UTF-8"?> |
| 2 | <module name="notifications" |
| 3 | xmlns="urn:ietf:params:xml:ns:yang:yin:1" |
| 4 | xmlns:ncEvent="urn:ietf:params:xml:ns:netconf:notification:1.0" |
| 5 | xmlns:yang="urn:ietf:params:xml:ns:yang:ietf-yang-types"> |
| 6 | <namespace uri="urn:ietf:params:xml:ns:netconf:notification:1.0"/> |
| 7 | <prefix value="ncEvent"/> |
| 8 | <import module="ietf-yang-types"> |
| 9 | <prefix value="yang"/> |
| 10 | </import> |
| 11 | <organization> |
| 12 | <text>IETF NETCONF WG</text> |
| 13 | </organization> |
| 14 | <contact> |
| 15 | <text>netconf@ops.ietf.org</text> |
| 16 | </contact> |
| 17 | <description> |
| 18 | <text>Conversion of the 'ncEvent' XSD in the |
| 19 | NETCONF Notifications RFC.</text> |
| 20 | </description> |
| 21 | <reference> |
| 22 | <text>RFC 5277.</text> |
| 23 | </reference> |
| 24 | <revision date="2008-07-14"> |
| 25 | <description> |
| 26 | <text>RFC 5277 version.</text> |
| 27 | </description> |
| 28 | </revision> |
| 29 | <typedef name="streamNameType"> |
| 30 | <description> |
| 31 | <text>The name of an event stream.</text> |
| 32 | </description> |
| 33 | <type name="string"/> |
| 34 | </typedef> |
| 35 | <rpc name="create-subscription"> |
| 36 | <description> |
| 37 | <text>The command to create a notification subscription. It |
| 38 | takes as argument the name of the notification stream |
| 39 | and filter. Both of those options limit the content of |
| 40 | the subscription. In addition, there are two time-related |
| 41 | parameters, startTime and stopTime, which can be used to |
| 42 | select the time interval of interest to the notification |
| 43 | replay feature.</text> |
| 44 | </description> |
| 45 | <input> |
| 46 | <leaf name="stream"> |
| 47 | <description> |
| 48 | <text>An optional parameter that indicates which stream of events |
| 49 | is of interest. If not present, then events in the default |
| 50 | NETCONF stream will be sent.</text> |
| 51 | </description> |
| 52 | <type name="streamNameType"/> |
| 53 | <default value="NETCONF"/> |
| 54 | </leaf> |
| 55 | <anyxml name="filter"> |
| 56 | <description> |
| 57 | <text>An optional parameter that indicates which subset of all |
| 58 | possible events is of interest. The format of this |
| 59 | parameter is the same as that of the filter parameter |
| 60 | in the NETCONF protocol operations. If not present, |
| 61 | all events not precluded by other parameters will |
| 62 | be sent.</text> |
| 63 | </description> |
| 64 | </anyxml> |
| 65 | <leaf name="startTime"> |
| 66 | <description> |
| 67 | <text>A parameter used to trigger the replay feature and |
| 68 | indicates that the replay should start at the time |
| 69 | specified. If start time is not present, this is not a |
| 70 | replay subscription.</text> |
| 71 | </description> |
| 72 | <type name="yang:date-and-time"/> |
| 73 | </leaf> |
| 74 | <leaf name="stopTime"> |
| 75 | <description> |
| 76 | <text>An optional parameter used with the optional replay |
| 77 | feature to indicate the newest notifications of |
| 78 | interest. If stop time is not present, the notifications |
| 79 | will continue until the subscription is terminated. |
| 80 | Must be used with startTime.</text> |
| 81 | </description> |
| 82 | <type name="yang:date-and-time"/> |
| 83 | </leaf> |
| 84 | </input> |
| 85 | </rpc> |
| 86 | <container name="notification"> |
| 87 | <description> |
| 88 | <text>internal struct to start a notification</text> |
| 89 | </description> |
| 90 | <config value="false"/> |
| 91 | <leaf name="eventTime"> |
| 92 | <mandatory value="true"/> |
| 93 | <type name="yang:date-and-time"/> |
| 94 | </leaf> |
| 95 | </container> |
| 96 | </module> |