NETCONF Event Notifications
draft-gonzalez-netconf-5277bis-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-03-21
Replaced by draft-ietf-netconf-rfc5277bis
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                               A. Gonzalez Prieto
Internet-Draft                                                  A. Clemm
Intended status: Standards Track                                 E. Voit
Expires: September 22, 2016                            E. Nilsen-Nygaard
                                                             A. Tripathy
                                                           Cisco Systems
                                                          March 21, 2016

                      NETCONF Event Notifications
                   draft-gonzalez-netconf-5277bis-01

Abstract

   This document defines capabilities and operations for providing
   asynchronous message notification delivery on top of the Network
   Configuration protocol (NETCONF).  This notification delivery is an
   optional capability built on top of the base NETCONF definition.
   This document is eventually intended to obsolete RFC 5277.

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 September 22, 2016.

Copyright Notice

   Copyright (c) 2016 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

Gonzalez Prieto, et al.Expires September 22, 2016               [Page 1]
Internet-Draft                  5277 bis                      March 2016

   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
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Solution Overview . . . . . . . . . . . . . . . . . . . .   5
   2.  Solution  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.1.  Event Streams . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Event Stream Discovery  . . . . . . . . . . . . . . . . .   7
     2.3.  Default Event Stream  . . . . . . . . . . . . . . . . . .   9
     2.4.  Data Model Trees for Event Notifications  . . . . . . . .   9
     2.5.  Creating a Subscription . . . . . . . . . . . . . . . . .  13
     2.6.  Establishing a Subscription . . . . . . . . . . . . . . .  16
     2.7.  Modifying a Subscription  . . . . . . . . . . . . . . . .  19
     2.8.  Deleting a Subscription . . . . . . . . . . . . . . . . .  24
     2.9.  Static Subscriptions  . . . . . . . . . . . . . . . . . .  26
     2.10. Event (Data Plane) Notifications  . . . . . . . . . . . .  30
     2.11. Control Plane Notifications . . . . . . . . . . . . . . .  32
     2.12. Subscription Management . . . . . . . . . . . . . . . . .  33
   3.  Data Models for Event Notifications . . . . . . . . . . . . .  34
     3.1.  Data Model for RFC5277 (netmod namespace) . . . . . . . .  34
     3.2.  Data Model for RFC5277 (netconf namespace)  . . . . . . .  38
     3.3.  Data Model for RFC5277-bis Extensions . . . . . . . . . .  41
   4.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .  58
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  59
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  60
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  60
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  61
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  61

1.  Introduction

   [RFC6241] can be conceptually partitioned into four layers:

Gonzalez Prieto, et al.Expires September 22, 2016               [Page 2]
Internet-Draft                  5277 bis                      March 2016

         Layer                         Example
       +-------------+     +-------------------------------------------+
       |   Content   |     |     Configuration data                    |
       +-------------+     +-------------------------------------------+
Show full document text