YANG Notification Headers and Bundles
draft-voit-netmod-yang-notifications2-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-24
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
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                                                           E. Voit
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                              A. Bierman
Expires: August 25, 2017                                       YumaWorks
                                                                A. Clemm
                                                                  Huawei
                                                              T. Jenkins
                                                           Cisco Systems
                                                       February 21, 2017

                 YANG Notification Headers and Bundles
                draft-voit-netmod-yang-notifications2-00

Abstract

   There are useful capabilities not available with existing YANG
   notifications as described in Section 7.16 of [RFC7950].  These
   include:

   1.  what are the set of transport agnostic header objects which might
       be usefully placed within YANG notifications.

   2.  how might a set of YANG notifications be bundled into a single
       transport message.

   3.  how do you query the originator of a notification to troubleshoot
       the bundling process

   This specification provides technologies enabling these three
   capabilities.

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 http://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 25, 2017.

Voit, et al.             Expires August 25, 2017                [Page 1]
Internet-Draft                   Notif2                    February 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Header Objects  . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Headers added to an RFC7950 Notification  . . . . . . . . . .   4
   5.  Bundled Notifications . . . . . . . . . . . . . . . . . . . .   5
   6.  Querying an Object Model  . . . . . . . . . . . . . . . . . .   7
   7.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  20
   Appendix A.  Issues being worked  . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   Mechanisms to support subscription to event notifications and yang
   datastore push are being defined in [sn] and [yang-push].  Work on
   those documents has shown that additional capabilities in YANG
   notifications would be helpful.  Three of these capabilities include:

   1.  what are the set of transport agnostic header objects which might
       be usefully placed within YANG notifications.

   2.  how might a set of YANG notifications be bundled into a single
       transport message.

   3.  how do you query the originator of a notification to troubleshoot
       the bundling process.

Voit, et al.             Expires August 25, 2017                [Page 2]
Internet-Draft                   Notif2                    February 2017

   As none of these three capabilities are specific to subscriptions, it
   would be good to define them in a transport protocol agnostic way.
Show full document text