Per-Node Capabilities for Optimum Operational Data Collection
draft-claise-netconf-metadata-for-collection-01
Document Type Active Internet-Draft (individual)
Authors Benoît Claise  , Munish Nayyar  , Adithya Sesani 
Last updated 2020-12-28
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Yang Validation ☯ 0 errors, 1 warnings.
Additional Resources
- Yang catalog entry for ietf-system-node-metadata@2020-03-23.yang
- Yang impact analysis for draft-claise-netconf-metadata-for-collection
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)
Email authors IPR References Referenced by Nits 
NETCONF                                                        B. Claise
Internet-Draft                                                 M. Nayyar
Intended status: Standards Track                         A. Reddy Sesani
Expires: July 1, 2021                                Cisco Systems, Inc.
                                                       December 28, 2020

     Per-Node Capabilities for Optimum Operational Data Collection
            draft-claise-netconf-metadata-for-collection-01

Abstract

   This document proposes a YANG module that provides per-node
   capabilities for optimum operational data collection.  This YANG
   module augments the YANG Modules for describing System Capabilities
   and YANG-Push Notification capabilities.

   This module defines augmented nodes to publish the metadata
   information specific to YANG node-identifier as per ietf-system-
   capabilities datatree.

   Complementary RPCs, based on the same node capabilities, simplify the
   data collection operations.

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 July 1, 2021.

Copyright Notice

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

Claise, et al.            Expires July 1, 2021                  [Page 1]
Internet-DraftNode Capabilities For Closed Loop Automation December 2020

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

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Concepts  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Base ietf-system-node-metadata YANG module  . . . . . . . . .   7
     4.1.  Tree View . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Full Tree View  . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  The IETF XML Registry . . . . . . . . . . . . . . . . . .  20
   8.  Open Issues . . . . . . . . . . . . . . . . . . . . . . . . .  21
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

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 term Client and Server are specified in [RFC8342].

   The term Implementation-time and Run-time are specified in
   [I-D.ietf-netconf-notification-capabilities].

2.  Introduction

   This document specifies a way to learn from the devices how granular
   its telemetry and data can be to provide the best post-processing
   analytics.  In the end, the service assurance architecture
   [I-D.claise-opsawg-service-assurance-architecture], it's not
   sufficient to simply stream (or poll) telemetry data, it is equally

Claise, et al.            Expires July 1, 2021                  [Page 2]
Internet-DraftNode Capabilities For Closed Loop Automation December 2020

   important to be able to act on the data.  As such, a series of extra
   information about the node capabilities is essential.

   The module ietf-system-capabilities
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools