Support of Versioning in
YANG Notifications SubscriptionSwisscomBinzring 17Zurich8045Switzerlandthomas.graf@swisscom.comHuaweibenoit.claise@huawei.comINSA-LyonLyonFrancealex.huang-feng@insa-lyon.frThis 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.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
when, and only when,
they appear in all capitals, as shown here.In order to process the newly received YANG push notification
messages described in section 3.7 of 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 , where a publisher is
configured to stream notification out of band, as opposed to dynamic
subscriptions defined in Section 2.4 of , where
the 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 and
being streamed from the publisher to receiver with the subscription
state change notifications described in Section 2.7 of where for each subscription a locally unique
subscription ID described in Section 4.3.2 of
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 and states that the newer revision needs to be
backward compatible to the previous revision. Section 3.1 of specifies that newer
semantic versions introduced in MAY not be backward compatible to
the previous version when indicated with non-backwards-compatible
keyword.The YANG notifications subscription mechanism defined in 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 revision and semantic version.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 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.
General
Subscription Error Identities and Associated "error-tag" Use
Error identity
Uses "error-tag"
revision-unsupported
invalid-value
revision-label-unsupported
invalid-value
incompatible-revision-and-revision-label
invalid-value
provides
an example of a "establish-subscription" RPC call with YANG revision and
datastore-xpath-filter for periodical subscription.
shows the response when the RPC has been accepted by the NETCONF server
and the
error sent by the NETCONF server when the revision is not supported.
xmlns:ypr="urn:ietf:params:xml:ns:yang:ietf-yang-push-revision">
ds:operational
/ex:foo
ex:foo2023-09-17500
]]>
52
]]>applicationoperation-failederror
ypr:revision-unsupported
]]>Besides the Subscription ID and the xpath or sub-tree filter
reference as described in Section 2.7 of , 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 for the related streamed content.
revision-label:
Describes the YANG module semantic version as specified in for the related streamed
content.
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 ). This
subscription state change notification message is encoded XML over the Network Configuration Protocol
(NETCONF) as per .2023-01-03T10:00:00Z101
/int:interfaces
NETCONFietf-interfaces2018-02-202.0.0
]]>
provides an example of a JSON encoded, ,
subscription state change notification message over HTTPS-based or UDP-based transport for the same
subscription.This YANG module augments the "ietf-yang-push" module with the
module-name, revision and revision-label 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.The following is the YANG tree diagram
for the ietf-yang-push-revision YANG moduleThe following is the YANG tree diagram
for the ietf-yang-push-revision augmentation within the
ietf-subscribed-notifications, including the RPCs and
notifications.
| +--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?
+--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? {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?
| | {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?
| | | | {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?
| | {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
| {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
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?
| | | | | | {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?
| | | | {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}?
| | | +---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?
| | | | {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?
| | | {sn:subtree}?
| | +--:(yp:datastore-xpath-filter)
| | +---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?
| | | | | {subtree}?
| | | | +--:(stream-xpath-filter)
| | | | +--ro stream-xpath-filter?
| | | | yang:xpath1.0 {xpath}?
| | | +--ro stream
| | | | stream-ref
| | | +--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?
| | | {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
| +--ro yp:excluded-change* change-type
+---n subscription-resumed
| +--ro id subscription-id
+---n subscription-started {configured}?
| +--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?
| | | | | {subtree}?
| | | | +--:(stream-xpath-filter)
| | | | +--ro stream-xpath-filter?
| | | | yang:xpath1.0 {xpath}?
| | | +--ro stream
| | | | stream-ref
| | | +--ro replay-start-time?
| | | | yang:date-and-time {replay}?
| | | +--ro replay-previous-event-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?
| | | {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
| +--ro yp:excluded-change* change-type
+---n subscription-suspended
| +--ro id subscription-id
| +--ro reason identityref
+---n subscription-terminated
+--ro id subscription-id
+--ro reason identityref
]]>The YANG module has two leaves augmenting the model of Subscription to YANG Notifications. file "ietf-yang-push-revision@2024-05-28.yang"
module ietf-yang-push-revision {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-yang-push-revision";
prefix ypr;
import ietf-subscribed-notifications {
prefix sn;
reference
"RFC 8639: Subscription to YANG Notifications";
}
import ietf-yang-revisions {
prefix rev;
reference
"RFC YYYY: draft-ietf-netmod-yang-module-versioning-11,
Updated YANG Module Revision Handling";
}
import ietf-yang-types {
prefix yang;
rev:recommended-min-date "2013-07-15";
reference
"RFC 6991: Common YANG Data Types.";
}
import ietf-yang-semver {
prefix ysver;
reference
"RFC ZZZZ: draft-ietf-netmod-yang-semver-15, YANG Semantic
Versioning";
}
organization "IETF NETCONF (Network Configuration) Working Group";
contact
"WG Web:
WG List:
Authors: Thomas Graf
Benoit Claise
Alex Huang Feng
";
description
"Defines YANG push event notification header with the revision and
the revision-label. Adds the support of the revision and
revision-label selection in the YANG push subscription RPCs.
Copyright (c) 2023 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 2024-06-16 {
description
"First revision";
reference
"RFC XXXX: Support of Versioning in YANG Notifications
Subscription";
}
feature yang-push-revision-supported {
description
"This feature indicates the YANG Subscription Notifications
supports specifying the list of modules, revisions and
revision-label in the YANG subscription.";
}
// Identities
identity revision-unsupported {
base sn:establish-subscription-error;
base sn:modify-subscription-error;
description
"Revision not supported. This failure can be due to subscribing
to a specific revision not supported by the publisher.";
}
identity revision-label-unsupported {
base sn:establish-subscription-error;
base sn:modify-subscription-error;
description
"Revision-label not supported. This failure can be due to
subscribing to a specific revision-label not supported by the publisher.";
}
identity incompatible-revision-and-revision-label {
base sn:establish-subscription-error;
base sn:modify-subscription-error;
description
"The combination of revision and the revision-label are
incompatible. This failure happens when the revision and the
revision-label are both specified in the RPC and the YANG
module supported by the publisher does not support one of the
revision or the revision-label.";
}
grouping yang-push-module-version-config {
description
"This grouping combines the module name, the revision and
revision-label leaves. This grouping is to be used for
configuration and the leaves are not mandatory.";
leaf module-name {
type yang:yang-identifier;
description
"This references the YANG module name.";
}
leaf revision {
type rev:revision-date;
description
"This references the YANG module revision to be sent in the
subscription.";
}
leaf revision-label {
type ysver:version;
description
"This references the YANG module semantic version to be sent in the
subscription.";
}
}
grouping yang-push-module-version {
description
"This grouping combines the module name, the revision and
revision-label leaves. This grouping is to be used for
read-only cases such as the content of YANG push Notifications.
The module-name and revision are mandatory and MUST be present
in the data.";
leaf module-name {
type yang:yang-identifier;
config false;
mandatory true;
description
"This references the YANG module name.";
}
leaf revision {
type rev:revision-date;
config false;
mandatory true;
description
"This references the YANG module revision of the sent
notification message.";
}
leaf revision-label {
type ysver:version;
description
"This references the YANG module semantic version of the sent
notification message.";
}
}
grouping yang-push-module-version-list {
description
"This grouping defines a list of yang-push-module-version
grouping.";
list module-version {
key "module-name";
config false;
description
"List of yang-push-module-version grouping. The revision is
not configurable.";
uses ypr:yang-push-module-version;
}
}
grouping yang-push-module-version-config-list {
description
"This grouping defines a list of yang-push-module-version-config
grouping.";
list module-version-config {
key "module-name";
description
"List of yang-push-module-version-config grouping. The revision
is configurable.";
uses ypr:yang-push-module-version-config;
}
}
// Subscription parameters
augment "/sn:establish-subscription/sn:input" {
if-feature "yang-push-revision-supported";
description
"Augment the establish-subscription RPC from the
ietf-subscribed-notifications YANG module with the
yang-push-module-version-config-list grouping.";
uses ypr:yang-push-module-version-config-list;
}
augment "/sn:modify-subscription/sn:input" {
if-feature "yang-push-revision-supported";
description
"Augment the modify-subscription RPC from the
ietf-subscribed-notifications YANG module with the
yang-push-module-version-config-list grouping.";
uses ypr:yang-push-module-version-config-list;
}
// Subscription notifications
augment "/sn:subscription-started" {
if-feature "yang-push-revision-supported";
description
"Augment the subscription-started notification from the
ietf-subscribed-notifications YANG module with the
yang-push-module-version-list grouping.";
uses ypr:yang-push-module-version-list;
}
augment "/sn:subscription-modified" {
if-feature "yang-push-revision-supported";
description
"Augment the subscription-modified notification from the
ietf-subscribed-notifications YANG module with the
yang-push-module-version-list grouping.";
uses ypr:yang-push-module-version-list;
}
// Subscription container
augment "/sn:subscriptions/sn:subscription" {
if-feature "yang-push-revision-supported";
description
"Augment the subscriptions RPC container from the
ietf-subscribed-notifications YANG module with the
yang-push-module-version-config-list grouping.";
uses ypr:yang-push-module-version-config-list;
}
}
]]>This document registers the following URIs in the "IETF XML
Registry" :This document registers the following YANG modules in the "YANG
Module Names" registry :A YANG package ,
specifies a versioned organizational structure used to manage a set of
YANG modules that collectively defines a package schema. For example, a
YANG package could contain a set of YANG modules required to implement a
L3VPN service on a network node. It offers therefore a complementary
information to the solution in this draft by describing how one specific
YANG module revision is part of a set of YANG modules.Note to the RFC-Editor: Please remove this section before
publishing.Huawei implemented this document for a YANG Push publisher on UDP-based Transport for Configured
Subscriptions in their VRP platform.The security considerations for the YANG notifications subscription
mechanism are described in . This documents adds
no additional security considerations.The authors would like to thank Qiufang Ma and Robert Wilton for
their review and valuable comments.Extensible Markup Language (XML) 1.0 (Fifth Edition)World Wide Web Consortium Recommendation
REC-xml-20081126