Network Working Group R. Shakir
Internet-Draft BT
Intended status: Informational A. Shaikh
Expires: January 7, 2016 M. Hines
Google
July 6, 2015
Consistent Modeling of Operational State Data in YANG
draft-openconfig-netmod-opstate-01
Abstract
This document proposes an approach for modeling configuration and
operational state data in YANG [RFC6020] that is geared toward
network management systems that require capabilities beyond those
typically envisioned in a NETCONF-based management system. The
document presents the requirements of such systems and proposes a
modeling approach to meet these requirements, along with implications
and design patterns for modeling operational state in YANG.
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 January 7, 2016.
Copyright Notice
Copyright (c) 2015 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
Shakir, et al. Expires January 7, 2016 [Page 1]
Internet-Draft Modeling Operational State July 2015
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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Requirement to interact with both intended and applied
configuration . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Operational requirements . . . . . . . . . . . . . . . . . . 6
4.1. Applied configuration as part of operational state . . .