draft-ietf-i2rs-ephemeral-state-07.txt   draft-ietf-i2rs-ephemeral-state-08.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: November 26, 2016 Huawei Expires: December 2, 2016 Huawei
May 25, 2016 May 31, 2016
I2RS Ephemeral State Requirements I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-07 draft-ietf-i2rs-ephemeral-state-08
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 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 26, 2016. This Internet-Draft will expire on December 2, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 14
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Review of Requirements from I2RS architecture document . . . 3 2. Review of Requirements from I2RS architecture document . . . 3
3. Ephemeral State Requirements . . . . . . . . . . . . . . . . 5 3. Ephemeral State Requirements . . . . . . . . . . . . . . . . 5
3.1. Persistence . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Persistence . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Constraints . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. Constraints . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 5 3.3. Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . 5
4. YANG Features for Ephemeral State for I2RS Protocol version 1 5 4. YANG Features for Ephemeral State for I2RS Protocol version 1 6
5. NETCONF Features for Ephemeral State for I2RS Protocol 5. NETCONF Features for Ephemeral State for I2RS Protocol
version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 6 version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. RESTCONF Features for Ephemeral State for I2RS Protocol 6. RESTCONF Features for Ephemeral State for I2RS Protocol
version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 7 version 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Requirements regarding Supporting Multi-Head Control via 7. Requirements regarding Supporting Multi-Head Control via
Client Priority . . . . . . . . . . . . . . . . . . . . . . . 9 Client Priority . . . . . . . . . . . . . . . . . . . . . . . 9
8. Multiple Message Transactions . . . . . . . . . . . . . . . . 10 8. Multiple Message Transactions . . . . . . . . . . . . . . . . 10
9. Pub/Sub Requirements Expanded for Ephemeral State . . . . . . 11 9. Pub/Sub Requirements Expanded for Ephemeral State . . . . . . 10
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
11. Security Considerations . . . . . . . . . . . . . . . . . . . 11 11. Security Considerations . . . . . . . . . . . . . . . . . . . 11
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
13.1. Normative References: . . . . . . . . . . . . . . . . . 12 13.1. Normative References: . . . . . . . . . . . . . . . . . 12
13.2. Informative References . . . . . . . . . . . . . . . . . 14 13.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
The Interface to the Routing System (I2RS) Working Group is chartered The Interface to the Routing System (I2RS) Working Group is chartered
with providing architecture and mechanisms to inject into and with providing architecture and mechanisms to inject into and
retrieve information from the routing system. The I2RS Architecture retrieve information from the routing system. The I2RS Architecture
document [I-D.ietf-i2rs-architecture] abstractly documents a number document [I-D.ietf-i2rs-architecture] abstractly documents a number
of requirements for implementing the I2RS requirements. Section 2 of requirements for implementing the I2RS requirements. Section 2
reviews 10 key requirements related to ephemeral state. reviews 10 key requirements related to ephemeral state.
skipping to change at page 4, line 15 skipping to change at page 4, line 15
3. The I2RS protocol will operate on data models which MAY be 3. The I2RS protocol will operate on data models which MAY be
protocol independent or protocol dependent. protocol independent or protocol dependent.
4. I2RS Agent MUST record the client identity when a node is 4. I2RS Agent MUST record the client identity when a node is
created or modified. The I2RS Agent SHOULD to be able to read created or modified. The I2RS Agent SHOULD to be able to read
the client identity of a node and use the client identity's the client identity of a node and use the client identity's
associated priority to resolve conflicts. The secondary associated priority to resolve conflicts. The secondary
identity is useful for traceability and may also be recorded. identity is useful for traceability and may also be recorded.
5. Client identity MUST have only one priority for the client's 5. Client identity MUST have only one priority for the client's
identifer. A collision on writes is considered an error, but identifier. A collision on writes is considered an error, but
the priority associated with each client identifier is utilized the priority associated with each client identifier is utilized
to compare requests from two different clients in order to to compare requests from two different clients in order to
modify an existing node entry. Only an entry from a client modify an existing node entry. Only an entry from a client
which is higher priority can modify an existing entry (First which is higher priority can modify an existing entry (First
entry wins). Priority only has meaning at the time of use. entry wins). Priority only has meaning at the time of use.
6. The Agent identity and the Client identity SHOULD be passed 6. The Agent identity and the Client identity SHOULD be passed
outside of the I2RS protocol in a authentication and outside of the I2RS protocol in a authentication and
authorization protocol (AAA). Client priority may be passed in authorization protocol (AAA). Client priority may be passed in
the AAA protocol. The values of identities are originally set the AAA protocol. The values of identities are originally set
skipping to change at page 5, line 35 skipping to change at page 5, line 35
Ephemeral-REQ-03: Ephemeral state must be able to utilized temporary Ephemeral-REQ-03: Ephemeral state must be able to utilized temporary
operational state (e.g. MPLS LSP-ID or a BGP IN-RIB) as a operational state (e.g. MPLS LSP-ID or a BGP IN-RIB) as a
constraints. constraints.
Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state Ephemeral-REQ-04: Ephemeral state MAY refer to non-ephemeral state
for purposes of implementing constraints. The designer of ephemeral for purposes of implementing constraints. The designer of ephemeral
state modules are advised that such constraints may impact the speed state modules are advised that such constraints may impact the speed
of processing ephemeral state commits and should avoid them when of processing ephemeral state commits and should avoid them when
speed is essential. speed is essential.
Ephemeral-REQ-05: Ephemeral state handling and notifications could
increase need for CPU processing, data flow rates across a transport,
or the rate of publication of data in a subscription or the logging
for traceability. The I2RS Agent SHOULD have the ability to
constraints for OAM functions operating to limit CPU processing, data
rate across a transport, the rate of publication of data in a
subscription, and logging rates; and the I2RS Agent SHOULD have the
ability to prioritize some of the management data flows between the
I2RS Agent and I2RS Client. In order to constrain resources needed,
the I2RS Agent MAY also schedule data flows or split data flows unto
multiple data flow streams.
3.3. Hierarchy 3.3. Hierarchy
Ephemeral-REQ-05: The ability to augment an object with appropriate Ephemeral-REQ-06: The ability to augment an object with appropriate
YANG structures that have the property of being ephemeral. An object YANG structures that have the property of being ephemeral. An object
defined as Yang module, schema tree, a schema node, submodule or defined as any one of the following:
components of a submodule (derived types, groupings, data node, RPCs,
actions, and notifications". o Yang module(and the module's schema tree),
o submodule or components of a submodule (e.g. derived types,
groupings, data node, RPCs, actions, and notifications), or
o a schema node (container, leaf, leaf-list, choice, case, rpc,
input, output, notifications, and anyxml).
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-06: 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, status/configuration, and secure/non-secure transport. (If writable, and status/configuration. Yang must also have a way to
you desire examples, please see [I-D.hares-i2rs-protocol-strawman] specify on a model or sub-model level whether the data MAY optionally
for potential yang syntax). 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-07: 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, mixed config module whether a module is an ephemeral-only module or mixed ephemeral
(ephemeral and config), mixed derived state (ephemeral and config (ephemeral + config), mixed derived state (ephemeral and
config). opstate).
3. multiple message support - supports the I2RS "all or nothing" 3. multiple message support - supports the I2RS "all or nothing"
concept ([I-D.ietf-i2rs-architecture] section 7.9) which is the concept ([I-D.ietf-i2rs-architecture] section 7.9) which is the
same as NETCONF "roll-back-on-error". same as NETCONF "roll-back-on-error".
4. support for the following transports protocol supported: "TCP", 4. support for the following transports protocol supported: "TCP",
"SSH", "TLS", and non-secure transport (see "SSH", "TLS", and non-secure transport (see
[I-D.ietf-i2rs-protocol-security-requirements] section 3.2 in [I-D.ietf-i2rs-protocol-security-requirements] section 3.2 in
requirements SEC-REQ-09 and SEC-REQ-11 for details). NETCONF requirements SEC-REQ-09 and SEC-REQ-11 for details). NETCONF
should be able to expand the number of secure transport protocols should be able to expand the number of secure transport protocols
supported as I2RS may add additional transport protocols. supported as I2RS may add additional transport protocols.
5. ability to restrict insecure transport support to specific 5. ability to restrict non-secure transport support to specific
portions of a data models marked as valid to transfer via portions of a data models marked as valid to transfer via
insecure protocol. insecure protocol.
6. ephemeral state overwriting of configuration state MUST be 6. ephemeral state overwriting of configuration state MUST be
controlled by the following policy knobs (as defined by controlled by the following policy knobs (as defined by
[I-D.ietf-i2rs-architecture] section 6.3 and 6.3.1): [I-D.ietf-i2rs-architecture] section 6.3 and 6.3.1):
* ephemeral configuration overwrites local configuration (true/ * ephemeral configuration overwrites local configuration (true/
false; normal value: true), and false; normal value: true), and
* Update of local configuration value supercedes and overwrites * Update of local configuration value supersedes and overwrites
the ephemeral configuration (true/false; normal value: false). the ephemeral configuration (true/false; normal value: false).
7. The ephemeral overwriting to local configuration described in (8) 7. The ephemeral overwriting to local configuration described in (6)
above is considered to be the composite of all ephemeral values above is considered to be the composite of all ephemeral values
by all clients. Some may consider this approach as a single pane by all clients. Some may consider this approach as a single pane
of glass for ephemeral state. of glass for ephemeral state.
8. The ephemeral state must support notification of write conflicts 8. The ephemeral state must support notification of write conflicts
using the priority requirements defined in section 3.7 below in using the priority requirements defined in section 7 below in
requirements Ephemeral-REQ-09 through Ephemeral-REQ-14). requirements Ephemeral-REQ-10 through Ephemeral-REQ-13).
9. Ephemeral data stores SHOULD not require support interactions 9. Ephemeral data stores SHOULD not require support interactions
with writable-running, candidate data store, confirmed commit, with writable-running, candidate data store, confirmed commit,
and a distinct start-up capability, and a distinct start-up capability,
This list of requirements require the following the following This list of requirements require the following the following
existing features are supported: existing features are supported:
support for the following encodings: XML or JSON. support for the following encodings: XML or JSON.
skipping to change at page 7, line 32 skipping to change at page 7, line 47
* call-home [I-D.ietf-netconf-call-home], and * call-home [I-D.ietf-netconf-call-home], and
* server model [I-D.ietf-netconf-server-model] with the server * server model [I-D.ietf-netconf-server-model] with the server
module must be augmented to support mutual authentication (see module must be augmented to support mutual authentication (see
[I-D.ietf-i2rs-protocol-security-requirements] section 3.1 in [I-D.ietf-i2rs-protocol-security-requirements] section 3.1 in
requirements: SEC-REQ-01 to SEC-REQ-08). requirements: SEC-REQ-01 to SEC-REQ-08).
6. RESTCONF Features for Ephemeral State for I2RS Protocol version 1 6. RESTCONF Features for Ephemeral State for I2RS Protocol version 1
Ephemeral-REQ-08: The conceptual changes to RESTCONF are: Ephemeral-REQ-09: The conceptual changes to RESTCONF are:
1. protocol version support for I2RS protocol modification (e.g. 1. protocol version support for I2RS protocol modification (e.g.
I2RS-version 1). I2RS-version 1).
2. ephemeral model scope allowed - ephemeral modules, mixed config 2. ephemeral model scope allowed - ephemeral modules, mixed config
module (ephemeral and config), mixed derived state (ephemeral and module (ephemeral and config), mixed derived state (ephemeral and
config). opstate).
3. support for both of the following transport protocol suites: 3. support for both of the following transport protocol suites:
* HTTP over TLS (secure HTTP as defined in RESTCONF * HTTP over TLS (secure HTTP as defined in RESTCONF
[I-D.ietf-netconf-restconf] section 2), [I-D.ietf-netconf-restconf] section 2),
* HTTP used in a non-secure fashion (See * HTTP used in a non-secure fashion (See
[I-D.ietf-i2rs-protocol-security-requirements], section 3.2, [I-D.ietf-i2rs-protocol-security-requirements], section 3.2,
requirements SEC-REQ-09 and SEC-REQ-11 for details), and requirements SEC-REQ-09 and SEC-REQ-11 for details), and
skipping to change at page 8, line 20 skipping to change at page 8, line 36
based on the requirements in [I-D.ietf-i2rs-pub-sub-requirements] based on the requirements in [I-D.ietf-i2rs-pub-sub-requirements]
and equivalent to the netconf . [I-D.ietf-netconf-yang-push] and equivalent to the netconf . [I-D.ietf-netconf-yang-push]
6. ephemeral state overwriting of configuration state MUST be 6. ephemeral state overwriting of configuration state MUST be
controlled by the following policy knobs (as defined by controlled by the following policy knobs (as defined by
[I-D.ietf-i2rs-architecture] section 6.3 and 6.3.1) [I-D.ietf-i2rs-architecture] section 6.3 and 6.3.1)
* Ephemeral configuration overwrites local configuration (true/ * Ephemeral configuration overwrites local configuration (true/
false; normal value:true), and false; normal value:true), and
* Update of local configuration value supercedes and overwrites * Update of local configuration value supersedes and overwrites
the ephemeral configuration (true/false; normal value:false). the ephemeral configuration (true/false; normal value:false).
7. The ephemeral state overwriting a local configuration described 7. The ephemeral state overwriting a local configuration described
above is considered to be the composite of all ephemeral state above is considered to be the composite of all ephemeral state
values by all clients. Some may consider this a single "pane of values by all clients. Some may consider this a single "pane of
glass" for the ephemeral values. glass" for the ephemeral values.
8. RESTCONF support ephemeral state MUST support notification of 8. RESTCONF support ephemeral state MUST support notification of
write conflicts using the priority requirements (see section 3.7 write conflicts using the priority requirements (see section 7
below, specifically requirements Ephemeral-REQ-09 through below, specifically requirements Ephemeral-REQ-10 through
Ephemeral-REQ-14). Expansion of existing "edit-collision" Ephemeral-REQ-13). Expansion of existing "edit-collision"
features (timestamp and Entity tag) to include I2RS client- features (timestamp and Entity tag) to include I2RS client-
priorities is preferred since I2RS client-Agents exchange MAY priorities is preferred since I2RS client-Agents exchange MAY
wish to use the existing edit-collision features in RESTCONF. wish to use the existing edit-collision features in RESTCONF.
9. Ephemeral data stores SHOULD not require support for interactions 9. Ephemeral data stores SHOULD not require support for interactions
with writeable-running, candidate data stores, confirmed commit, with writeable-running, candidate data stores, confirmed commit,
and a distinct start-up capability. and a distinct start-up capability.
This requirement also requires that RESTCONF support all of the This requirement also requires that RESTCONF support all of the
following specifications: following specifications:
1. support for the following encodings: XML or JSON. 1. support for the following encodings: XML or JSON.
2. all of the following curren RESTCONF specifications: 2. all of the following current RESTCONF specifications:
1. RESTCONF [I-D.ietf-netconf-restconf], 1. RESTCONF [I-D.ietf-netconf-restconf],
2. the yang-patch features as specified in 2. the yang-patch features as specified in
[I-D.ietf-netconf-yang-patch], [I-D.ietf-netconf-yang-patch],
3. yang module library [I-D.ietf-netconf-yang-library] as 3. yang module library [I-D.ietf-netconf-yang-library] as
defined in RESTCONF [I-D.ietf-netconf-restconf] section defined in RESTCONF [I-D.ietf-netconf-restconf] section
3.3.3), 3.3.3),
skipping to change at page 9, line 25 skipping to change at page 9, line 41
7. Requirements regarding Supporting Multi-Head Control via Client 7. Requirements regarding Supporting Multi-Head Control via Client
Priority Priority
To support Multi-Headed Control, I2RS requires that there be a To support Multi-Headed Control, I2RS requires that there be a
decidable means of arbitrating the correct state of data when decidable means of arbitrating the correct state of data when
multiple clients attempt to manipulate the same piece of data. This multiple clients attempt to manipulate the same piece of data. This
is done via a priority mechanism with the highest priority winning. is done via a priority mechanism with the highest priority winning.
This priority is per-client. This priority is per-client.
Ephemeral-REQ-09: The data nodes MAY store I2RS client identity and Ephemeral-REQ-10: The data nodes MAY store I2RS client identity and
not the effective priority at the time the data node is stored. Per not the effective priority at the time the data node is stored. Per
SEC-REQ-07 in section 3.1 of SEC-REQ-07 in section 3.1 of
[I-D.ietf-i2rs-protocol-security-requirements], an identifier must [I-D.ietf-i2rs-protocol-security-requirements], an identifier must
have just one priority. Therefore, the data nodes MAY store I2RS have just one priority. Therefore, the data nodes MAY store I2RS
client identity and not the effective priority of the I2RS client at client identity and not the effective priority of the I2RS client at
the time the data node is stored. The priority MAY be dynamically the time the data node is stored. The priority MAY be dynamically
changed by AAA, but the exact actions are part of the protocol changed by AAA, but the exact actions are part of the protocol
definition as long as collisions are handled as described in definition as long as collisions are handled as described in
Ephemeral-REQ-10, Ephemeral-REQ-11, and Ephemeral-REQ-12. Ephemeral-REQ-10, Ephemeral-REQ-11, and Ephemeral-REQ-12.
Ephemeral-REQ-10: When a collision occurs as two clients are trying Ephemeral-REQ-11: When a collision occurs as two clients are trying
to write the same data node, this collision is considered an error to write the same data node, this collision is considered an error
and priorities were created to give a deterministic result. When and priorities were created to give a deterministic result. When
there is a collision, a notification MUST BE sent to the original there is a collision, a notification MUST BE sent to the original
client to give the original client a chance to deal with the issues client to give the original client a chance to deal with the issues
surrounding the collision. The original client may need to fix their surrounding the collision. The original client may need to fix their
state. state.
Ephemeral-REQ-11: The requirement to support multi-headed control is Ephemeral-REQ-12: The requirement to support multi-headed control is
required for collisions and the priority resolution of collisions. required for collisions and the priority resolution of collisions.
Multi-headed control is not tied to ephemeral state. I2RS is not Multi-headed control is not tied to ephemeral state. I2RS is not
mandating how AAA supports priority. Mechanisms which prevent mandating how AAA supports priority. Mechanisms which prevent
collisions of two clients trying the same node of data are the focus. collisions of two clients trying the same node of data are the focus.
Ephemeral-REQ-12: If two clients have the same priority, the Ephemeral-REQ-13: If two clients have the same priority, the
architecture says the first one wins. The I2RS protocol has this architecture says the first one wins. The I2RS protocol has this
requirement to prevent was the oscillation between clients. If one requirement to prevent was the oscillation between clients. If one
uses the last wins scenario, you may oscillate. That was our uses the last wins scenario, you may oscillate. That was our
opinion, but a design which prevents oscillation is the key point. opinion, but a design which prevents oscillation is the key point.
8. Multiple Message Transactions 8. Multiple Message Transactions
Ephemeral-REQ-13: Section 7.9 of the [I-D.ietf-i2rs-architecture] Ephemeral-REQ-14: Section 7.9 of the [I-D.ietf-i2rs-architecture]
states the I2RS architecture does not include multi-message atomicity states the I2RS architecture does not include multi-message atomicity
and roll-back mechanisms. I2RS notes multiple operations in one or and roll-back mechanisms. I2RS notes multiple operations in one or
more messages handling can handle errors within the set of operations more messages handling can handle errors within the set of operations
in many ways. No multi-message commands SHOULD cause errors to be in many ways. No multi-message commands SHOULD cause errors to be
inserted into the I2RS ephemeral data-store. inserted into the I2RS ephemeral data-store.
Explanation:
I2RS suggests the following are some of the potential error handling
techniques for multiple message sent to the I2RS client:
1. Perform all or none: All operations succeed or none of them will
be applied. This useful when there are mutual dependencies.
2. Perform until error: Operations are applied in order, and when
error occurs the processing stops. This is useful when
dependencies exist between multiple-message operations, and order
is important.
3. Perform all storing errors: Perform all actions storing error
indications for errors. This method can be used when there are
no dependencies between operations, and the client wants to sort
it out.
Is important to reliability of the data store that none of these
error handling for multiple operations in one more multiple messages
cause errors into be insert the I2RS ephemeral data-store.
Discussion of Current NETCONF/RESTCONF versus
RESTCONF does an atomic action within a http session, and NETCONF has
atomic actions within a commit. These features may be used to
perform these features.
I2RS processing is dependent on the I2RS model. The I2RS model must
consider the dependencies within multiple operations work within a
model.
9. Pub/Sub Requirements Expanded for Ephemeral State 9. Pub/Sub Requirements Expanded for Ephemeral State
I2RS clients require the ability to monitor changes to ephemeral I2RS clients require the ability to monitor changes to ephemeral
state. While subscriptions are well defined for receiving state. While subscriptions are well defined for receiving
notifications, the need to create a notification set for all notifications, the need to create a notification set for all
ephemeral configuration state may be overly burdensome to the user. ephemeral configuration state may be overly burdensome to the user.
There is thus a need for a general subscription mechanism that can There is thus a need for a general subscription mechanism that can
provide notification of changed state, with sufficient information to provide notification of changed state, with sufficient information to
permit the client to retrieve the impacted nodes. This should be permit the client to retrieve the impacted nodes. This should be
 End of changes. 29 change blocks. 
69 lines changed or deleted 57 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/