draft-ietf-i2rs-ephemeral-state-22.txt   draft-ietf-i2rs-ephemeral-state-23.txt 
I2RS working group J. Haas I2RS working group J. Haas
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Informational S. Hares Intended status: Informational S. Hares
Expires: May 18, 2017 Huawei Expires: May 20, 2017 Huawei
November 14, 2016 November 16, 2016
I2RS Ephemeral State Requirements I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-22.txt draft-ietf-i2rs-ephemeral-state-23.txt
Abstract Abstract
The I2RS (interface to the routing system) Architecture document The I2RS (interface to the routing system) Architecture document
(RFC7921) abstractly describes a number of requirements for ephemeral (RFC7921) abstractly describes a number of requirements for ephemeral
state (in terms of capabilities and behaviors) which any protocol state (in terms of capabilities and behaviors) which any protocol
suite attempting to meet the needs of I2RS has to provide. This suite attempting to meet the needs of I2RS has to provide. This
document describes, in detail, requirements for ephemeral state for document describes, in detail, requirements for ephemeral state for
those implementing the I2RS protocol. those implementing the I2RS protocol.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 May 18, 2017. This Internet-Draft will expire on May 20, 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 42 skipping to change at page 2, line 42
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 [RFC7921] abstractly documents a number of requirements for document [RFC7921] abstractly documents a number of requirements for
implementing the I2RS, and defines ephemeral state as "state which implementing the I2RS, and defines ephemeral state as "state which
does not survive the reboot of a routing device or the reboot of the does not survive the reboot of a routing device or the reboot of the
software handling the I2RS software on a routing device" (see section software handling the I2RS software on a routing device" (see section
1.1 of [RFC7921]). Section 2 describes the specific requirements 1.1 of [RFC7921]). Section 2 describes the specific requirements
which the I2RS Working group has identified based on the I2RS which the I2RS working group has identified based on the I2RS
architecture's abstract requirements. architecture's abstract requirements.
The I2RS Working Group has chosen to use the YANG data modeling The I2RS Working Group has chosen to use the YANG data modeling
language [RFC7950] as the basis to implement its mechanisms. language [RFC7950] as the basis to implement its mechanisms.
Additionally, the I2RS Working group has chosen to re-use two Additionally, the I2RS Working group has chosen to re-use two
existing protocols, NETCONF [RFC6241] and its similar but lighter- existing protocols, NETCONF [RFC6241] and its similar but lighter-
weight relative RESTCONF [I-D.ietf-netconf-restconf], as the weight relative RESTCONF [I-D.ietf-netconf-restconf], as the
protocols for carrying I2RS. protocols for carrying I2RS.
skipping to change at page 6, line 50 skipping to change at page 6, line 50
determine that an I2RS agent supports the mechanisms needed for determine that an I2RS agent supports the mechanisms needed for
I2RS operation. I2RS operation.
2. The ephemeral state MUST support notification of write conflicts 2. The ephemeral state MUST support notification of write conflicts
using the priority requirements defined in section 7 below (see using the priority requirements defined in section 7 below (see
requirements Ephemeral-REQ-11 through Ephemeral-REQ-14). requirements Ephemeral-REQ-11 through Ephemeral-REQ-14).
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-11: The following requirements must be supported by the Ephemeral-REQ-11: The following requirements must be supported by the
I2RS protocol in order to support I2RS client identity and priority: I2RS protocol in order to support I2RS client identity and priority:
o the data nodes MUST store I2RS client identity and MAY store the o the data nodes MUST store I2RS client identity and MAY store the
effective priority at the time the data node is stored. effective priority at the time the data node is stored.
skipping to change at page 10, line 22 skipping to change at page 10, line 22
13.1. Normative References: 13.1. Normative References:
[I-D.ietf-i2rs-protocol-security-requirements] [I-D.ietf-i2rs-protocol-security-requirements]
Hares, S., Migault, D., and J. Halpern, "I2RS Security Hares, S., Migault, D., and J. Halpern, "I2RS Security
Related Requirements", draft-ietf-i2rs-protocol-security- Related Requirements", draft-ietf-i2rs-protocol-security-
requirements-17 (work in progress), September 2016. requirements-17 (work in progress), September 2016.
[I-D.ietf-i2rs-security-environment-reqs] [I-D.ietf-i2rs-security-environment-reqs]
Migault, D., Halpern, J., and S. Hares, "I2RS Environment Migault, D., Halpern, J., and S. Hares, "I2RS Environment
Security Requirements", draft-ietf-i2rs-security- Security Requirements", draft-ietf-i2rs-security-
environment-reqs-01 (work in progress), April 2016. environment-reqs-02 (work in progress), November 2016.
[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-18 (work in Protocol", draft-ietf-netconf-restconf-18 (work in
progress), October 2016. progress), October 2016.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <http://www.rfc-editor.org/info/rfc6241>.
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 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/