draft-ietf-i2rs-ephemeral-state-11.txt   draft-ietf-i2rs-ephemeral-state-12.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 27, 2016 Huawei Expires: January 1, 2017 Huawei
June 25, 2016 June 30, 2016
I2RS Ephemeral State Requirements I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-11 draft-ietf-i2rs-ephemeral-state-12
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 December 27, 2016. This Internet-Draft will expire on January 1, 2017.
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 27 skipping to change at page 2, line 27
6. RESTCONF Features for Ephemeral State . . . . . . . . . . . . 6 6. RESTCONF Features for Ephemeral State . . . . . . . . . . . . 6
7. Requirements regarding Supporting Multi-Head Control via 7. Requirements regarding Supporting Multi-Head Control via
Client Priority . . . . . . . . . . . . . . . . . . . . . . . 6 Client Priority . . . . . . . . . . . . . . . . . . . . . . . 6
8. Multiple Message Transactions . . . . . . . . . . . . . . . . 7 8. Multiple Message Transactions . . . . . . . . . . . . . . . . 7
9. Pub/Sub Requirements Expanded for Ephemeral State . . . . . . 7 9. Pub/Sub Requirements Expanded for Ephemeral State . . . . . . 7
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. Security Considerations . . . . . . . . . . . . . . . . . . . 8 11. Security Considerations . . . . . . . . . . . . . . . . . . . 8
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
13.1. Normative References: . . . . . . . . . . . . . . . . . 9 13.1. Normative References: . . . . . . . . . . . . . . . . . 9
13.2. Informative References . . . . . . . . . . . . . . . . . 10 13.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
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 3, line 11 skipping to change at page 3, line 11
NETCONF and RESTCONF are a good starting basis for the I2RS protocol, NETCONF and RESTCONF are a good starting basis for the I2RS protocol,
the creation of the I2RS protocol implementations requires that the the creation of the I2RS protocol implementations requires that the
I2RS requirements I2RS requirements
1. select features from YANG, NETCONF, and RESTCONF per version of 1. select features from YANG, NETCONF, and RESTCONF per version of
the I2RS protocol (See sections 4, 5, and 6) the I2RS protocol (See sections 4, 5, and 6)
2. propose additions to YANG, NETCONF, and RESTCONF per version of 2. propose additions to YANG, NETCONF, and RESTCONF per version of
the I2RS protocol for key functions (ephemeral state, protocol the I2RS protocol for key functions (ephemeral state, protocol
security, publication/subscription service, traceability), security, publication/subscription service, traceability),
3. suggest protocol strawman as ideas for the NETCONF, RESTCONF, and 3. suggest protocol strawman (e.g.
YANG changes. [I-D.hares-i2rs-protocol-strawman]) as ideas for the NETCONF,
RESTCONF, and YANG changes.
The purpose of these requirements and the suggested protocol straw The purpose of these requirements and the suggested protocol straw
man is to provide a quick turnaround on creating the I2RS protocol. man is to provide a quick turnaround on creating the I2RS protocol.
Support for ephemeral state is I2RS protocol requirement that Support for ephemeral state is I2RS protocol requirement that
requires datastore changes (see section 3), Yang additions (see requires datastore changes (see section 3), YANG additions (see
section 4), NETCONF additions (see section 5), and RESTCONF additions section 4), NETCONF additions (see section 5), and RESTCONF additions
(see section 6). (see section 6).
Sections 7-9 provide details that expand upon the changes in sections Sections 7-9 provide details that expand upon the changes in sections
3-6 to clarify requirements discussed by the I2RS and NETCONF working 3-6 to clarify requirements discussed by the I2RS and NETCONF working
groups. Sections 7 provide additional requirements that detail how groups. Sections 7 provide additional requirements that detail how
write-conflicts should be resolved if two I2RS client write the same write-conflicts should be resolved if two I2RS client write the same
data. Section 8 provides an additional requirement that details on data. Section 8 provides an additional requirement that details on
I2RS support of multiple message transactions. Section 9 highlights I2RS support of multiple message transactions. Section 9 highlights
two requirements in the I2RS publication/subscription requirements two requirements in the I2RS publication/subscription requirements
skipping to change at page 5, line 46 skipping to change at page 5, line 46
Ephemeral-REQ-05: I2RS pub-sub, logging, RPC or other mechanisms may Ephemeral-REQ-05: I2RS pub-sub, logging, RPC or other mechanisms may
lead to undesirable or unsustainable resource consumption on a system lead to undesirable or unsustainable resource consumption on a system
implementing an I2RS Agent. It is RECOMMENDED that mechanisms be implementing an I2RS Agent. It is RECOMMENDED that mechanisms be
made available to permit prioritization of I2RS operations, when made available to permit prioritization of I2RS operations, when
appropriate, to permit implementations to shed work load when appropriate, to permit implementations to shed work load when
operating under constrained resources. An example of such a work operating under constrained resources. An example of such a work
shedding mechanism is rate-limiting. shedding mechanism is rate-limiting.
3.3. Hierarchy 3.3. Hierarchy
Ephemeral-REQ-06: The ability to augment Yang schema nodes with Ephemeral-REQ-06: The ability to:
additional Yang Schema nodes that have the property of being
ephemeral. 1. to define a YANG module or submodule schema that only contains
data nodes with the property of being ephemeral, and
2. to augment a YANG data model with additional YANG schema nodes
that have the property of being ephemeral.
3.4. Ephemeral Configuration overlapping Local Configuration 3.4. Ephemeral Configuration overlapping Local Configuration
Ephemeral-REQ-07: Ephemeral configuration state could override Ephemeral-REQ-07: Ephemeral configuration state could override
overlapping local configuration state, or vice-versa. overlapping local configuration state, or vice-versa.
Implementations MUST provide a mechanism to choose which takes Implementations MUST provide a mechanism to choose which takes
precedence. This mechanism MUST include local configuration (policy) precedence. This mechanism MUST include local configuration (policy)
and MAY be provided via the I2RS protocol mechanisms. and MAY be provided via the I2RS protocol mechanisms.
4. YANG Features for Ephemeral State 4. YANG Features for Ephemeral State
Ephemeral-REQ-08: Yang MUST have a way to indicate in a data model Ephemeral-REQ-08: YANG MUST have a way to indicate in a data model
that schema nodes have the following properties: ephemeral, writable/ that schema nodes have the following properties: ephemeral, writable/
not-writable, and status/configuration. not-writable, and status/configuration.
5. NETCONF Features for Ephemeral State 5. NETCONF Features for Ephemeral State
Ephemeral-REQ-09: The conceptual changes to NETCONF Ephemeral-REQ-09: The conceptual changes to NETCONF
1. Support for communication mechanisms to enable an I2RS client to 1. Support for communication mechanisms to enable an I2RS client to
determine that an I2RS agent supports the mechanisms needed for determine that an I2RS agent supports the mechanisms needed for
I2RS operation. I2RS operation.
skipping to change at page 7, line 19 skipping to change at page 7, line 19
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-12, Ephemeral-REQ-13, and Ephemeral-REQ-14. Ephemeral-REQ-12, Ephemeral-REQ-13, and Ephemeral-REQ-14.
Ephemeral-REQ-12: When a collision occurs as two clients are trying Ephemeral-REQ-12: 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 (which includes indicating data
client to give the original client a chance to deal with the issues node the collision occurred on) MUST BE sent to the original 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-13: The requirement to support multi-headed control is Ephemeral-REQ-13: 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 to modify the same node of data are
the focus.
Ephemeral-REQ-14: If two clients have the same priority, the Ephemeral-REQ-14: A deterministic conflict resolution mechanism MUST
architecture says the first one wins. The I2RS protocol has this be provided to handle the error scenario that two clients, with the
requirement to prevent oscillations between clients. If one uses the same priority, update the same configuration data node. The I2RS
last wins scenario, you may oscillate. That was our opinion, but a architecture gives one way that this could be achieved, by specifying
design which prevents oscillation is the key point. that the first update wins. Other solutions, that prevent
oscillation of the config data node, are also acceptable.
8. Multiple Message Transactions 8. Multiple Message Transactions
Ephemeral-REQ-15: Section 7.9 of the [I-D.ietf-i2rs-architecture] Ephemeral-REQ-15: 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 state.
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
skipping to change at page 8, line 49 skipping to change at page 9, line 4
I2RS mailing list for an architecture that was for a long period of I2RS mailing list for an architecture that was for a long period of
time a moving target. Some individuals in particular warrant time a moving target. Some individuals in particular warrant
specific mention for their extensive help in providing the basis for specific mention for their extensive help in providing the basis for
this document: this document:
o Alia Atlas o Alia Atlas
o Andy Bierman o Andy Bierman
o Martin Bjorklund o Martin Bjorklund
o Dean Bogdanavich o Dean Bogdanavich
o Rex Fernando o Rex Fernando
o Joel Halpern o Joel Halpern
o Thomas Nadeau o Thomas Nadeau
o Juergen Schoenwaelder o Juergen Schoenwaelder
o Kent Watsen o Kent Watsen
o Robert Wilton
13. References 13. References
13.1. Normative References: 13.1. Normative References:
[I-D.ietf-i2rs-architecture] [I-D.ietf-i2rs-architecture]
Atlas, A., Halpern, J., Hares, S., Ward, D., and T. Atlas, A., Halpern, J., Hares, S., Ward, D., and T.
Nadeau, "An Architecture for the Interface to the Routing Nadeau, "An Architecture for the Interface to the Routing
System", draft-ietf-i2rs-architecture-15 (work in System", draft-ietf-i2rs-architecture-15 (work in
progress), April 2016. progress), April 2016.
skipping to change at page 9, line 50 skipping to change at page 10, line 12
Information Model", draft-ietf-i2rs-traceability-11 (work Information Model", draft-ietf-i2rs-traceability-11 (work
in progress), May 2016. in progress), May 2016.
[I-D.ietf-netconf-call-home] [I-D.ietf-netconf-call-home]
Watsen, K., "NETCONF Call Home and RESTCONF Call Home", Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
draft-ietf-netconf-call-home-17 (work in progress), draft-ietf-netconf-call-home-17 (work in progress),
December 2015. December 2015.
[I-D.ietf-netconf-restconf] [I-D.ietf-netconf-restconf]
Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", draft-ietf-netconf-restconf-13 (work in Protocol", draft-ietf-netconf-restconf-14 (work in
progress), April 2016. progress), June 2016.
[I-D.ietf-netconf-server-model] [I-D.ietf-netconf-server-model]
Watsen, K. and J. Schoenwaelder, "NETCONF Server and Watsen, K. and J. Schoenwaelder, "NETCONF Server and
RESTCONF Server Configuration Models", draft-ietf-netconf- RESTCONF Server Configuration Models", draft-ietf-netconf-
server-model-09 (work in progress), March 2016. server-model-09 (work in progress), March 2016.
[I-D.ietf-netconf-yang-library] [I-D.ietf-netconf-yang-library]
Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module Bierman, A., Bjorklund, M., and K. Watsen, "YANG Module
Library", draft-ietf-netconf-yang-library-06 (work in Library", draft-ietf-netconf-yang-library-06 (work in
progress), April 2016. progress), April 2016.
[I-D.ietf-netconf-yang-patch] [I-D.ietf-netconf-yang-patch]
Bierman, A., Bjorklund, M., and K. Watsen, "YANG Patch Bierman, A., Bjorklund, M., and K. Watsen, "YANG Patch
Media Type", draft-ietf-netconf-yang-patch-08 (work in Media Type", draft-ietf-netconf-yang-patch-09 (work in
progress), March 2016. progress), June 2016.
[I-D.ietf-netconf-yang-push] [I-D.ietf-netconf-yang-push]
Clemm, A., Prieto, A., Voit, E., Tripathy, A., and E. Clemm, A., Prieto, A., Voit, E., Tripathy, A., and E.
Nilsen-Nygaard, "Subscribing to YANG datastore push Nilsen-Nygaard, "Subscribing to YANG datastore push
updates", draft-ietf-netconf-yang-push-03 (work in updates", draft-ietf-netconf-yang-push-03 (work in
progress), June 2016. progress), June 2016.
[I-D.ietf-netconf-zerotouch] [I-D.ietf-netconf-zerotouch]
Watsen, K. and M. Abrahamsson, "Zero Touch Provisioning Watsen, K. and M. Abrahamsson, "Zero Touch Provisioning
for NETCONF or RESTCONF based Management", draft-ietf- for NETCONF or RESTCONF based Management", draft-ietf-
 End of changes. 17 change blocks. 
26 lines changed or deleted 36 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/