Michal Vasko | 086311b | 2016-01-08 09:53:11 +0100 | [diff] [blame] | 1 | <?xml version="1.0" encoding="UTF-8"?> |
| 2 | <module name="nc-notifications" |
| 3 | xmlns="urn:ietf:params:xml:ns:yang:yin:1" |
| 4 | xmlns:manageEvent="urn:ietf:params:xml:ns:netmod:notification" |
| 5 | xmlns:yang="urn:ietf:params:xml:ns:yang:ietf-yang-types" |
| 6 | xmlns:ncEvent="urn:ietf:params:xml:ns:netconf:notification:1.0"> |
| 7 | <namespace uri="urn:ietf:params:xml:ns:netmod:notification"/> |
| 8 | <prefix value="manageEvent"/> |
| 9 | <import module="ietf-yang-types"> |
| 10 | <prefix value="yang"/> |
| 11 | </import> |
| 12 | <import module="notifications"> |
| 13 | <prefix value="ncEvent"/> |
| 14 | </import> |
| 15 | <organization> |
| 16 | <text>IETF NETCONF WG</text> |
| 17 | </organization> |
| 18 | <contact> |
| 19 | <text>netconf@ietf.org</text> |
| 20 | </contact> |
| 21 | <description> |
| 22 | <text>Conversion of the 'manageEvent' XSD in the NETCONF |
| 23 | Notifications RFC.</text> |
| 24 | </description> |
| 25 | <reference> |
| 26 | <text>RFC 5277</text> |
| 27 | </reference> |
| 28 | <revision date="2008-07-14"> |
| 29 | <description> |
| 30 | <text>RFC 5277 version.</text> |
| 31 | </description> |
| 32 | </revision> |
| 33 | <container name="netconf"> |
| 34 | <description> |
| 35 | <text>Top-level element in the notification namespace</text> |
| 36 | </description> |
| 37 | <config value="false"/> |
| 38 | <container name="streams"> |
| 39 | <description> |
| 40 | <text>The list of event streams supported by the system. When |
| 41 | a query is issued, the returned set of streams is |
| 42 | determined based on user privileges.</text> |
| 43 | </description> |
| 44 | <list name="stream"> |
| 45 | <description> |
| 46 | <text>Stream name, description and other information.</text> |
| 47 | </description> |
| 48 | <key value="name"/> |
| 49 | <min-elements value="1"/> |
| 50 | <leaf name="name"> |
| 51 | <description> |
| 52 | <text>The name of the event stream. If this is the default |
| 53 | NETCONF stream, this must have the value 'NETCONF'.</text> |
| 54 | </description> |
| 55 | <type name="ncEvent:streamNameType"/> |
| 56 | </leaf> |
| 57 | <leaf name="description"> |
| 58 | <description> |
| 59 | <text>A description of the event stream, including such |
| 60 | information as the type of events that are sent over |
| 61 | this stream.</text> |
| 62 | </description> |
| 63 | <type name="string"/> |
| 64 | <mandatory value="true"/> |
| 65 | </leaf> |
| 66 | <leaf name="replaySupport"> |
| 67 | <description> |
| 68 | <text>A description of the event stream, including such |
| 69 | information as the type of events that are sent over |
| 70 | this stream.</text> |
| 71 | </description> |
| 72 | <type name="boolean"/> |
| 73 | <mandatory value="true"/> |
| 74 | </leaf> |
| 75 | <leaf name="replayLogCreationTime"> |
| 76 | <description> |
| 77 | <text>The timestamp of the creation of the log used to support |
| 78 | the replay function on this stream. Note that this might |
| 79 | be earlier then the earliest available notification in |
| 80 | the log. This object is updated if the log resets for |
| 81 | some reason. This object MUST be present if replay is |
| 82 | supported.</text> |
| 83 | </description> |
| 84 | <type name="yang:date-and-time"/> |
| 85 | </leaf> |
| 86 | </list> |
| 87 | </container> |
| 88 | </container> |
| 89 | <notification name="replayComplete"> |
| 90 | <description> |
| 91 | <text>This notification is sent to signal the end of a replay |
| 92 | portion of a subscription.</text> |
| 93 | </description> |
| 94 | </notification> |
| 95 | <notification name="notificationComplete"> |
| 96 | <description> |
| 97 | <text>This notification is sent to signal the end of a notification |
| 98 | subscription. It is sent in the case that stopTime was |
| 99 | specified during the creation of the subscription..</text> |
| 100 | </description> |
| 101 | </notification> |
| 102 | </module> |