RESTCONF Changes to Support I2RS Protocol
draft-hares-netconf-i2rs-restconf-02

Document Type Active Internet-Draft (individual)
Last updated 2017-03-29
Stream (None)
Intended RFC status (None)
Formats plain text pdf xml html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
I2RS working group                                              S. Hares
Internet-Draft                                                    Huawei
Intended status: Informational                                   A. Dass
Expires: September 30, 2017                                     Ericsson
                                                          March 29, 2017

               RESTCONF Changes to Support I2RS Protocol
                draft-hares-netconf-i2rs-restconf-02.txt

Abstract

   This document describes two RESTCONF optional capabilities (i2rs-
   control plane capability, ephemeral state capabilities) that are
   needed to support the I2RS protocol needs.

   The purpose of this draft is to kick-start the discussions with I2RS
   Working Group and NETCONF WG on these two capabilities.

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 30, 2017.

Copyright Notice

   Copyright (c) 2017 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

Hares & Dass           Expires September 30, 2017               [Page 1]
Internet-Draft             I2RS Protocol Yang                 March 2017

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Background on I2RS  . . . . . . . . . . . . . . . . . . .   3
     1.2.  Structure of draft  . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions and Background on I2RS  . . . . . . . . . . . . .   3
     2.1.  IETF Requirements language  . . . . . . . . . . . . . . .   3
     2.2.  I2RS Definitions  . . . . . . . . . . . . . . . . . . . .   3
     2.3.  I2RS protocol requirements  . . . . . . . . . . . . . . .   5
   3.  RESTCONF control plane datastore capability . . . . . . . . .   5
     3.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Dependencies  . . . . . . . . . . . . . . . . . . . . . .   6
     3.3.  New Operations  . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Modified Operations . . . . . . . . . . . . . . . . . . .   6
   4.  RESTCONF protocol extensions for the ephemeral datastore  . .   6
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Dependencies  . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Capability identifier . . . . . . . . . . . . . . . . . .   8
     4.4.  New Operations  . . . . . . . . . . . . . . . . . . . . .   8
     4.5.  Modification to data resources  . . . . . . . . . . . . .   8
     4.6.  Modification to existing operations . . . . . . . . . . .   8
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References: . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   This a proposal for the following two RESTCONF capabilities to
   augment RESTCONF [RFC8040] to support the first version of the I2RS
   protocol: Control plane datstore capability and ephemeral state
   capability.  The yang that supports this proposal is described in
   [I-D.hares-netmod-i2rs-yang].  This work is based on the datastore
   definitions in [I-D.ietf-netmod-revised-datastores].

   This draft parallels a similar proposal for NETCONF [RFC6241] is
   described in [I-D.hares-netconf-i2rs-protocol].  One difference
Show full document text