YangPush Notification Capabilities

Document Type Active Internet-Draft (individual)
Last updated 2018-02-23
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         B. Lengyel
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                A. Clemm
Expires: August 26, 2018                                      Huawei USA
                                                       February 22, 2018

                   YangPush Notification Capabilities


   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 August 26, 2018.

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 August 26, 2018                [Page 1]
Internet-Draft     YangPush Notification Capabilities      February 2018

1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "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

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

   In some cases, a publisher supporting on-change notifications will
   not be able to push updates for some object types on-change.  Reasons
   for this might be that the value of the datastore node changes
   frequently (e.g. in-octets counter), that small object changes are
   frequent and meaningless (e.g., a temperature gauge changing 0.1
   degrees), or that the implementation is not capable of on-change
   notification for a particular object.  In those cases, it will be
   important for client applications to have a way to identify for which
   objects on-change notifications are supported and for which ones they
   are not supported.

   Faced with the reality that support for on-change notification does
   not mean that such notifications will be sent for any specific data
   node, client/management applications can not rely on the on-change
   functionality unless the client has some means to identify for which
   objects on-change notifications are supported and for which ones they
   are not supported.  YANG models are meant to be used as an interface
   contract.  Without identification of data nodes supporting on-change,
   today this contract only states the YANG server may (or may not) send
   on-change notifications for a data node specified in a YANG module.

Lengyel & Clemm          Expires August 26, 2018                [Page 2]
Internet-Draft     YangPush Notification Capabilities      February 2018

   This document proposes a YANG module that allows a client to identify
Show full document text