Binary Encoding for NETCONF
draft-mahesh-netconf-binary-encoding-00

Document Type Active Internet-Draft (individual)
Last updated 2018-02-21
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 WG                                               M. Jethanandani
Internet-Draft
Intended status: Standards Track                                  J. Lam
Expires: August 27, 2018                                        A. Leung
                                                     Cisco Systems, Inc.
                                                       February 23, 2018

                      Binary Encoding for NETCONF
                draft-mahesh-netconf-binary-encoding-00

Abstract

   This document describes a method by which a NETCONF [RFC6241] client
   and server can negotiate an alternate form of encoding.

   This document updates RFC 6241.

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 August 27, 2018.

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

Jethanandani, et al.     Expires August 27, 2018                [Page 1]
Internet-Draft               Binary Encoding               February 2018

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions and Acronyms  . . . . . . . . . . . . . . . .   2
   2.  Protocol Negotiation  . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.2.  Dependencies  . . . . . . . . . . . . . . . . . . . .   3
       2.1.3.  Capability Identifier . . . . . . . . . . . . . . . .   3
       2.1.4.  New Operation . . . . . . . . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  NETCONF Capability URNs . . . . . . . . . . . . . . . . .   5
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   NETCONF [RFC6241], by default, supports XML encoding for its payload.
   However, XML can be very verbose, specially for operational data.
   That combined with parsing of tags leads to slow processing of the
   data.  This document proposes a mechanism by which clients and
   servers can negotiate an alternate form of encoding, e.g.  binary
   encoding, and use that to exchange data.  Binary encoding can reduce
   the physical size of the data exchanged, in some cases by as much as
   66%, and improve the time that is required to process the data, while
   preserving the original data.

   Several binary encoding mechanisms have been proposed, including CBOR
   [RFC7049].  This document does not advocate any particular binary
   encoding format.  Instead, it leaves it up to the negotiation between
   client and server to decide the form of encoding.  For an example of
   how to encode YANG in CBOR format, see CBOR Encoding of Data Modeled
   with YANG [I-D.ietf-core-yang-cbor].

1.1.  Definitions and Acronyms

2.  Protocol Negotiation

   NETCONF clients and servers exchange a hello as part of establishing
   a connection.  As part of the hello exchange, each of them advertises

Jethanandani, et al.     Expires August 27, 2018                [Page 2]
Internet-Draft               Binary Encoding               February 2018

   their set of capabilities.  This draft suggests advertisement of the
   following additional capability.

2.1.  Encoding

2.1.1.  Overview

   The :encoding capability indicates what encoding format each side is
Show full document text