YANG-Push Notification Capabilities
draft-ietf-netconf-notification-capabilities-08
Document Type Active Internet-Draft (netconf WG)
Last updated 2019-12-09
Replaces draft-lengyel-netconf-notification-capabilities
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Yang Validation ☯ 9 errors, 0 warnings.
Reviews
YANGDOCTORS Last Call Review (of -05): Ready with Nits
Additional URLs
- Yang catalog entry for ietf-notification-capabilities@2019-12-09.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
Document shepherd Kent Watsen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Kent Watsen <kent+ietf@watsen.net>
Email authors Email WG IPR References Referenced by Nits 
NETCONF                                                       B. Lengyel
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                A. Clemm
Expires: June 11, 2020                                         Futurewei
                                                               B. Claise
                                                     Cisco Systems, Inc.
                                                        December 9, 2019

                  YANG-Push Notification Capabilities
            draft-ietf-netconf-notification-capabilities-08

Abstract

   This document proposes a YANG module that allows a publisher to
   specify capabilities related to "Subscription to YANG Datastores"
   (YANG-Push).  It proposes to use YANG Instance Data to document this
   information and make it already available at implementation-time, but
   also allow it to be reported at run-time.

   The YANG module is also prepared to contain other system
   capabilities, for future augmentations.

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 June 11, 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

Lengyel, et al.           Expires June 11, 2020                 [Page 1]
Internet-Draft     YANG-Push Notification Capabilities     December 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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Notification Capability Model . . . . . . . . . . . . . . . .   5
     3.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  YANG Module . . . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Other System Capabilities . . . . . . . . . . . . . . . .  13
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  The IETF XML Registry . . . . . . . . . . . . . . . . . .  13
     5.2.  The YANG Module Names Registry  . . . . . . . . . . . . .  14
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Appendix A.  Instance data examples . . . . . . . . . . . . . . .  15
   Appendix B.  Changes between revisions  . . . . . . . . . . . . .  19
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  20

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 terms YANG-Push, On-change subscription and Periodic subscription
   are used as defined in [RFC8641]

   The terms Subscriber, Publisher and Receiver are used as defined in
   [RFC8639]

   The term Server is used as defined in [RFC8342]

   On-change Notification Capability: The capability of the publisher to
   send on-change notifications for a specific datastore or a specific
   data node.

   Implementation-time information: Information about the publisher's
   behavior that is made available during the implementation of the

Lengyel, et al.           Expires June 11, 2020                 [Page 2]
Internet-Draft     YANG-Push Notification Capabilities     December 2019

   publisher, available from a source other then a running server
   implementing the publisher.

   Run-time information: Information about the publisher's behavior that
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools