1 <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1">
2 <data xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">module notifications {
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.";
25 typedef streamNameType {
28 "The name of an event stream.";
31 container notification {
34 "internal struct to start a notification";
36 type yang:date-and-time;
41 rpc create-subscription {
43 "The command to create a notification subscription. It
44 takes as argument the name of the notification stream
45 and filter. Both of those options limit the content of
46 the subscription. In addition, there are two time-related
47 parameters, startTime and stopTime, which can be used to
48 select the time interval of interest to the notification
55 "An optional parameter that indicates which stream of events
56 is of interest. If not present, then events in the default
57 NETCONF stream will be sent.";
62 "An optional parameter that indicates which subset of all
63 possible events is of interest. The format of this
64 parameter is the same as that of the filter parameter
65 in the NETCONF protocol operations. If not present,
66 all events not precluded by other parameters will
71 type yang:date-and-time;
73 "A parameter used to trigger the replay feature and
74 indicates that the replay should start at the time
75 specified. If start time is not present, this is not a
76 replay subscription.";
80 type yang:date-and-time;
82 "An optional parameter used with the optional replay
83 feature to indicate the newest notifications of
84 interest. If stop time is not present, the notifications
85 will continue until the subscription is terminated.
86 Must be used with startTime.";