YANG Modules for describing System Capabilities and Yang-Push Notification Capabilities
draft-ietf-netconf-notification-capabilities-13

Document Type Active Internet-Draft (netconf WG)
Last updated 2020-06-08 (latest revision 2020-03-23)
Replaces draft-lengyel-netconf-notification-capabilities
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Yang Validation 6 errors, 11 warnings.
Reviews
Additional Resources
- Yang catalog entry for ietf-notification-capabilities@2020-03-23.yang
- Yang catalog entry for ietf-system-capabilities@2020-03-23.yang
- Yang impact analysis for draft-ietf-netconf-notification-capabilities
- Mailing list discussion
Stream WG state Waiting for WG Chair Go-Ahead
Revised I-D Needed - Issue raised by WG, Awaiting Expert Review/Resolution of Issues Raised, Doc Shepherd Follow-up Underway
Document shepherd Kent Watsen
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Kent Watsen <kent+ietf@watsen.net>
NETCONF                                                       B. Lengyel
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                A. Clemm
Expires: September 24, 2020                                    Futurewei
                                                               B. Claise
                                                     Cisco Systems, Inc.
                                                          March 23, 2020

     YANG Modules for describing System Capabilities and Yang-Push
                       Notification Capabilities
            draft-ietf-netconf-notification-capabilities-13

Abstract

   This document defines two YANG modules:

   The module ietf-system-capabilities provides a structure that can be
   used to specify YANG related system capabilities for servers.  The
   module can be used in conjunction with YANG Instance Data to make
   this information available at implementation-time.  The module can
   also be used to report capability information from the server at run-
   time.

   The module ietf-notification-capabilities augments ietf-system-
   capabilities to specify capabilities related to "Subscription to YANG
   Datastores" (YANG-Push).

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 September 24, 2020.

Lengyel, et al.        Expires September 24, 2020               [Page 1]
Internet-Draft     YANG-Push Notification Capabilities        March 2020

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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  YANG-Push Notification Capabilities . . . . . . . . . . .   4
   3.  Providing System Capability Information . . . . . . . . . . .   6
   4.  System Capabilities Model . . . . . . . . . . . . . . . . . .   6
     4.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Notification Capabilities Model . . . . . . . . . . . . . . .  10
     5.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .  10
     5.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .  11
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     7.1.  The IETF XML Registry . . . . . . . . . . . . . . . . . .  17
     7.2.  The YANG Module Names Registry  . . . . . . . . . . . . .  17
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  19
   Appendix A.  Instance data examples . . . . . . . . . . . . . . .  19
   Appendix B.  Changes between revisions  . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  26

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.

Lengyel, et al.        Expires September 24, 2020               [Page 2]
Internet-Draft     YANG-Push Notification Capabilities        March 2020

   The terms YANG-Push, On-change subscription and Periodic subscription
   are used as defined in [RFC8641].
Show full document text