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

The information below is for an old version of the document
Document Type Active Internet-Draft (i2rs WG)
Last updated 2016-09-20 (latest revision 2016-08-29)
Replaces draft-haas-i2rs-ephemeral-state-reqs
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: Aug 2016 - Request publication ... )
Document shepherd Joe Clarke
Shepherd write-up Show (last changed 2016-08-29)
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Joe Clarke" <jclarke@cisco.com>
I2RS working group                                               J. Haas
Internet-Draft                                                   Juniper
Intended status: Standards Track                                S. Hares
Expires: March 2, 2017                                            Huawei
                                                         August 29, 2016

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

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

Haas & Hares              Expires March 2, 2017                 [Page 1]
Internet-Draft      I2RS Ephemeral State Requirements        August 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Review of Requirements from I2RS architecture document  . . .   3
   3.  Ephemeral State Requirements  . . . . . . . . . . . . . . . .   5
     3.1.  Persistence . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Constraints . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Hierarchy . . . . . . . . . . . . . . . . . . . . . . . .   6
     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 . . . . . . . . . . . . . . . . . . . . . . .   7
   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  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References:  . . . . . . . . . . . . . . . . .  10
     13.2.  Informative References . . . . . . . . . . . . . . . . .  10
   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 requirements.  Section 2 reviews 10 key
   requirements related to ephemeral state.

   The I2RS Working Group has chosen to use the YANG data modeling
   language [RFC6020] as the basis to implement its mechanisms.

   Additionally, the I2RS Working group has chosen to re-use two
   existing protocols, NETCONF [RFC6241] and its similar but lighter-
   weight relative RESTCONF [I-D.ietf-netconf-restconf], as the
   protocols for carrying I2RS.

   What does re-use of a protocol mean?  Re-use means that while YANG,
   NETCONF and RESTCONF are a good starting basis for the I2RS protocol,
   the creation of the I2RS protocol implementations requires that the
   I2RS requirements

Haas & Hares              Expires March 2, 2017                 [Page 2]
Internet-Draft      I2RS Ephemeral State Requirements        August 2016
Show full document text