Inline Action Capability for NETCONF
draft-zheng-netconf-inline-action-capability-02

Document Type Active Internet-Draft (individual)
Last updated 2018-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf 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)
NETCONF Working Group                                           W. Zheng
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                                  Huawei
Expires: May 8, 2019                                    November 4, 2018

                  Inline Action Capability for NETCONF
            draft-zheng-netconf-inline-action-capability-02

Abstract

   NETCONF provides mechanism to install configuration of network
   devices.  In many cases, it is required that the same configuration
   repeats on many interfaces.  In the absence of protocol semantics for
   performing operations with group-specific scope, this results in
   either a significant amount of signaling traffic and configuration
   template applying on a periodic basis or large packet size between a
   given network management system and a network devices.  This document
   defines optimizations to the NETCONF protocol operations for
   performing operations with group-specific scope with the use of a
   group identifier.

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 https://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 8, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Zheng & Wu                 Expires May 8, 2019                  [Page 1]
Internet-Draft          Inline Action Capability           November 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Inline-Action Capability  . . . . . . . . . . . . . . . . . .   3
     2.1.  Description . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Dependencies  . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Capability Identifier . . . . . . . . . . . . . . . . . .   3
     2.4.  New Operations  . . . . . . . . . . . . . . . . . . . . .   3
     2.5.  Modifications to Existing Operations  . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  NETCONF Capability URN  . . . . . . . . . . . . . . . . .   9
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   NETCONF provides mechanism to install configuration of network
   devices.  In many cases, it is required that the same configuration
   repeats on many interfaces, e.g., configure multiple VLAN ranges on
   the same Trunk interface.  In the absence of protocol semantics for
   performing operations with group-specific scope, using configuration
   template to replicate multiple copies on the same interface result in
   either a significant amount of signaling traffic(e.g, multiple data
   retrieval for vlan tag configuration on the interface) on a periodic
   basis or large packet size (e.g,edit-config operation related to
   protocol message) between a given network management system and a
   network devices.

   This document defines optimizations to the NETCONF protocol
   operation(i.e., inline action operation) for performing bulk
   operations with group-specific scope with the use of a group
   identifier and allows NETCONF protocol operation work together with
   inline action operation that apply to different conceptual node in
   the underlying data model in one transaction.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP

Zheng & Wu                 Expires May 8, 2019                  [Page 2]
Show full document text