Terminology and Requirements for Enhanced Handling of Operational State
draft-ietf-netmod-opstate-reqs-04
| Document | Type | Expired Internet-Draft (netmod WG) | |
|---|---|---|---|
| Last updated | 2017-12-22 (latest revision 2016-01-22) | ||
| Replaces | draft-chairs-netmod-opstate-reqs | ||
| Stream | IETF | ||
| Intended RFC status | Informational | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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 | Expired (IESG: Dead::Revised I-D Needed) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| 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
Kent Watsen
(kwatsen@juniper.net)
Thomas Nadeau
(tnadeau@lucidvision.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)