Terminology and Requirements for Enhanced Operational State Visibility and Control
draft-ietf-netmod-opstate-reqs-02

The information below is for an old version of the document
Document Type Active Internet-Draft (netmod WG)
Last updated 2016-01-04
Replaces draft-chairs-netmod-opstate-reqs
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)
NETMOD Working Group                                           K. Watsen
Internet-Draft                                          Juniper Networks
Intended status: Informational                                 T. Nadeau
Expires: July 7, 2016                                   Brocade Networks
                                                         January 4, 2016

               Terminology and Requirements for Enhanced
                Operational State Visibility and Control
                   draft-ietf-netmod-opstate-reqs-02

Abstract

   This document discusses the difference between intended configuration
   and applied configuration of a device and how intended and applied
   configuration relate to the operational state of a device.  The
   document defines the necessary terminology and identifies
   requirements enabling visibility into the difference of intended
   configuration and applied configuration.

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 July 7, 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

Watsen & Nadeau           Expires July 7, 2016                  [Page 1]
Internet-Draft       OpState Visibility and Control         January 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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Backwards Compatibility . . . . . . . . . . . . . . . . . . .   4
   4.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document discusses the difference between intended configuration
   and applied configuration of a device and how intended and applied
   configuration relate to the operational state of a device.  The
   document defines the necessary terminology and identifies
   requirements enabling visibility into the difference of intended
   configuration and applied configuration.

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 term "client" is used throughout this document to refer to what
   is many times known as the "application" or "network management
   system".  This definition is intended to be consistent with the term
   "client" defined in [RFC6241], Section 1.1, but independent of any
   association to a particular protocol.

   The term "server" is used throughout this document to refer to what
   is many times known as the "device", "system", or "network element".
   This definition is intended to be consistent with the term "server"
   defined in [RFC6241], Section 1.1, but independent of any association
   to a particular protocol.

   This document defines the following terms:

Watsen & Nadeau           Expires July 7, 2016                  [Page 2]
Internet-Draft       OpState Visibility and Control         January 2016

   Applied Configuration:  This data represents the configuration state
       that the server is actually in.  That is, the configuration state
       which is currently being used by server components (e.g., control
Show full document text