Bulk Subscription to YANG Event Notification
draft-wang-netconf-bulk-subscribed-notifications-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
Yang Validation 9 errors, 4 warnings.
Additional URLs
- Yang catalog entry for ietf-bulk-notification@2019-09-23.yang
- Yang catalog entry for ietf-bulk-subscription@2019-10-14.yang
- Yang impact analysis for draft-wang-netconf-bulk-subscribed-notifications
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                                            Z. Wang
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                                  Huawei
Expires: May 6, 2020                                    November 3, 2019

              Bulk Subscription to YANG Event Notification
          draft-wang-netconf-bulk-subscribed-notifications-00

Abstract

   This document defines a YANG data model and associated mechanism that
   allows subscriber applications to bulk subscribe to publishers' event
   streams based on their requirements.  And it also allows the
   publishers to report multiple event streams or subscriptions into a
   single notification message based on group identifier affiliation.

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

Wang & Wu                  Expires May 6, 2020                  [Page 1]
Internet-Draft              Bulk Subscription              November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Model Overview  . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Bulk Subscription YANG Module . . . . . . . . . . . . . . . .   5
   4.  Bulk Notification YANG Module . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Updates to the IETF XML Registry  . . . . . . . . . . . .   8
     5.2.  Updates to the YANG Module Names Registry . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The Subscription to YANG Notifications specification [RFC8639] uses A
   "stream" name in dynamic subscription protocol operation for
   identifying the targeted event stream against which the subscription
   is applied.  Notification Message Headers and Bundles [I-D.  ietf-
   netconf-notification-messages] uses subscription-id for identifying
   the targeted subscription.  However the dynamic subscription protocol
   operation lack the capability to identify a set of event streams or a
   set of subscriptions which have a common characteristic.  A group
   identifier associated with an event stream enables the ability to
   perform protocol operation on a set of event stream via a single
   transaction.  The group identifier provides a more optimal mechanism
   for protocol operation which would otherwise require multiple atomic
   transactions on a per event stream basis.  Following are some of the
   use-cases where such identifier can be used.

   o  For establishing a Dynamic Subscription, the subscriber may send a
      a single request the creation of a subscription for each of event
      stream's groups and perform creation of a subscription for all
      event steam's that are part of that group.

   o  The subscriber in dynamic subscription domain may choose to delete
      a dynamic subscription or end a dynamic subscription that is not
      associated with the specific transport session and domain.  In
      such case, the subscriber can perform delete-subscription or kill-
      subscription signaling using the group ID associated with a
      specific set of event streams.

   o  Multiple notifications (e.g., multiple notifications associated
Show full document text