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

The information below is for an old version of the document
Document Type Active Internet-Draft (i2rs WG)
Last updated 2016-03-21
Replaces draft-haas-i2rs-ephemeral-state-reqs
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Aug 2016 - Request publication ... )
Revised I-D Needed - Issue raised by WG
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
I2RS working group                                               J. Haas
Internet-Draft                                                   Juniper
Intended status: Standards Track                                S. Hares
Expires: September 22, 2016                                       Huawei
                                                          March 21, 2016

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

Abstract

   This document covers requests to the netmod and netconf Working
   Groups for functionality to support the ephemeral state requirements
   to implement the I2RS architecture.

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 September 22, 2016.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Haas & Hares           Expires September 22, 2016               [Page 1]
Internet-Draft      I2RS Ephemeral State Requirements         March 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Review of Requirements from I2RS architecture document  . . .   3
   3.  Ephemeral State Requirements  . . . . . . . . . . . . . . . .   4
     3.1.  Persistence . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Constraints . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Hierarchy . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  changes to YANG . . . . . . . . . . . . . . . . . . . . .   5
       3.4.1.  Suggested Yang changes  . . . . . . . . . . . . . . .   5
       3.4.2.  Changes to Yang Under debate  . . . . . . . . . . . .   5
     3.5.  Minimal Changes to NETCONF for I2RS Protocol (v1) . . . .   6
       3.5.1.  dependencies  . . . . . . . . . . . . . . . . . . . .   6
       3.5.2.  New operations (under debate) . . . . . . . . . . . .   6
       3.5.3.  modified operations . . . . . . . . . . . . . . . . .   6
       3.5.4.  no supported operations . . . . . . . . . . . . . . .   6
       3.5.5.  interactions with capabilities (Some Debate)  . . . .   7
     3.6.  Changes to RESTCONF for I2RS Protocol (v1)  . . . . . . .   7
       3.6.1.  dependencies for RESTCONF . . . . . . . . . . . . . .   7
       3.6.2.  modification to context . . . . . . . . . . . . . . .   8
       3.6.3.  modification to existing operations . . . . . . . . .   8
     3.7.  Requirements regarding Identity, Secondary-Identity and
           Priority  . . . . . . . . . . . . . . . . . . . . . . . .   8
       3.7.1.  Identity Requirements . . . . . . . . . . . . . . . .   8
       3.7.2.  Priority Requirements . . . . . . . . . . . . . . . .   9
       3.7.3.  Transactions  . . . . . . . . . . . . . . . . . . . .  10
       3.7.4.  Subscriptions to Changed State Requirements . . . . .  10
   4.  Previously Considered Ideas . . . . . . . . . . . . . . . . .  11
     4.1.  A Separate Ephemeral Datastore  . . . . . . . . . . . . .  11
     4.2.  Panes of Glass/Overlay  . . . . . . . . . . . . . . . . .  12
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Normative References: . . . . . . . . . . . . . . . . . .  13
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  15

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
Show full document text