3 namespace "urn:ietf:params:xml:ns:netconf:notification:1.0";
6 import ietf-yang-types {
13 "netconf@ops.ietf.org";
15 "Conversion of the 'ncEvent' XSD in the
16 NETCONF Notifications RFC.";
17 reference "RFC 5277.";
21 "First step to a common notification yang.";
23 "RFC 5277: NETCONF Event Notifications";
29 "RFC 5277: NETCONF Event Notifications";
32 typedef streamNameType {
35 "The name of an event stream.";
38 rpc create-subscription {
40 "The command to create a notification subscription. It
41 takes as argument the name of the notification stream
42 and filter. Both of those options limit the content of
43 the subscription. In addition, there are two time-related
44 parameters, startTime and stopTime, which can be used to
45 select the time interval of interest to the notification
52 "An optional parameter that indicates which stream of events
53 is of interest. If not present, then events in the default
54 NETCONF stream will be sent.";
58 "An optional parameter that indicates which subset of all
59 possible events is of interest. The format of this
60 parameter is the same as that of the filter parameter
61 in the NETCONF protocol operations. If not present,
62 all events not precluded by other parameters will
66 type yang:date-and-time;
68 "A parameter used to trigger the replay feature and
69 indicates that the replay should start at the time
70 specified. If start time is not present, this is not a
71 replay subscription.";
74 type yang:date-and-time;
76 "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.";
84 container notification {
87 "internal struct to start a notification";
89 type yang:date-and-time;
92 "The time the event was generated by the event source. This
93 parameter is of type dateTime and compliant to [RFC3339].
94 Implementations must support time zones.";