-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathdraft-tgraf-netconf-notif-sequencing-06.txt
896 lines (632 loc) · 31.1 KB
/
draft-tgraf-netconf-notif-sequencing-06.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
Network Working Group T. Graf
Internet-Draft Swisscom
Intended status: Standards Track J. Quilbeuf
Expires: 1 January 2025 Huawei
A. Huang Feng
INSA-Lyon
30 June 2024
Support of Hostname and Sequencing in YANG Notifications
draft-tgraf-netconf-notif-sequencing-06
Abstract
This document specifies a new YANG module that augments the NETCONF
Event Notification header to support the hostname and sequence number
to identify from which network node and at which time the message was
published. This allows the collector to recognize loss, delay and
reordering between the publisher and the downstream system storing
the messages.
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 1 January 2025.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
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
Graf, et al. Expires 1 January 2025 [Page 1]
Internet-Draft YANG Notifications Sequencing June 2024
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
2. Extend the YANG Notification Header . . . . . . . . . . . . . 3
2.1. Extension for NETCONF Event Notifications . . . . . . . . 4
2.2. Extension for YANG-Push . . . . . . . . . . . . . . . . . 5
3. YANG Module for Event Notifications . . . . . . . . . . . . . 7
3.1. YANG Tree Diagram . . . . . . . . . . . . . . . . . . . . 8
3.2. Full Tree View . . . . . . . . . . . . . . . . . . . . . 8
3.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 9
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 13
4.1. 6WIND VSR . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
6.1. IETF XML Registry . . . . . . . . . . . . . . . . . . . . 13
6.2. YANG Module Name . . . . . . . . . . . . . . . . . . . . 13
6.3. NETCONF Capability URNs Registry . . . . . . . . . . . . 14
7. Operational Considerations . . . . . . . . . . . . . . . . . 14
7.1. SysName Correlation . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
NETCONF Event Notifications [RFC5277] and YANG-Push [RFC8641] allow
NETCONF [RFC6241] servers and YANG-Push publishers to send
notifications to a data collection. In the metadata of the event
notification header, only the eventTime is present indicating at
which time the notification message was published. For YANG-Push
notifications, the subscription ID is added to the "push-update" and
"push-change-update" notification messages allowing the YANG-Push
receiver to map and recognize which Xpath or subtree is bound to the
subscription.
When the NETCONF event notification message is forwarded from the
receiver to another system, such as a messaging system or a time
series database, the transport context is lost since it is not part
of the NETCONF event notification message metadata. Therefore, the
downstream system is unable to associate the message to the
publishing process (the exporting router), nor able to detect message
loss or reordering.
Graf, et al. Expires 1 January 2025 [Page 2]
Internet-Draft YANG Notifications Sequencing June 2024
To correlate network data among different Network Telemetry planes as
described in Section 3.1 of [RFC9232] or among different YANG-Push
subscription types as defined in Section 3.1 of [RFC8641], a
reference to the node streaming the data is needed. This is
essential for understanding the timely relationship among these
different planes and YANG-Push subscription types.
Today, network operators work around this impediment by preserving
the transport source IP address and sequence numbers of the
publishing process. However, this implies encoding this information
in the NETCONF event notification message which impacts the semantic
readability of the message in the downstream system.
On top of that, the transport source IP address might not represent
the management IP address by which the YANG-Push publisher should be
known. In other terms, the source-host [RFC6470], which is the
"Address of the remote host for the session" might not be the
management IP address.
To overcome these issues, this document proposes extending the YANG
notification header with a sysName, the node's fully-qualified domain
name, and a sequence number as described in [RFC9187]. This allows
the downstream system to not only be able to identify from which
network node, subscription, and time the message was published but
also, the order of the published messages.
2. Extend the YANG Notification Header
NETCONF Event Notifications [RFC5277] and YANG-Push [RFC8641] uses
the same notification header that is described in Section 2.2.1 of
[RFC5277]. [I-D.ahuang-netconf-notif-yang] defines how these
notifications should be encoded in JSON and CBOR.
Besides the eventTime described in Section 2.2.1 of [RFC5277] the
following metadata objects are part of a notification message.
sysName: Describes the node's fully-qualified domain name according
to the 'sysName' object definition in [RFC1213] from where the
message was published from. This value is usually configured on
the node by the administrator to uniquely identify the node in the
network.
sequenceNumber: Generates a unique sequence number for each
published message by the publisher process. The number counts up
at every published notification message as described in [RFC9187].
Graf, et al. Expires 1 January 2025 [Page 3]
Internet-Draft YANG Notifications Sequencing June 2024
2.1. Extension for NETCONF Event Notifications
The Notification of NETCONF Event Notifications [RFC5277] uses a XML
structure that is defined in Section 2.2.1 of [RFC5277]. [RFC5277]
also defines the capability
"urn:ietf:params:netconf:capability:notification:1.0" allowing a
NETCONF client to know that the NETCONF server supports sending
notifications.
2.1.1. Notification header
An implementation supporting this document extends the notification
defined in Section 2.2.1 of [RFC5277] adding a sysName and a
sequenceNumber. Two more child nodes within the "notification"
container are expected, representing the sysName and the
sequenceNumber.
An example showing this extension in XML is provided in Figure 1:
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2007-07-08T00:10:00Z</eventTime>
<sysName xmlns="urn:ietf:params:xml:ns:yang:ietf-notification-sequencing">
example-router
</sysName>
<sequenceNumber xmlns="urn:ietf:params:xml:ns:yang:ietf-notification-sequencing">
187653
</sequenceNumber>
<event xmlns="http://example.com/event/1.0">
<eventClass>state</eventClass>
<reportingEntity>
<card>Ethernet0</card>
</reportingEntity>
<operState>enabled</operState>
</event>
</notification>
Figure 1: NETCONF Event Notification message
2.1.2. Capability exchange
This document also adds a new capability to NETCONF so that the
NETCONF server can notify the support of the sysName and
sequenceNumber to the NETCONF client.
When the NETCONF server supports this document, the following
capability is advertised:
urn:ietf:params:netconf:capability:notification-sysname-sequence:1.0
Graf, et al. Expires 1 January 2025 [Page 4]
Internet-Draft YANG Notifications Sequencing June 2024
The capability identifier is requested to IANA in Section 6.
In the capability exchange between the NETCONF client and server, the
server will announce this capability along with the supported
capabilities by the server as shown in the example in Figure 2.
<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>
urn:ietf:params:xml:ns:netconf:base:1.0
</capability>
<capability>
urn:ietf:params:netconf:capability:startup:1.0
</capability>
<capability>
urn:ietf:params:netconf:capability:notification:1.0
</capability>
<capability>
urn:ietf:params:netconf:capability:notification-sysname-sequence:1.0
</capability>
</capabilities>
<session-id>4</session-id>
</hello>
Figure 2: Example of a capability exchange.
2.2. Extension for YANG-Push
YANG-Push [RFC8641] uses the same structure defined in [RFC5277].
[RFC5277] defines the structure using XML encoding. For other YANG
encodings, [I-D.ahuang-netconf-notif-yang] describes how
notifications should be encoded in JSON and CBOR.
2.2.1. YANG-Push Notification header
An implementation supporting this document extends the notification
defined in Section 4 of [I-D.ahuang-netconf-notif-yang] adding a
sysName and a sequenceNumber. Two more child nodes within the
"notification" root container are expected, representing the sysName
and the sequenceNumber.
Figure 3 provides an example of a "push-update" notification with the
sysName and sequenceNumber. This examples is encoded in XML
[W3C.REC-xml-20081126].
Graf, et al. Expires 1 January 2025 [Page 5]
Internet-Draft YANG Notifications Sequencing June 2024
<notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<eventTime>2023-02-04T16:30:11.22Z</eventTime>
<sysName xmlns="urn:ietf:params:xml:ns:yang:ietf-notification-sequencing">
example-router
</sysName>
<sequenceNumber xmlns="urn:ietf:params:xml:ns:yang:ietf-notification-sequencing">
187653
</sequenceNumber>
<push-update xmlns="urn:ietf:params:xml:ns:yang:ietf-yang-push">
<id>1011</id>
<datastore-contents>
<interfaces xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
<interface>
<name>eth0</name>
<oper-status>up</oper-status>
</interface>
</interfaces>
</datastore-contents>
</push-update>
</notification>
Figure 3: YANG-Push Notification example encoded in XML
When the notifcation is encoded using JSON [RFC7951], the sysName and
the sequenceNumber are encoded at root container. An example is
shown in Figure 4.
{
"ietf-notification:notification": {
"eventTime": "2023-02-10T08:00:11.22Z",
"ietf-notification-sequencing:sysName":"example-router",
"ietf-notification-sequencing:sequenceNumber": 187653,
"ietf-yang-push:push-update": {
"id": 1011,
"datastore-contents": {
"ietf-interfaces:interfaces": [
{
"interface": {
"name": "eth0",
"oper-status": "up"
}
}
]
}
}
}
}
Graf, et al. Expires 1 January 2025 [Page 6]
Internet-Draft YANG Notifications Sequencing June 2024
Figure 4: YANG-Push Notification example encoded in JSON
When the notification is encoded in CBOR [RFC9254], the sysName and
the sequenceNumber are encoded at root container. An example is
shown in Figure 5 using CBOR diagnostic notation from Section 3.1 of
[RFC9254].
{
"ietf-notification:notification": {
"eventTime": "2023-02-10T08:00:11.22Z",
"ietf-notification-sequencing:sysName":"example-router",
"ietf-notification-sequencing:sequenceNumber": 187653,
"ietf-yang-push:push-update": {
"id": 1011,
"datastore-contents": {
"ietf-interfaces:interfaces": [
{
"interface": {
"name": "eth0",
"oper-status": "up"
}
}
]
}
}
}
}
Figure 5: YANG-Push Notification example in CBOR diagnostic notation.
2.2.2. YANG-Push capabilities
YANG-related system capabilites can be discovered by subscribing to
the datastore defined in [RFC9196]. This document augments the
"ietf-notification-capabilities" defined in Section 5 of [RFC9196] so
that the YANG-Push receiver can learn the capabilities defined in
this documents throught the datastore.
The definition of this YANG augmentation is specified in Section 3.
3. YANG Module for Event Notifications
Graf, et al. Expires 1 January 2025 [Page 7]
Internet-Draft YANG Notifications Sequencing June 2024
3.1. YANG Tree Diagram
This "ietf-notification-sequencing" YANG module augments the "ietf-
notification" YANG module specified in Section 5 of
[I-D.ahuang-netconf-notif-yang] adding the sysName and the
sequenceNumber leaves and augments "ietf-notification-capabilities"
defined in [RFC9196] to add a system level capability.
module: ietf-notification-sequencing
augment /sysc:system-capabilities/notc:subscription-capabilities:
+--ro sysname-sequence-supported? notification-support {sysname-sequence}?
augment-structure /inotif:notification:
+-- sysName inet:host
+-- sequenceNumber yang:counter32
3.2. Full Tree View
The following is the YANG tree diagram [RFC8340] for the "ietf-
notification" structure:
module: ietf-notification
structure notification:
+-- eventTime yang:date-and-time
+-- inotifseq:sysName inet:host
+-- inotifseq:sequenceNumber yang:counter32
The following YANG tree diagram [RFC8340] is the full tree of the
"ietf-notification-capabilities" YANG model:
Graf, et al. Expires 1 January 2025 [Page 8]
Internet-Draft YANG Notifications Sequencing June 2024
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 inotifseq:sysname-sequence-supported?
notification-support {sysname-sequence}?
3.3. YANG Module
The "ietf-notification-sequencing" augments the "ietf-notification"
and "ietf-notification-capabilities" YANG modules.
Graf, et al. Expires 1 January 2025 [Page 9]
Internet-Draft YANG Notifications Sequencing June 2024
<CODE BEGINS> file "[email protected]"
module ietf-notification-sequencing {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-notification-sequencing";
prefix inotifseq;
import ietf-inet-types {
prefix inet;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-yang-types {
prefix yang;
reference
"RFC 6991: Common YANG Data Types";
}
import ietf-notification {
prefix inotif;
reference
"draft-ahuang-netconf-notif-yang: NETCONF Event Notification YANG";
}
import ietf-system-capabilities {
prefix sysc;
reference
"RFC 9196: YANG Modules Describing Capabilities for
Systems and Datastore Update Notifications";
}
import ietf-notification-capabilities {
prefix notc;
reference
"RFC 9196: YANG Modules Describing Capabilities for
Systems and Datastore Update Notifications";
}
import ietf-yang-structure-ext {
prefix sx;
reference
"RFC 8791: YANG Data Structure Extensions";
}
organization "IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web: <http:/tools.ietf.org/wg/netconf/>
WG List: <mailto:[email protected]>
Authors: Thomas Graf
<mailto:[email protected]>
Jean Quilbeuf
<mailto:[email protected]>
Graf, et al. Expires 1 January 2025 [Page 10]
Internet-Draft YANG Notifications Sequencing June 2024
Alex Huang Feng
<mailto:[email protected]>";
description
"Defines NETCONF Event Notification structure with the sysName and
the sequenceNumber.
Copyright (c) 2024 IETF Trust and the persons identified as
authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license
terms contained in, the Revised BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the RFC
itself for full legal notices.";
revision 2023-05-29 {
description
"First revision";
reference
"RFC XXXX: YANG Notifications Sequencing";
}
feature sysname-sequence {
description
"This feature indicates that sysName and sequenceNumber are
supported in notifications.";
}
typedef notification-support {
type bits {
bit config-changes {
description
"The publisher is capable of sending
notifications for 'config true' nodes for the
relevant scope and subscription type.";
}
bit state-changes {
description
"The publisher is capable of sending
notifications for 'config false' nodes for the
relevant scope and subscription type.";
}
}
description
Graf, et al. Expires 1 January 2025 [Page 11]
Internet-Draft YANG Notifications Sequencing June 2024
"Redefition of the type 'notification-support' from
'ietf-notification-capabilities' module to be reusable in
other YANG modules.
Type for defining whether 'on-change' or
'periodic' notifications are supported for all data nodes,
'config false' data nodes, 'config true' data nodes, or
no data nodes.
The bits config-changes or state-changes have no effect
when they are set for a datastore or for a set of nodes
that does not contain nodes with the indicated config
value. In those cases, the effect is the same as if no
support was declared. One example of this is indicating
support for state-changes for a candidate datastore that
has no effect.";
reference
"RFC XXXX: YANG Notifications Sequencing
RFC 9196: YANG Modules Describing Capabilities for
Systems and Datastore Update Notifications";
}
sx:augment-structure "/inotif:notification" {
leaf sysName {
type inet:host;
mandatory true;
description
"Fully-qualified domain name of the node according to
[RFC1213]. This value is usually configured on the node
by the administrator to uniquely identify the node in
the network.";
}
leaf sequenceNumber {
type yang:counter32;
mandatory true;
description
"Unique sequence number as described in [RFC3339] for each
published message.";
}
}
augment "/sysc:system-capabilities/notc:subscription-capabilities" {
description
"Add system level capabilities";
leaf sysname-sequence-supported {
if-feature "sysname-sequence";
type notification-support;
description
Graf, et al. Expires 1 January 2025 [Page 12]
Internet-Draft YANG Notifications Sequencing June 2024
"Specifies whether the publisher supports exporting a
sysName and a sequenceNumber in notifications.";
reference
"RFC XXXX: YANG Notifications Sequencing";
}
}
}
<CODE ENDS>
4. Implementation Status
Note to the RFC-Editor: Please remove this section before publishing.
4.1. 6WIND VSR
6WIND implemented this document for a YANG-Push publisher on
UDP-based Transport for Configured Subscriptions
[I-D.ietf-netconf-udp-notif] in their VSR platform.
5. Security Considerations
The security considerations for the NETCONF Event notifications are
described in [RFC5277]. This documents adds no additional security
considerations.
6. IANA Considerations
6.1. IETF XML Registry
This document registers the following URIs in the "IETF XML Registry"
[RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-notification-sequencing
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
6.2. YANG Module Name
This document registers the following YANG modules in the "YANG
Module Names" registry [RFC6020]:
name: ietf-notification-sequencing
namespace: urn:ietf:params:xml:ns:yang:ietf-notification-sequencing
prefix: inotifseq
reference: RFC XXXX
Graf, et al. Expires 1 January 2025 [Page 13]
Internet-Draft YANG Notifications Sequencing June 2024
6.3. NETCONF Capability URNs Registry
This document registers the following NETCONF capability in the
"Network Configuration Protocol (NETCONF) Capability URNs" registry:
Capability: :notification-sysname-sequence:1.0
Capability Identifier: urn:ietf:params:netconf:capability:notification-sysname-sequence:1.0
Reference: RFC XXXX
7. Operational Considerations
7.1. SysName Correlation
In order to allow data correlation among BGP Monitoring Protocol
(BMP) [RFC7854] and YANG-Push, the same hostname value should be used
as described in Section 4.4 of [RFC7854] for the information TLV in
the init BMP message type.
8. Acknowledgements
The authors would like to thank Rob Wilton, Nick Corran, Pierre
Francois, Benoit Claise, Ahmed Elhassany and Ignacio Dominguez
Martinez-Casanueva for their review and valuable comments.
9. References
9.1. Normative References
[I-D.ahuang-netconf-notif-yang]
Feng, A. H., Francois, P., Graf, T., and B. Claise, "YANG
model for NETCONF Event Notifications", Work in Progress,
Internet-Draft, draft-ahuang-netconf-notif-yang-05, 18
June 2024, <https://datatracker.ietf.org/doc/html/draft-
ahuang-netconf-notif-yang-05>.
[RFC1213] McCloghrie, K. and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, DOI 10.17487/RFC1213, March 1991,
<https://www.rfc-editor.org/info/rfc1213>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/info/rfc3688>.
[RFC5277] Chisholm, S. and H. Trevino, "NETCONF Event
Notifications", RFC 5277, DOI 10.17487/RFC5277, July 2008,
<https://www.rfc-editor.org/info/rfc5277>.
Graf, et al. Expires 1 January 2025 [Page 14]
Internet-Draft YANG Notifications Sequencing June 2024
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>.
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/info/rfc8340>.
[RFC8641] Clemm, A. and E. Voit, "Subscription to YANG Notifications
for Datastore Updates", RFC 8641, DOI 10.17487/RFC8641,
September 2019, <https://www.rfc-editor.org/info/rfc8641>.
[RFC9187] Touch, J., "Sequence Number Extension for Windowed
Protocols", RFC 9187, DOI 10.17487/RFC9187, January 2022,
<https://www.rfc-editor.org/info/rfc9187>.
[RFC9196] Lengyel, B., Clemm, A., and B. Claise, "YANG Modules
Describing Capabilities for Systems and Datastore Update
Notifications", RFC 9196, DOI 10.17487/RFC9196, February
2022, <https://www.rfc-editor.org/info/rfc9196>.
[RFC9254] Veillette, M., Ed., Petrov, I., Ed., Pelov, A., Bormann,
C., and M. Richardson, "Encoding of Data Modeled with YANG
in the Concise Binary Object Representation (CBOR)",
RFC 9254, DOI 10.17487/RFC9254, July 2022,
<https://www.rfc-editor.org/info/rfc9254>.
[W3C.REC-xml-20081126]
Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008,
<https://www.w3.org/TR/2008/REC-xml-20081126>.
9.2. Informative References
Graf, et al. Expires 1 January 2025 [Page 15]
Internet-Draft YANG Notifications Sequencing June 2024
[I-D.ietf-netconf-udp-notif]
Zheng, G., Zhou, T., Graf, T., Francois, P., Feng, A. H.,
and P. Lucente, "UDP-based Transport for Configured
Subscriptions", Work in Progress, Internet-Draft, draft-
ietf-netconf-udp-notif-13, 27 June 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-netconf-
udp-notif-13>.
[RFC6470] Bierman, A., "Network Configuration Protocol (NETCONF)
Base Notifications", RFC 6470, DOI 10.17487/RFC6470,
February 2012, <https://www.rfc-editor.org/info/rfc6470>.
[RFC7854] Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP
Monitoring Protocol (BMP)", RFC 7854,
DOI 10.17487/RFC7854, June 2016,
<https://www.rfc-editor.org/info/rfc7854>.
[RFC9232] Song, H., Qin, F., Martinez-Julia, P., Ciavaglia, L., and
A. Wang, "Network Telemetry Framework", RFC 9232,
DOI 10.17487/RFC9232, May 2022,
<https://www.rfc-editor.org/info/rfc9232>.
Authors' Addresses
Thomas Graf
Swisscom
Binzring 17
CH-8045 Zurich
Switzerland
Email: [email protected]
Jean Quilbeuf
Huawei
Email: [email protected]
Alex Huang Feng
INSA-Lyon
Lyon
France
Email: [email protected]
Graf, et al. Expires 1 January 2025 [Page 16]