Terminology and Requirements for Enhanced Handling of Operational State
draft-ietf-netmod-opstate-reqs-04
|
| Document |
Type |
|
Active Internet-Draft (netmod WG)
|
|
Last updated |
|
2016-03-02
(latest revision 2016-01-22)
|
|
Replaces |
|
draft-chairs-netmod-opstate-reqs
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Informational
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Andrew McLachlan
|
|
Shepherd write-up |
|
Show
(last changed 2016-02-02)
|
| IESG |
IESG state |
|
Waiting for AD Go-Ahead::Revised I-D Needed
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Benoit Claise
|
|
Send notices to |
|
amclachl@cisco.com
|
| IANA |
IANA review state |
|
IANA OK - No Actions Needed
|
|
IANA action state |
|
None
|
NETMOD Working Group K. Watsen
Internet-Draft Juniper Networks
Intended status: Informational T. Nadeau
Expires: July 25, 2016 Brocade Networks
January 22, 2016
Terminology and Requirements for Enhanced Handling of Operational State
draft-ietf-netmod-opstate-reqs-04
Abstract
This document primarily regards the difference between the intended
configuration and the applied configuration of a device and how
intended and applied configuration relate to the operational state of
a device. This document defines requirements for the applied
configuration's data model and its values, as well as for enabling a
client to know when a configuration has been fully applied or not,
how to access operational state, and how to relate intended
configuration nodes to applied configuration and derived state nodes.
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 25, 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
Watsen & Nadeau Expires July 25, 2016 [Page 1]
Internet-DraftTerms and Reqs for OpState Enhanced Handling January 2016
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. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
This document primarily regards the difference between the intended
configuration and the applied configuration of a device and how
intended and applied configuration relate to the operational state of
a device. This document defines requirements for the applied
configuration's data model and its values, as well as for enabling a
client to know when a configuration has been fully applied or not,
how to access operational state, and how to relate intended
configuration nodes to applied configuration and derived state nodes.
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".
Show full document text