Terminology and Requirements for Enhanced Handling of Operational State
draft-ietf-netmod-opstate-reqs-04
Document | Type | Expired Internet-Draft (netmod WG) | |
---|---|---|---|
Authors | Kent Watsen , Thomas Nadeau | ||
Last updated | 2017-12-22 (Latest revision 2016-01-22) | ||
Replaces | draft-chairs-netmod-opstate-reqs | ||
Stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
Reviews |
GENART Last Call review
Almost Ready
SECDIR Last Call review
Has Nits
OPSDIR Last Call review
Has Issues
|
||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Andrew McLachlan | ||
Shepherd write-up | Show Last changed 2016-02-02 | ||
IESG | IESG state | Expired (IESG: Dead::Revised I-D Needed) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | Benoît Claise | ||
Send notices to | amclachl@cisco.com | ||
IANA | IANA review state | IANA OK - No Actions Needed |
https://www.ietf.org/archive/id/draft-ietf-netmod-opstate-reqs-04.txt
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)