I2RS Ephemeral State Requirements
draft-ietf-i2rs-ephemeral-state-23

Document Type Active Internet-Draft (i2rs WG)
Last updated 2017-07-20 (latest revision 2016-11-16)
Replaces draft-haas-i2rs-ephemeral-state-reqs
Stream IETF
Intended RFC status Informational
Formats plain text pdf xml html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Aug 2016 - Request publication ... )
Document shepherd Joe Clarke
Shepherd write-up Show (last changed 2016-09-22)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to "Joe Clarke" <jclarke@cisco.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
I2RS working group                                               J. Haas
Internet-Draft                                                   Juniper
Intended status: Informational                                  S. Hares
Expires: May 20, 2017                                             Huawei
                                                       November 16, 2016

                   I2RS Ephemeral State Requirements
                 draft-ietf-i2rs-ephemeral-state-23.txt

Abstract

   The I2RS (interface to the routing system) Architecture document
   (RFC7921) abstractly describes a number of requirements for ephemeral
   state (in terms of capabilities and behaviors) which any protocol
   suite attempting to meet the needs of I2RS has to provide.  This
   document describes, in detail, requirements for ephemeral state for
   those implementing the I2RS protocol.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 20, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Haas & Hares              Expires May 20, 2017                  [Page 1]
Internet-Draft      I2RS Ephemeral State Requirements      November 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Architectural Requirements for Ephemeral State  . . . . . . .   3
   3.  Ephemeral State Requirements  . . . . . . . . . . . . . . . .   4
     3.1.  Persistence . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Constraints . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Hierarchy . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Ephemeral Configuration overlapping Local Configuration .   6
   4.  YANG Features for Ephemeral State . . . . . . . . . . . . . .   6
   5.  NETCONF Features for Ephemeral State  . . . . . . . . . . . .   6
   6.  RESTCONF Features for Ephemeral State . . . . . . . . . . . .   6
   7.  Requirements regarding Supporting Multi-Head Control via
       client Priority . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Multiple Message Transactions . . . . . . . . . . . . . . . .   8
   9.  Pub/Sub Requirements Expanded for Ephemeral State . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   11. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     13.1.  Normative References:  . . . . . . . . . . . . . . . . .  10
     13.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The Interface to the Routing System (I2RS) Working Group is chartered
   with providing architecture and mechanisms to inject into and
   retrieve information from the routing system.  The I2RS Architecture
   document [RFC7921] abstractly documents a number of requirements for
   implementing the I2RS, and defines ephemeral state as "state which
   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
   1.1 of [RFC7921]).  Section 2 describes the specific requirements
   which the I2RS working group has identified based on the I2RS
   architecture's abstract requirements.

   The I2RS Working Group has chosen to use the YANG data modeling
Show full document text