-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathdraft-ietf-netconf-yang-notifications-versioning-07.txt
1736 lines (1286 loc) · 62.2 KB
/
draft-ietf-netconf-yang-notifications-versioning-07.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Network Working Group T. Graf
Internet-Draft Swisscom
Intended status: Standards Track B. Claise
Expires: 21 July 2025 Huawei
A. Huang Feng
INSA-Lyon
17 January 2025
Support of Versioning in YANG Notifications Subscription
draft-ietf-netconf-yang-notifications-versioning-07
Abstract
This document extends the YANG notifications subscription mechanism
to specify the YANG module semantic version at the subscription.
Then, a new extension with the revision and the semantic version of
the YANG push subscription state change notification is proposed.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 21 July 2025.
Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
Graf, et al. Expires 21 July 2025 [Page 1]
Internet-Draft YANG Notifications Versioning January 2025
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Extend the Datastore Selection . . . . . . . . . . . . . . . 4
3. Extend the Subscription State Change Notifications . . . . . 6
4. Discovering "ietf-yang-push-revision" Support . . . . . . . . 8
5. The "ietf-yang-push-revision" Module . . . . . . . . . . . . 10
5.1. Data Model Overview . . . . . . . . . . . . . . . . . . . 10
5.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 21
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
6.1. IETF XML Registry . . . . . . . . . . . . . . . . . . . . 27
6.2. YANG Module Name . . . . . . . . . . . . . . . . . . . . 27
7. Operational Considerations . . . . . . . . . . . . . . . . . 27
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 27
8.1. Huawei VRP . . . . . . . . . . . . . . . . . . . . . . . 27
8.2. 6WIND VSR . . . . . . . . . . . . . . . . . . . . . . . . 28
8.3. Cisco IOS XR . . . . . . . . . . . . . . . . . . . . . . 28
9. Security Considerations . . . . . . . . . . . . . . . . . . . 28
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 28
11.1. Normative References . . . . . . . . . . . . . . . . . . 28
11.2. Informative References . . . . . . . . . . . . . . . . . 29
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction
In order to process the newly received YANG push notification
messages described in section 3.7 of [RFC8641] without querying the
Publisher IETF-YANG-LIBRARY each time to understand whether the YANG
module(s) semantic has changed at the YANG push receiver, a semantic
reference to the YANG module and the XPath or subtree is needed to
determine the data types for each field and which part of the YANG
module the metrics are expose from.
This specification applies to the YANG push configured subscriptions
defined in Section 2.5 of [RFC8639], where a publisher is configured
to stream notification out of band, as opposed to dynamic
subscriptions defined in Section 2.4 of [RFC8639], where the
Graf, et al. Expires 21 July 2025 [Page 2]
Internet-Draft YANG Notifications Versioning January 2025
subscriber can initiate and modify the subscription dynamically in-
band. In the latter case, the subscriber knows already all the
subscriber YANG-related information, which it has to know in order to
configure the subscription.
This semantic reference is available when the subscription is
established as described in Section 3.6 of [RFC8641] and being
streamed from the publisher to receiver with the subscription state
change notifications described in Section 2.7 of [RFC8639] where for
each subscription a locally unique subscription ID described in
Section 4.3.2 of [RFC8641] is being issued and streamed as metadata
with the notification message in the YANG push message header.
The semantics can change between different YANG module revisions.
The YANG module version statement is specified in Section 7.1.2 of
[RFC6020] and states that the newer revision needs to be backward
compatible to the previous revision. Section 3.1 of
[I-D.ietf-netmod-yang-module-versioning] specifies that newer
semantic versions introduced in [I-D.ietf-netmod-yang-semver] MAY not
be backward compatible to the previous version when indicated with
non-backwards-compatible keyword.
The YANG notifications subscription mechanism defined in [RFC8641]
does not allow to specify the YANG module revision. When a network
node is upgraded, the subscribed YANG module revision MAY have
updated and might, consequently, break the data processing pipeline
since the YANG push receiver may not be aware of this change.
This documents extends the current YANG notifications subscription
mechanism to allow to subscribe to a specific revision or latest YANG
module semantic version to which the YANG module version needs to be
backward compatible to.
The subscription state change "subscription-started" and
"subscription-modified" notification messages are also extended to
include the YANG module revision, revision-label, and YANG library
content-id. Changes in the revision and revision-label fields allow
a YANG-Push receiver to detect whenever the subscribed YANG module
has changed. Changes in the yang-library-content-id that YANG
module(s) on the network management server of the YANG-Push publisher
has/have changed.
Graf, et al. Expires 21 July 2025 [Page 3]
Internet-Draft YANG Notifications Versioning January 2025
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The terms "YANG library" and "YANG library content identifier" are
used as defined in [RFC8525].
2. Extend the Datastore Selection
The YANG notifications subscription OPTIONALLY can be restricted to
the following YANG module revision for future capabilities:
module: Restricts the subscription to one or more YANG module names
with revision and revision-label together for the related streamed
content.
revision: Restricts the subscription to a specific YANG module
revision. Example: "2014-05-08".
revision-label: Restricts the subscription to the latest compatible
YANG module semantic version referenced to. Example: "2.0.0".
When the NETCONF client creates or modifies the subscription using
the RPCs establish-subscription and modify-subscription and the
NETCONF server does not support the revision, the revision-label or
the combination of revision and revision-label specified in the RPC
request, the NETCONF server MUST return an RPC reply including an
<rpc-error> element as defined in Section 4.3 of [RFC6241] with the
error information populated as follows:
* an "error-type" node of "application".
* an "error-tag" node whose value is a string that corresponds to an
identity associated with the error.
Graf, et al. Expires 21 July 2025 [Page 4]
Internet-Draft YANG Notifications Versioning January 2025
+==========================================+==================+
| Error identity | Uses "error-tag" |
+==========================================+==================+
| revision-unsupported | invalid-value |
+------------------------------------------+------------------+
| revision-label-unsupported | invalid-value |
+------------------------------------------+------------------+
| incompatible-revision-and-revision-label | invalid-value |
+------------------------------------------+------------------+
Table 1: General Subscription Error Identities and
Associated "error-tag" Use
Figure 1 provides an example of a "establish-subscription" RPC call
with YANG revision and datastore-xpath-filter for periodical
subscription. Figure 2 shows the response when the RPC has been
accepted by the NETCONF server and Figure 3 the error sent by the
NETCONF server when the revision is not supported.
<netconf:rpc message-id="101"
xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0">
<establish-subscription
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications"
xmlns:yp="urn:ietf:params:xml:ns:yang:ietf-yang-push">
xmlns:ypr="urn:ietf:params:xml:ns:yang:ietf-yang-push-revision">
<yp:datastore
xmlns:ds="urn:ietf:params:xml:ns:yang:ietf-datastores">
ds:operational
</yp:datastore>
<yp:datastore-xpath-filter
xmlns:ex="https://example.com/sample-data/1.0">
/ex:foo
</yp:datastore-xpath-filter>
<ypr:module-version>
<ypr:module-name>ex:foo</ypr:module-name>
<ypr:revision>2023-09-17</ypr:revision>
</ypr:module-version>
<yp:periodic>
<yp:period>500</yp:period>
</yp:periodic>
</establish-subscription>
</netconf:rpc>
Figure 1: RPC Example for an establish-subscription
Graf, et al. Expires 21 July 2025 [Page 5]
Internet-Draft YANG Notifications Versioning January 2025
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<id
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
52
</id>
</rpc-reply>
Figure 2: RPC Example for a positive establish-subscription response
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
xmlns:yp="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-path xmlns:ypr="urn:ietf:params:xml:ns:yang:ietf-yang-push-revision">
<error-info>
<yp:establish-subscription-error-datastore>
<yp:reason xmlns:ypr="urn:ietf:params:xml:ns:yang:ietf-yang-push-revision">
ypr:revision-unsupported
</yp:reason>
</yp:establish-subscription-error-datastore>
</error-info>
</rpc-error>
</rpc-reply>
Figure 3: RPC Example for an error establish-subscription response
3. Extend the Subscription State Change Notifications
Besides the Subscription ID and the xpath or sub-tree filter
reference as described in Section 2.7 of [RFC8639], the following
metadata objects are part of a "subscription-started" or
"subscription-modified" subscription state change notification.
module: Describes the YANG module names for the related streamed
content.
revision: Describes the YANG module revision as specified in
Section 7.1.9 of [RFC6020] for the related streamed content.
revision-label: Describes the YANG module semantic version as
specified in [I-D.ietf-netmod-yang-semver] for the related
streamed content.
yang-library-content-id: Contains the YANG library content
Graf, et al. Expires 21 July 2025 [Page 6]
Internet-Draft YANG Notifications Versioning January 2025
identifier [RFC8525] which is an implementation-specific
identifier representing the current information in the YANG
library on a specific server.
Figure 4 provides an example of a "subscription-modified"
subscription state change notification message with the YANG module
name, revision, revision label and datastore-xpath-filter for
tracking the operational status of a single Ethernet interface (per
[RFC8343]). This subscription state change notification message is
encoded XML [W3C.REC-xml-20081126] over the Network Configuration
Protocol (NETCONF) as per [RFC8640].
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2023-01-03T10:00:00Z</eventTime>
<subscription-modified
xmlns="urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications">
<id>101</id>
<stream-xpath-filter
xmlns:int="urn:ietf:params:xml:ns:yang:ietf-interfaces">
/int:interfaces
</stream-xpath-filter>
<stream>NETCONF</stream>
<module-version
xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push-revision">
<module-name>ietf-interfaces</module-name>
<revision>2018-02-20</revision>
<revision-label>2.0.0</revision-label>
<yang-library-content-id>1</yang-library-content-id>
</module-version>
</subscription-modified>
</notification>
Figure 4: XML Push Example for a subscription-modified
notification message
Figure 5 provides an example of a JSON encoded, [RFC8259],
subscription state change notification message over HTTPS-based
[I-D.ietf-netconf-https-notif] or UDP-based
[I-D.ietf-netconf-udp-notif] transport for the same subscription.
Graf, et al. Expires 21 July 2025 [Page 7]
Internet-Draft YANG Notifications Versioning January 2025
{
"ietf-restconf:notification" : {
"eventTime": "2023-01-03T10:00:00Z",
"ietf-subscribed-notifications:subscription-modified": {
"id": 101,
"stream-xpath-filter": "/ietf-interfaces:interfaces",
"stream": "NETCONF",
"ietf-yang-push-revision:module-version": [{
"module-name": "ietf-interfaces"
"revision": "2018-02-20",
"revision-label": "2.0.0",
"yang-library-content-id": "1",
}],
}
}
}
Figure 5: JSON Push Example for a subscription-modified
notification message
4. Discovering "ietf-yang-push-revision" Support
A client can discover the support of 'ietf-yang-push-revision'model
through the capabilities model defined in [RFC9196]. This documents
extends the 'ietf-notification-capabilities' model with:
* A leaf 'yang-push-module-revision-supported', stating that the
YANG-Push subscription state change notifications are extended
with revision, revision-label and yang-library-content-id
extensions.
The YANG models defined in Section 5.2 augments the 'ietf-
notification-capabilities' model with the leaf listed above.
Graf, et al. Expires 21 July 2025 [Page 8]
Internet-Draft YANG Notifications Versioning January 2025
module: ietf-system-capabilities
+--ro system-capabilities
+--ro datastore-capabilities* [datastore]
| +--ro datastore
| | -> /yanglib:yang-library/datastore/name
| +--ro per-node-capabilities* []
| +--ro (node-selection)?
| | +--:(node-selector)
| | +--ro node-selector?
| | nacm:node-instance-identifier
| +--ro notc:subscription-capabilities
| +--ro notc:max-nodes-per-update? uint32
| +--ro notc:periodic-notifications-supported?
| | notification-support
| +--ro (notc:update-period)?
| | +--:(notc:minimum-update-period)
| | | +--ro notc:minimum-update-period? uint32
| | +--:(notc:supported-update-period)
| | +--ro notc:supported-update-period* uint32
| +--ro notc:on-change-supported?
| | notification-support {yp:on-change}?
| +--ro notc:minimum-dampening-period? uint32
| | {yp:on-change}?
| +--ro notc:supported-excluded-change-type* union
| {yp:on-change}?
+--ro notc:subscription-capabilities
+--ro notc:max-nodes-per-update? uint32
+--ro notc:periodic-notifications-supported?
| notification-support
+--ro (notc:update-period)?
| +--:(notc:minimum-update-period)
| | +--ro notc:minimum-update-period? uint32
| +--:(notc:supported-update-period)
| +--ro notc:supported-update-period* uint32
+--ro notc:on-change-supported?
| notification-support {yp:on-change}?
+--ro notc:minimum-dampening-period? uint32
| {yp:on-change}?
+--ro notc:supported-excluded-change-type* union
| {yp:on-change}?
+--ro ypr:yang-push-module-revision-supported? boolean
{yang-push-revision-supported}?
This model can be retrieved via a NETCONF <get> RPC.
Graf, et al. Expires 21 July 2025 [Page 9]
Internet-Draft YANG Notifications Versioning January 2025
5. The "ietf-yang-push-revision" Module
5.1. Data Model Overview
This YANG module augments the "ietf-yang-push" module with the
module-name, revision, revision-label and yang-library-content-id in
the "subscription-started" and "subscription-modified" subscription
state change notifications and the ability to define the "revision"
and "revision-label" in the "establish-subscription" and "modify-
subscription" RPCs in the datastore push subscription.
5.1.1. Tree View
The following is the YANG tree diagram [RFC8340] for the ietf-yang-
push-revision YANG module
Graf, et al. Expires 21 July 2025 [Page 10]
Internet-Draft YANG Notifications Versioning January 2025
module: ietf-yang-push-revision
augment /sn:establish-subscription/sn:input:
+---w module-version-config* [module-name]
{yang-push-revision-supported}?
+---w module-name yang:yang-identifier
+---w revision? rev:revision-date
+---w revision-label? ysver:version
augment /sn:modify-subscription/sn:input:
+---w module-version-config* [module-name]
{yang-push-revision-supported}?
+---w module-name yang:yang-identifier
+---w revision? rev:revision-date
+---w revision-label? ysver:version
augment /sn:subscription-started:
+--ro module-version* [module-name]
| {yang-push-revision-supported}?
| +--ro module-name yang:yang-identifier
| +--ro revision rev:revision-date
| +--ro revision-label? ysver:version
+--ro yang-library-content-id? -> /yanglib:yang-library/content-id
{yang-push-revision-supported}?
augment /sn:subscription-modified:
+--ro module-version* [module-name]
| {yang-push-revision-supported}?
| +--ro module-name yang:yang-identifier
| +--ro revision rev:revision-date
| +--ro revision-label? ysver:version
+--ro yang-library-content-id? -> /yanglib:yang-library/content-id
{yang-push-revision-supported}?
augment /sn:subscriptions/sn:subscription:
+--rw module-version-config* [module-name]
{yang-push-revision-supported}?
+--rw module-name yang:yang-identifier
+--rw revision? rev:revision-date
+--rw revision-label? ysver:version
augment /sysc:system-capabilities/notc:subscription-capabilities:
+--ro yang-push-module-revision-supported? boolean
{yang-push-revision-supported}?
5.1.2. Full Tree View
The following is the YANG tree diagram [RFC8340] for the ietf-yang-
push-revision augmentation within the ietf-subscribed-notifications,
including the RPCs and notifications.
Graf, et al. Expires 21 July 2025 [Page 11]
Internet-Draft YANG Notifications Versioning January 2025
module: ietf-yang-push
rpcs:
+---x resync-subscription {on-change}?
+---w input
+---w id sn:subscription-id
notifications:
+---n push-update
| +--ro id? sn:subscription-id
| +--ro datastore-contents? <anydata>
| +--ro incomplete-update? empty
+---n push-change-update {on-change}?
+--ro id? sn:subscription-id
+--ro datastore-changes
| +--ro yang-patch
| +--ro patch-id string
| +--ro comment? string
| +--ro edit* [edit-id]
| +--ro edit-id string
| +--ro operation enumeration
| +--ro target target-resource-offset
| +--ro point? target-resource-offset
| +--ro where? enumeration
| +--ro value? <anydata>
+--ro incomplete-update? empty
module: ietf-subscribed-notifications
+--ro streams
| +--ro stream* [name]
| +--ro name string
| +--ro description? string
| +--ro replay-support? empty {replay}?
| +--ro replay-log-creation-time yang:date-and-time {replay}?
| +--ro replay-log-aged-time? yang:date-and-time {replay}?
+--rw filters
| +--rw stream-filter* [name]
| | +--rw name string
| | +--rw (filter-spec)?
| | +--:(stream-subtree-filter)
| | | +--rw stream-subtree-filter? <anydata> {subtree}?
| | +--:(stream-xpath-filter)
| | +--rw stream-xpath-filter? yang:xpath1.0 {xpath}?
| +--rw yp:selection-filter* [filter-id]
| +--rw yp:filter-id string
| +--rw (yp:filter-spec)?
| +--:(yp:datastore-subtree-filter)
| | +--rw yp:datastore-subtree-filter? <anydata>
Graf, et al. Expires 21 July 2025 [Page 12]
Internet-Draft YANG Notifications Versioning January 2025
| | {sn:subtree}?
| +--:(yp:datastore-xpath-filter)
| +--rw yp:datastore-xpath-filter? yang:xpath1.0
| {sn:xpath}?
+--rw subscriptions
+--rw subscription* [id]
+--rw id
| subscription-id
+--rw (target)
| +--:(stream)
| | +--rw (stream-filter)?
| | | +--:(by-reference)
| | | | +--rw stream-filter-name
| | | | stream-filter-ref
| | | +--:(within-subscription)
| | | +--rw (filter-spec)?
| | | +--:(stream-subtree-filter)
| | | | +--rw stream-subtree-filter?
| | | | <anydata> {subtree}?
| | | +--:(stream-xpath-filter)
| | | +--rw stream-xpath-filter?
| | | yang:xpath1.0 {xpath}?
| | +--rw stream
| | | stream-ref
| | +--ro replay-start-time?
| | | yang:date-and-time {replay}?
| | +--rw configured-replay? empty
| | {configured,replay}?
| +--:(yp:datastore)
| +--rw yp:datastore
| | identityref
| +--rw (yp:selection-filter)?
| +--:(yp:by-reference)
| | +--rw yp:selection-filter-ref
| | selection-filter-ref
| +--:(yp:within-subscription)
| +--rw (yp:filter-spec)?
| +--:(yp:datastore-subtree-filter)
| | +--rw yp:datastore-subtree-filter?
| | <anydata> {sn:subtree}?
| +--:(yp:datastore-xpath-filter)
| +--rw yp:datastore-xpath-filter?
| yang:xpath1.0 {sn:xpath}?
+--rw stop-time?
| yang:date-and-time
+--rw dscp?
| inet:dscp {dscp}?
+--rw weighting? uint8
Graf, et al. Expires 21 July 2025 [Page 13]
Internet-Draft YANG Notifications Versioning January 2025
| {qos}?
+--rw dependency?
| subscription-id {qos}?
+--rw transport?
| transport {configured}?
+--rw encoding?
| encoding
+--rw purpose? string
| {configured}?
+--rw (notification-message-origin)? {configured}?
| +--:(interface-originated)
| | +--rw source-interface?
| | if:interface-ref {interface-designation}?
| +--:(address-originated)
| +--rw source-vrf?
| | -> /ni:network-instances/network-instance/name
| | {supports-vrf}?
| +--rw source-address?
| inet:ip-address-no-zone
+--ro configured-subscription-state?
| enumeration {configured}?
+--rw receivers
| +--rw receiver* [name]
| +--rw name string
| +--ro sent-event-records?
| | yang:zero-based-counter64
| +--ro excluded-event-records?
| | yang:zero-based-counter64
| +--ro state enumeration
| +---x reset {configured}?
| +--ro output
| +--ro time yang:date-and-time
+--rw ypr:module-version-config* [module-name]
| {yang-push-revision-supported}?
| +--rw ypr:module-name yang:yang-identifier
| +--rw ypr:revision? rev:revision-date
| +--rw ypr:revision-label? ysver:version
+--rw (yp:update-trigger)?
+--:(yp:periodic)
| +--rw yp:periodic!
| +--rw yp:period centiseconds
| +--rw yp:anchor-time? yang:date-and-time
+--:(yp:on-change) {on-change}?
+--rw yp:on-change!
+--rw yp:dampening-period? centiseconds
+--rw yp:sync-on-start? boolean
+--rw yp:excluded-change* change-type
Graf, et al. Expires 21 July 2025 [Page 14]
Internet-Draft YANG Notifications Versioning January 2025
rpcs:
+---x establish-subscription
| +---w input
| | +---w (target)
| | | +--:(stream)
| | | | +---w (stream-filter)?
| | | | | +--:(by-reference)
| | | | | | +---w stream-filter-name
| | | | | | stream-filter-ref
| | | | | +--:(within-subscription)
| | | | | +---w (filter-spec)?
| | | | | +--:(stream-subtree-filter)
| | | | | | +---w stream-subtree-filter?
| | | | | | <anydata> {subtree}?
| | | | | +--:(stream-xpath-filter)
| | | | | +---w stream-xpath-filter?
| | | | | yang:xpath1.0 {xpath}?
| | | | +---w stream
| | | | | stream-ref
| | | | +---w replay-start-time?
| | | | yang:date-and-time {replay}?
| | | +--:(yp:datastore)
| | | +---w yp:datastore
| | | | identityref
| | | +---w (yp:selection-filter)?
| | | +--:(yp:by-reference)
| | | | +---w yp:selection-filter-ref
| | | | selection-filter-ref
| | | +--:(yp:within-subscription)
| | | +---w (yp:filter-spec)?
| | | +--:(yp:datastore-subtree-filter)
| | | | +---w yp:datastore-subtree-filter?
| | | | <anydata> {sn:subtree}?
| | | +--:(yp:datastore-xpath-filter)
| | | +---w yp:datastore-xpath-filter?
| | | yang:xpath1.0 {sn:xpath}?
| | +---w stop-time?
| | | yang:date-and-time
| | +---w dscp?
| | | inet:dscp {dscp}?
| | +---w weighting? uint8
| | | {qos}?
| | +---w dependency?
| | | subscription-id {qos}?
| | +---w encoding?
| | | encoding
| | +---w ypr:module-version-config* [module-name]
| | | {yang-push-revision-supported}?
Graf, et al. Expires 21 July 2025 [Page 15]
Internet-Draft YANG Notifications Versioning January 2025
| | | +---w ypr:module-name yang:yang-identifier
| | | +---w ypr:revision? rev:revision-date
| | | +---w ypr:revision-label? ysver:version
| | +---w (yp:update-trigger)?
| | +--:(yp:periodic)
| | | +---w yp:periodic!
| | | +---w yp:period centiseconds
| | | +---w yp:anchor-time? yang:date-and-time
| | +--:(yp:on-change) {on-change}?
| | +---w yp:on-change!
| | +---w yp:dampening-period? centiseconds
| | +---w yp:sync-on-start? boolean
| | +---w yp:excluded-change* change-type
| +--ro output
| +--ro id subscription-id
| +--ro replay-start-time-revision? yang:date-and-time
| {replay}?
+---x modify-subscription
| +---w input
| +---w id
| | subscription-id
| +---w (target)
| | +--:(stream)
| | | +---w (stream-filter)?
| | | +--:(by-reference)
| | | | +---w stream-filter-name
| | | | stream-filter-ref
| | | +--:(within-subscription)
| | | +---w (filter-spec)?
| | | +--:(stream-subtree-filter)
| | | | +---w stream-subtree-filter?
| | | | <anydata> {subtree}?
| | | +--:(stream-xpath-filter)
| | | +---w stream-xpath-filter?
| | | yang:xpath1.0 {xpath}?
| | +--:(yp:datastore)
| | +---w yp:datastore
| | | identityref
| | +---w (yp:selection-filter)?
| | +--:(yp:by-reference)
| | | +---w yp:selection-filter-ref
| | | selection-filter-ref
| | +--:(yp:within-subscription)
| | +---w (yp:filter-spec)?
| | +--:(yp:datastore-subtree-filter)
| | | +---w yp:datastore-subtree-filter?
| | | <anydata> {sn:subtree}?
| | +--:(yp:datastore-xpath-filter)
Graf, et al. Expires 21 July 2025 [Page 16]
Internet-Draft YANG Notifications Versioning January 2025
| | +---w yp:datastore-xpath-filter?
| | yang:xpath1.0 {sn:xpath}?
| +---w stop-time?
| | yang:date-and-time
| +---w ypr:module-version-config* [module-name]
| | {yang-push-revision-supported}?
| | +---w ypr:module-name yang:yang-identifier
| | +---w ypr:revision? rev:revision-date
| | +---w ypr:revision-label? ysver:version
| +---w (yp:update-trigger)?
| +--:(yp:periodic)
| | +---w yp:periodic!
| | +---w yp:period centiseconds
| | +---w yp:anchor-time? yang:date-and-time
| +--:(yp:on-change) {on-change}?
| +---w yp:on-change!
| +---w yp:dampening-period? centiseconds
+---x delete-subscription
| +---w input
| +---w id subscription-id
+---x kill-subscription
+---w input
+---w id subscription-id
notifications:
+---n replay-completed {replay}?
| +--ro id subscription-id
+---n subscription-completed {configured}?
| +--ro id subscription-id
+---n subscription-modified
| +--ro id
| | subscription-id
| +--ro (target)
| | +--:(stream)
| | | +--ro (stream-filter)?
| | | | +--:(by-reference)
| | | | | +--ro stream-filter-name
| | | | | stream-filter-ref
| | | | +--:(within-subscription)
| | | | +--ro (filter-spec)?
| | | | +--:(stream-subtree-filter)
| | | | | +--ro stream-subtree-filter?
| | | | | <anydata> {subtree}?
| | | | +--:(stream-xpath-filter)
| | | | +--ro stream-xpath-filter?
| | | | yang:xpath1.0 {xpath}?
| | | +--ro stream
| | | | stream-ref
Graf, et al. Expires 21 July 2025 [Page 17]
Internet-Draft YANG Notifications Versioning January 2025
| | | +--ro replay-start-time?
| | | yang:date-and-time {replay}?
| | +--:(yp:datastore)
| | +--ro yp:datastore
| | | identityref
| | +--ro (yp:selection-filter)?
| | +--:(yp:by-reference)
| | | +--ro yp:selection-filter-ref
| | | selection-filter-ref
| | +--:(yp:within-subscription)
| | +--ro (yp:filter-spec)?
| | +--:(yp:datastore-subtree-filter)
| | | +--ro yp:datastore-subtree-filter?
| | | <anydata> {sn:subtree}?
| | +--:(yp:datastore-xpath-filter)
| | +--ro yp:datastore-xpath-filter?
| | yang:xpath1.0 {sn:xpath}?
| +--ro stop-time?
| | yang:date-and-time
| +--ro dscp?
| | inet:dscp {dscp}?
| +--ro weighting? uint8
| | {qos}?
| +--ro dependency?
| | subscription-id {qos}?
| +--ro transport?
| | transport {configured}?
| +--ro encoding? encoding
| +--ro purpose? string
| | {configured}?
| +--ro ypr:module-version* [module-name]
| | {yang-push-revision-supported}?
| | +--ro ypr:module-name yang:yang-identifier
| | +--ro ypr:revision rev:revision-date
| | +--ro ypr:revision-label? ysver:version
| +--ro (yp:update-trigger)?
| +--:(yp:periodic)
| | +--ro yp:periodic!
| | +--ro yp:period centiseconds
| | +--ro yp:anchor-time? yang:date-and-time
| +--:(yp:on-change) {on-change}?
| +--ro yp:on-change!
| +--ro yp:dampening-period? centiseconds
| +--ro yp:sync-on-start? boolean