NMDA Base Notification for Intent based configuration update
draft-wu-netmod-base-notification-nmda-03

Document Type Active Internet-Draft (individual)
Last updated 2019-06-29
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Yang Validation 0 errors, 2 warnings.
Additional URLs
- Yang catalog entry for ietf-nmda-notifications@2019-06-19.yang
- Yang impact analysis for draft-wu-netmod-base-notification-nmda
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 Working Group                                               Q. Wu
Internet-Draft                                                    R. Tao
Intended status: Standards Track                               R. Ranade
Expires: December 31, 2019                                        Huawei
                                                           June 29, 2019

      NMDA Base Notification for Intent based configuration update
               draft-wu-netmod-base-notification-nmda-03

Abstract

   The Network Configuration Protocol (NETCONF)and RESTCONF provides
   mechanisms to manipulate configuration datastores.  NMDA introduces
   additional datastores for systems that support more advanced
   processing chains converting configuration to operational state.
   However, client applications are not able to be aware of common
   events in these additional datstores of the management system, such
   as a intended configuration state change in NETCONF server or
   RESTCONF server, that may impact management applications,especially
   when a server is managed by multiple clients or management
   applications.  This document define a YANG module that allows a
   client to receive additional notifications for some common system
   events pertaining to the Network Management Datastore Architecture
   (NMDA) defined in [RFC8342].

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 December 31, 2019.

Copyright Notice

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

Wu, et al.              Expires December 31, 2019               [Page 1]
Internet-Draft           NMDA Base Notification                June 2019

   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
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  NMDA Base Notifications for Intent based configuration Update   3
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Data Model Design . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Relation with NMDA Datastore Compare  . . . . . . . . . .   6
     2.4.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  14
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .  14
   Appendix A.  Changes between revisions  . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

1.  Introduction

   The Network Configuration Protocol (NETCONF) [RFC6241] and RESTCONF
   [RFC8040] provides mechanisms to manipulate configuration datastores.
   NMDA introduces additional datastores (e.g.,<intended>,
   <operational>) for systems that support more advanced processing
   chains converting configuration to operational state.  However,
   client applications are not able to be aware of common events in
   those additional datastores of the management system, e.g., there are
   many background system activities (e.g.,system internal interactions
   with hardware, interaction with protocols or other devices) that
   happen during propagation of a configuration change to the software
   and hardware components of a system.  It is possible that some
   configuration could not be applied to <operational> due to either
   remnant Configuration, or missing resource, etc.  There is a need for
   user or an application (configuration) to know the origin of failed
   configuration node and the reason why the configuration changes were
Show full document text