Notification Message Headers and Bundles
draft-voit-netconf-notification-messages-00

Document Type Active Internet-Draft (individual)
Last updated 2017-04-26
Replaces draft-voit-netmod-yang-notifications2
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)
NETCONF                                                          E. Voit
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                              A. Bierman
Expires: October 27, 2017                                      YumaWorks
                                                                A. Clemm
                                                                  Huawei
                                                              T. Jenkins
                                                           Cisco Systems
                                                          April 25, 2017

                Notification Message Headers and Bundles
              draft-voit-netconf-notification-messages-00

Abstract

   This document specifies transport independent capabilities for
   messages transporting event notifications and YANG datastore update
   records.  Included are:

   o  a set of transport agnostic message header objects, and

   o  how to associate a subset of these header objects with one or more
      events, YANG datastore updates, and/or alarms.

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 October 27, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Voit, et al.            Expires October 27, 2017                [Page 1]
Internet-Draft                Notifications                   April 2017

   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.  Transport independent headers for notifications . . . . . . .   4
   5.  Bundled Notifications . . . . . . . . . . . . . . . . . . . .   6
   6.  Data Model  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Issues being worked  . . . . . . . . . . . . . . . .  14
   Appendix B.  Querying an Object Model . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   Mechanisms to support subscription to event notifications and yang
   datastore push are being defined in [subscribe] and [yang-push].
   Work on those documents have shown that existing YANG notifications
   described in [RFC7950] section 7.16 do not expose some useful
   transport independent capabilities that application developers are
   requesting.  Communicating information on the following objects
   should not require knowledge of the underlying transport:

   o  the kind of information encapsulated (event, data objects, alarm?)

   o  the time information was generated

   o  the time the information was sent

   o  a signature to verify authenticity

   o  the process generating the information

   o  an originating request correlation

Voit, et al.            Expires October 27, 2017                [Page 2]
Internet-Draft                Notifications                   April 2017

   o  an ability to bundle information records together in a message

   o  the ability to check for message loss/reordering

   The document describes information elements needed for the functions
Show full document text