Notification Message Headers and Bundles
draft-ietf-netconf-notification-messages-02

Document Type Active Internet-Draft (netconf WG)
Last updated 2017-10-03
Replaces draft-voit-netconf-notification-messages
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Yang Validation 0 errors, 0 warnings.
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
NETCONF                                                          E. Voit
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                              A. Bierman
Expires: April 6, 2018                                         YumaWorks
                                                                A. Clemm
                                                                  Huawei
                                                              T. Jenkins
                                                           Cisco Systems
                                                        October 03, 2017

                Notification Message Headers and Bundles
              draft-ietf-netconf-notification-messages-02

Abstract

   This document defines a new notification message format, using yang-
   data.  Included are:

   o  a new notification mechanism and encoding to replace the one way
      operation of RFC-5277

   o  a set of common, transport agnostic message header objects.

   o  how to bundle multiple event records into a single notification
      message.

   o  how to ensure these new capabilities are only used with capable
      receivers.

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

Voit, et al.              Expires April 6, 2018                 [Page 1]
Internet-Draft                Notifications                 October 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
   (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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Header Objects  . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Encapsulation of Header Objects in Messages . . . . . . . . .   4
     4.1.  One Notification per Message  . . . . . . . . . . . . . .   5
     4.2.  Many Notifications per Message  . . . . . . . . . . . . .   6
     4.3.  Notification Type in Payload  . . . . . . . . . . . . . .   8
   5.  Configuration of Headers  . . . . . . . . . . . . . . . . . .   8
   6.  Discovering Receiver Support  . . . . . . . . . . . . . . . .   9
   7.  YANG Module . . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .  17
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     11.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Appendix A.  Changes between revisions  . . . . . . . . . . . . .  19
   Appendix B.  Issues being worked  . . . . . . . . . . . . . . . .  20
   Appendix C.  Subscription Specific Headers  . . . . . . . . . . .  20
   Appendix D.  Implications to Existing RFCs  . . . . . . . . . . .  21
     D.1.  Implications to RFC-7950  . . . . . . . . . . . . . . . .  21
     D.2.  Implications to RFC-8040  . . . . . . . . . . . . . . . .  21
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

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 has shown that notifications described in
   [RFC7950] section 7.16 could benefit from transport independent
   headers.  Communicating the following information to receiving
Show full document text