NETCONF Changes to Support I2RS Protocol
draft-hares-netconf-i2rs-protocol-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-15
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: May 19, 2017                                           Ericsson
                                                       November 15, 2016

                NETCONF Changes to Support I2RS Protocol
                draft-hares-netconf-i2rs-protocol-00.txt

Abstract

   This document describes a NETCONF capabiilty to support the Interface
   to Routing system (I2RS) protocol requirements for I2RS protocol
   version 1.  The I2RS protocol is a re-use higher layer protocol which
   defines extensions to other protocols (NETCONF and RESTCONf) and
   extensions to the Yang Data Modeling language.

   The I2RS protocol supports ephemeral state datastores as control
   plane datastores.  Initial versions of this document contain
   descriptions of the ephemeral datastore.  Future versions may move
   this description to NETMOD datastore description documents.

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 19, 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

Hares & Dass              Expires May 19, 2017                  [Page 1]
Internet-Draft             I2RS Protocol Yang              November 2016

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions Related to Ephemeral Configuration  . . . . . . .   4
     2.1.  Requirements language . . . . . . . . . . . . . . . . . .   4
     2.2.  I2RS Definitions  . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview of Changes . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  I2RS protocol requirements  . . . . . . . . . . . . . . .   6
     3.2.  NETCONF Features and Extensions . . . . . . . . . . . . .   7
     3.3.  RESTCONF features and Extensions  . . . . . . . . . . . .   8
     3.4.  Assumptions on Data Store Model Melee . . . . . . . . . .   8
   4.  NETCONF protocol extensions for the ephemeral datastore . . .   9
     4.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Dependencies  . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  Capability identifier . . . . . . . . . . . . . . . . . .  11
     4.4.  New Operations  . . . . . . . . . . . . . . . . . . . . .  11
     4.5.  Modification to existing operations . . . . . . . . . . .  11
       4.5.1.  <get-config>  . . . . . . . . . . . . . . . . . . . .  11
       4.5.2.  <edit-config> . . . . . . . . . . . . . . . . . . . .  12
       4.5.3.  <copy-config> . . . . . . . . . . . . . . . . . . . .  13
       4.5.4.  <delete-config> . . . . . . . . . . . . . . . . . . .  13
       4.5.5.  <lock> and <unlock> . . . . . . . . . . . . . . . . .  13
       4.5.6.  <get> . . . . . . . . . . . . . . . . . . . . . . . .  13
       4.5.7.  <close-session> and <kill-session>  . . . . . . . . .  13
     4.6.  Interactions with Capabilities  . . . . . . . . . . . . .  13
       4.6.1.  writable-running and candidate datastore  . . . . . .  14
       4.6.2.  confirmed commmit . . . . . . . . . . . . . . . . . .  14
       4.6.3.  rollback-on-error . . . . . . . . . . . . . . . . . .  14
       4.6.4.  validate  . . . . . . . . . . . . . . . . . . . . . .  14
       4.6.5.  Distinct Startup Capability . . . . . . . . . . . . .  15
       4.6.6.  URL capability and XPATH capability . . . . . . . . .  15
Show full document text