Notification Capabilities Model Extension for self-explanation data Node tag capability support
draft-tao-netconf-notif-node-tag-capabilities-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-03
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
NETCONF Working Group                                             R. Tao
Internet-Draft                                                     B. Wu
Intended status: Standards Track                                  Huawei
Expires: May 5, 2020                                    November 2, 2019

Notification Capabilities Model Extension for self-explanation data Node
                         tag capability support
            draft-tao-netconf-notif-node-tag-capabilities-00

Abstract

   Before a client application subscribes to updates from a datastore,
   server capabilities related to "Subscription to YANG Datastores" can
   be advertised using YANG Instance Data format.  These server
   capabilities can be documented at implement time or reported at run-
   time.

   This document proposes a YANG module for Data Node tag capability
   support which augments YANG Push Notification Capabilities model and
   provide additional self-explanation data node attributes associated
   with node selector within per-node capabilities.

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 May 5, 2020.

Copyright Notice

   Copyright (c) 2019 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

Tao & Wu                   Expires May 5, 2020                  [Page 1]
Internet-Draft            Node Tags Capability             November 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Notification Capability Model Extension . . . . . . . . . . .   3
     2.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   4
   3.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Updates to the IETF XML Registry  . . . . . . . . . . . .   5
     4.2.  Updates to the YANG Module Names Registry . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   As described in [I-D.netconf-notification-capabilities], a server
   supporting YANG-Push MAY have a number of capabilities such as

   o  Supported (reporting) periods for periodic subscriptions

   o  Maximum number of objects that can be sent in an update

   o  Supported dampening periods for on-change subscriptions

   o  The set of data nodes for which on-change notification is
      supported

   Notification capability model defined in [I-D.netconf-notification-
   capabilities] allows a client to discover YANG-Push related
   capabilities both at implementation-time and run-time.  Without using
   notification capability, it might lead to unexpected failure or
   additional message exchange for NETCONF clients to discover data
   models supported by a NETCONF server.

   When the state of all subscriptions of a particular Subscriber to be
   fetched is huge, filtering queries of operational state on a server
   based on server capabilities can greatly reduce the amount of data to
   be streamed out to the destination.

Tao & Wu                   Expires May 5, 2020                  [Page 2]
Internet-Draft            Node Tags Capability             November 2019

   However without self-explanation information on data node conveyed in
   Notification capability model [I-D.netconf-notification-
   capabilities], it is hard for NETCONF clients to automatically select
Show full document text