draft-ietf-i2rs-ephemeral-state-08.txt   draft-ietf-i2rs-ephemeral-state-09.txt 
I2RS working group J. Haas I2RS working group J. Haas
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Standards Track S. Hares Intended status: Standards Track S. Hares
Expires: December 2, 2016 Huawei Expires: December 2, 2016 Huawei
May 31, 2016 May 31, 2016
I2RS Ephemeral State Requirements I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-08 draft-ietf-i2rs-ephemeral-state-09
Abstract Abstract
This document covers requests to the NETMOD and NETCONF Working This document covers requests to the NETMOD and NETCONF Working
Groups for functionality to support the ephemeral state requirements Groups for functionality to support the ephemeral state requirements
to implement the I2RS architecture. to implement the I2RS architecture.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 5, line 12 skipping to change at page 5, line 12
must define within the model or service the valid uses of a non- must define within the model or service the valid uses of a non-
secure transport. secure transport.
3. Ephemeral State Requirements 3. Ephemeral State Requirements
3.1. Persistence 3.1. Persistence
Ephemeral-REQ-01: I2RS requires ephemeral state; i.e. state that does Ephemeral-REQ-01: I2RS requires ephemeral state; i.e. state that does
not persist across reboots. If state must be restored, it should be not persist across reboots. If state must be restored, it should be
done solely by replay actions from the I2RS client via the I2RS done solely by replay actions from the I2RS client via the I2RS
agent. agent. Ephemeral state may consist of ephemeral configuration or
ephemeral operational state, or both.
While at first glance this may seem equivalent to the writable- While at first glance this may seem equivalent to the writable-
running data store in NETCONF, running-config can be copied to a running data store in NETCONF, running-config can be copied to a
persistent data store, like startup config. I2RS ephemeral state persistent data store, like startup config. I2RS ephemeral state
MUST NOT be persisted. MUST NOT be persisted.
3.2. Constraints 3.2. Constraints
Ephemeral-REQ-02: Non-ephemeral state MUST NOT refer to ephemeral Ephemeral-REQ-02: Non-ephemeral state MUST NOT refer to ephemeral
state for constraint purposes; it SHALL be considered a validation state for constraint purposes; it SHALL be considered a validation
skipping to change at page 6, line 20 skipping to change at page 6, line 20
o a schema node (container, leaf, leaf-list, choice, case, rpc, o a schema node (container, leaf, leaf-list, choice, case, rpc,
input, output, notifications, and anyxml). input, output, notifications, and anyxml).
See [I-D.hares-i2rs-protocol-strawman] for examples of yang syntax. See [I-D.hares-i2rs-protocol-strawman] for examples of yang syntax.
4. YANG Features for Ephemeral State for I2RS Protocol version 1 4. YANG Features for Ephemeral State for I2RS Protocol version 1
Ephemeral-REQ-07: Yang MUST have a way to indicate in a data model Ephemeral-REQ-07: Yang MUST have a way to indicate in a data model
that nodes have the following properties: ephemeral, writable/not- that nodes have the following properties: ephemeral, writable/not-
writable, and status/configuration. Yang must also have a way to writable, and status/configuration. Yang must also have a way to
specify on a model or sub-model level whether the data MAY optionally specify on a module or submodule level whether the data MAY
flow across an non-secure transport. optionally flow across an non-secure transport.
5. NETCONF Features for Ephemeral State for I2RS Protocol version 1 5. NETCONF Features for Ephemeral State for I2RS Protocol version 1
Ephemeral-REQ-08: The conceptual changes to NETCONF Ephemeral-REQ-08: The conceptual changes to NETCONF
1. protocol version support for I2RS modifications - (e.g. I2RS 1. protocol version support for I2RS modifications - (e.g. I2RS
version 1) version 1)
2. support for ephemeral model scope indication - which indicates 2. support for ephemeral model scope indication - which indicates
whether a module is an ephemeral-only module or mixed ephemeral whether a module is an ephemeral-only module or mixed ephemeral
 End of changes. 3 change blocks. 
4 lines changed or deleted 5 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/