draft-ietf-netconf-notification-capabilities-06.txt   draft-ietf-netconf-notification-capabilities-07.txt 
NETCONF B. Lengyel NETCONF B. Lengyel
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track A. Clemm Intended status: Standards Track A. Clemm
Expires: May 20, 2020 Futurewei Expires: May 20, 2020 Futurewei
B. Claise B. Claise
Cisco Systems, Inc. Cisco Systems, Inc.
November 17, 2019 November 17, 2019
YANG-Push Notification Capabilities YANG-Push Notification Capabilities
draft-ietf-netconf-notification-capabilities-06 draft-ietf-netconf-notification-capabilities-07
Abstract Abstract
This document proposes a YANG module that allows a publisher to This document proposes a YANG module that allows a publisher to
specify capabilities related to "Subscription to YANG Datastores" specify capabilities related to "Subscription to YANG Datastores"
(YANG-Push). It proposes to use YANG Instance Data to document this (YANG-Push). It proposes to use YANG Instance Data to document this
information and make it already available at implementation-time, but information and make it already available at implementation-time, but
also allow it to be reported at run-time. also allow it to be reported at run-time.
Status of This Memo Status of This Memo
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 12 4. Security Considerations . . . . . . . . . . . . . . . . . . . 12
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 13 5.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 13
5.2. The YANG Module Names Registry . . . . . . . . . . . . . 13 5.2. The YANG Module Names Registry . . . . . . . . . . . . . 13
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Normative References . . . . . . . . . . . . . . . . . . 13 6.1. Normative References . . . . . . . . . . . . . . . . . . 13
6.2. Informative References . . . . . . . . . . . . . . . . . 14 6.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Instance data examples . . . . . . . . . . . . . . . 14 Appendix A. Instance data examples . . . . . . . . . . . . . . . 14
Appendix B. Changes between revisions . . . . . . . . . . . . . 17 Appendix B. Changes between revisions . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
The terms YANG-Push, On-change subscription and Periodic subscription The terms YANG-Push, On-change subscription and Periodic subscription
skipping to change at page 15, line 11 skipping to change at page 15, line 11
capabilities of a hypothetical "acme-switch". The switch implements capabilities of a hypothetical "acme-switch". The switch implements
the running, candidate and operational datastores. Every change can the running, candidate and operational datastores. Every change can
be reported on-change from running, nothing from candidate and all be reported on-change from running, nothing from candidate and all
config=false data from operational. Periodic subscriptions are config=false data from operational. Periodic subscriptions are
supported for running and operational, but not for candidate. supported for running and operational, but not for candidate.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<instance-data-set xmlns= <instance-data-set xmlns=
"urn:ietf:params:xml:ns:yang:ietf-yang-instance-data"> "urn:ietf:params:xml:ns:yang:ietf-yang-instance-data">
<name>acme-switch-notification-capabilities</name> <name>acme-switch-notification-capabilities</name>
<module>ietf-notification-capabilities@2019-10-22.yang</module> <yid-version>1</yid-version>
<content-schema>
<module>ietf-notification-capabilities@2019-10-22.yang</module>
</content-schema>
<!-- revision date, contact, etc. --> <!-- revision date, contact, etc. -->
<description>Notification capabilities of acme-switch. <description>Notification capabilities of acme-switch.
Acme-switch implements the running, candidate and operational Acme-switch implements the running, candidate and operational
datastores. Every change can be reported on-change from running, datastores. Every change can be reported on-change from running,
nothing from candidate and all config=false data from operational. nothing from candidate and all config=false data from operational.
Periodic subscriptions are supported for running and Periodic subscriptions are supported for running and
operational, but not for candidate. operational, but not for candidate.
</description> </description>
<content-data> <content-data>
<publisher-subscription-capabilities <publisher-subscription-capabilities
skipping to change at page 16, line 28 skipping to change at page 16, line 31
reported on-change from running, but only config=true nodes and some reported on-change from running, but only config=true nodes and some
config=false data from operational. Interface statistics are not config=false data from operational. Interface statistics are not
reported on-change only 2 important counters. Datastore subscription reported on-change only 2 important counters. Datastore subscription
capabilities are not reported on-change as they never change on the capabilities are not reported on-change as they never change on the
acme-router during run-time. acme-router during run-time.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<instance-data-set xmlns= <instance-data-set xmlns=
"urn:ietf:params:xml:ns:yang:ietf-yang-instance-data"> "urn:ietf:params:xml:ns:yang:ietf-yang-instance-data">
<name>acme-router-notification-capabilities</name> <name>acme-router-notification-capabilities</name>
<module>ietf-notification-capabilities@2019-10-22.yang</module> <yid-version>1</yid-version>
<content-schema>
<module>ietf-notification-capabilities@2019-10-22.yang</module>
<content-schema>
<!-- revision date, contact, etc. --> <!-- revision date, contact, etc. -->
<description>Defines the notification capabilities of an acme-router. <description>Defines the notification capabilities of an acme-router.
The router only has running, and operational datastores. The router only has running, and operational datastores.
Every change can be reported on-change from running, but Every change can be reported on-change from running, but
only config=true nodes and some config=false data from operational. only config=true nodes and some config=false data from operational.
Statistics are not reported on-change only 2 important counters, Statistics are not reported on-change only 2 important counters,
for these a smaller dampening period is possible. for these a smaller dampening period is possible.
</description> </description>
<content-data> <content-data>
<publisher-subscription-capabilities <publisher-subscription-capabilities
skipping to change at page 17, line 42 skipping to change at page 17, line 48
</per-node-capabilities> </per-node-capabilities>
</datastore-capabilities> </datastore-capabilities>
</publisher-subscription-capabilities> </publisher-subscription-capabilities>
</content-data> </content-data>
</instance-data-set> </instance-data-set>
Figure 2: Notification Capabilities with data node specific settings Figure 2: Notification Capabilities with data node specific settings
Appendix B. Changes between revisions Appendix B. Changes between revisions
v06 - v07
o Updated examples according to draft-ietf-netmod-yang-instance-
file-format-05.
v05 - v06 v05 - v06
o Providing the capability data is only a "SHOULD" recommendation. o Providing the capability data is only a "SHOULD" recommendation.
Some reviewers wanted MUST some wanted much less. Some reviewers wanted MUST some wanted much less.
o The YANG module import statements now indicate the imported o The YANG module import statements now indicate the imported
modules that must be implemented not just available as import as modules that must be implemented not just available as import as
requested by the YangDoctors review. requested by the YangDoctors review.
v04 - v05 v04 - v05
 End of changes. 5 change blocks. 
4 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/