NETCONF Support for Event Notifications
draft-ietf-netconf-netconf-event-notifications-05

The information below is for an old version of the document
Document Type Active Internet-Draft (netconf WG)
Last updated 2017-10-03
Replaces draft-gonzalez-netconf-event-notifications
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
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                                               A. Gonzalez Prieto
Internet-Draft                                                    VMware
Intended status: Standards Track                                A. Clemm
Expires: April 5, 2018                                            Huawei
                                                                 E. Voit
                                                       E. Nilsen-Nygaard
                                                             A. Tripathy
                                                           Cisco Systems
                                                         October 2, 2017

                NETCONF Support for Event Notifications
           draft-ietf-netconf-netconf-event-notifications-05

Abstract

   This document defines how to transport network subscriptions and
   event messages on top of the Network Configuration protocol
   (NETCONF).  This includes the full set of RPCs, subscription state
   changes, and subscribed content needing asynchronous delivery.

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 5, 2018.

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

Gonzalez Prieto, et al.   Expires April 5, 2018                 [Page 1]
Internet-Draft            NETCONF-notifications             October 2017

   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 . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Event Stream Discovery  . . . . . . . . . . . . . . . . .   3
     3.2.  Mandatory NETCONF support . . . . . . . . . . . . . . . .   4
     3.3.  Dynamic Subscriptions . . . . . . . . . . . . . . . . . .   4
     3.4.  Configured Subscriptions  . . . . . . . . . . . . . . . .  11
   4.  Interleave Capability . . . . . . . . . . . . . . . . . . . .  23
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  24
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  25
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  25
   Appendix A.  Open Items . . . . . . . . . . . . . . . . . . . . .  26
   Appendix B.  Changes between revisions  . . . . . . . . . . . . .  26
     B.1.  v04 to v05  . . . . . . . . . . . . . . . . . . . . . . .  26
     B.2.  v03 to v04  . . . . . . . . . . . . . . . . . . . . . . .  26
     B.3.  v01 to v03  . . . . . . . . . . . . . . . . . . . . . . .  26
     B.4.  v00 to v01  . . . . . . . . . . . . . . . . . . . . . . .  26
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  27

1.  Introduction

   This document defines mechanisms that provide a subscription and
   asynchronous message notification delivery service for the NETCONF
   protocol [RFC6241] based on [subscribe].  This is an optional
   capability built on top of the base NETCONF definition.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

   The following terms are defined in [RFC6241]: client, server,
   operation, RPC.

   The following terms are defined in [subscribe]: event, event
   notification, stream, publisher, receiver, subscriber, subscription,
   configured subscription.

Gonzalez Prieto, et al.   Expires April 5, 2018                 [Page 2]
Internet-Draft            NETCONF-notifications             October 2017
Show full document text