Extensions to Yang Push
draft-ranade-netmod-yang-push-extension-02

Document Type Active Internet-Draft (individual)
Last updated 2019-02-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 7 errors, 0 warnings.
Additional URLs
- Yang catalog entry for ietf-yang-push-ext@2019-02-01.yang
- Yang impact analysis for draft-ranade-netmod-yang-push-extension
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)
NETMOD Working Group                                           R. Ranade
Internet-Draft                                                    Huawei
Intended status: Standards Track                            Feb 05, 2019
Expires: August 9, 2019

                        Extensions to Yang Push
               draft-ranade-netmod-yang-push-extension-02

Abstract

   This document defines extensions to the yang push subscription
   mechanism, which can provide more granularity in tracking
   configuration changes in datastores.

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 9, 2019.

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
   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.

Ranade                   Expires August 9, 2019                 [Page 1]
Internet-Draft           Extensions to Yang Push                Feb 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Yang Push Subscription Extensions . . . . . . . . . . . . . .   3
     2.1.  Config Filter . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Origin Metadata Attribute . . . . . . . . . . . . . . . .   3
   3.  Examples of usage . . . . . . . . . . . . . . . . . . . . . .   3
   4.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The subscription mechanism defined in yang-push draft
   [I-D.ietf-netconf-yang-push] supports a subscription mechanism where
   datastore and its datanodes can be provided as targets.  However
   there are a few scenarios where a subscription to datanodes may not
   be sufficient.

   o  An application on the client, may want to track the configuration
      changes in a particular module.  If a module contains "config
      true" mixed with "config false" nodes, setting up a filter which
      targets only "config true" nodes at multiple levels will be
      cumbersome.

   o  An application on the client, may want to track the origin of the
      recently applied configuration.  Yang-push subscription currently
      does not provide such control.

1.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.

   The following terms are defined in [RFC8342] and are not redefined
   here:

   o  operational state datastore

   o  intended configuration datastore

Ranade                   Expires August 9, 2019                 [Page 2]
Internet-Draft           Extensions to Yang Push                Feb 2019

2.  Yang Push Subscription Extensions

   There are two new filter nodes added to the Yang push subscription
   mechanism.  They are listed below.

   o  config-filter

   o  with-origin

2.1.  Config Filter

   This is a filter for nodes with the given value for their 'config'
   property.  When this leaf is set to 'true', only 'config true' nodes
   are selected and, when set to 'false', only 'config false' nodes are
   selected.  If this leaf is not present, this filter is not applied.

2.2.  Origin Metadata Attribute
Show full document text