YangPush Notification Capabilities
draft-ietf-netconf-notification-capabilities-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

draft-ietf-netconf-notification-capabilities-00.txt:
xym 0.4:
Extracting 'ietf-notification-capabilities.yang'
   Removed 1 empty lines


ietf-notification-capabilities@2018-07-02.yang:
pyang 1.7.8: pyang --verbose --ietf -p {libs} {model}:
# read ietf-notification-capabilities@2018-07-02.yang (CL)
# read /a/www/ietf-datatracker/6.91.0/env/share/yang/modules/ietf/ietf-netconf-acm.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-netconf-acm@2018-02-14.yang
# read /a/www/ietf-datatracker/6.91.0/env/share/yang/modules/ietf/ietf-yang-types.yang
# read /a/www/ietf-ftp/yang/rfcmod/ietf-yang-types@2013-07-15.yang
ietf-notification-capabilities@2018-07-02.yang:95: error: RFC 6087: 4.12: statement "leaf" must have a "description" substatement

yanglint 0.14.80: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors

Netconf                                                       B. Lengyel
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                A. Clemm
Expires: April 5, 2019                                        Huawei USA
                                                         October 2, 2018

                   YangPush Notification Capabilities
            draft-ietf-netconf-notification-capabilities-00

Abstract

   This document proposes a YANG module that allows a YANG server to
   specify for which data nodes it will send "YANG Datastore
   Subscription" on-change notifications.  It also proposes to use YANG
   Instance Data to document this information in implementation time.

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 April 5, 2019.

Copyright Notice

   Copyright (c) 2018 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 extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Lengyel & Clemm           Expires April 5, 2019                 [Page 1]
Internet-Draft     YangPush Notification Capabilities       October 2018

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  On-change Notification Capability Model . . . . . . . . . . .   4
     3.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  The IETF XML Registry . . . . . . . . . . . . . . . . . .   8
     5.2.  The YANG Module Names Registry  . . . . . . . . . . . . .   8
   6.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Appendix A.  Changes between revisions  . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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.

   On-change Notification Capability: The capability of the YANG server
   to send on-change notifications on the change of the value for a
   specific data node.

   Implementation-time information: Information about the YANG server's
   behavior that is made available during the implementation of the
   server, available from a source other then a running Yang server.

   Rutime-information: Information about the YANG server's behavior that
   is available from the running YANG server via a protocol like
   NETCONF, RESTCONF or HTTPS.

2.  Introduction

   As defined in [I-D.ietf-netconf-yang-push] a YANG server may allow
   clients to subscribe to updates from a datastore and subsequently
   push such update notifications to the client.  Notifications may be
   sent periodically or on-change (more or less immendiately after each
   change).

   In some cases, a publisher supporting on-change notifications will
   not be able to push updates for some object types on-change.  Reasons

Lengyel & Clemm           Expires April 5, 2019                 [Page 2]
Internet-Draft     YangPush Notification Capabilities       October 2018

   for this might be that the value of the datastore node changes
   frequently (e.g. in-octets counter), that small object changes are