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

Document Type Active Internet-Draft (individual)
Last updated 2018-07-01
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
Updates: 6241 (if approved)                                       J. Lam
Intended status: Standards Track                                A. Leung
Expires: January 1, 2019                             Cisco Systems, Inc.
                                                              A. Bierman
                                                         YumaWorks, Inc.
                                                           June 30, 2018

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

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 January 1, 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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

Jethanandani, et al.     Expires January 1, 2019                [Page 1]
Internet-Draft               Binary Encoding                   June 2018

   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 . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Protocol Negotiation  . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Encoding  . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.2.  Example . . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.3.  Dependencies  . . . . . . . . . . . . . . . . . . . .   5
       2.1.4.  Capability Identifier . . . . . . . . . . . . . . . .   5
       2.1.5.  New Operations  . . . . . . . . . . . . . . . . . . .   6
       2.1.6.  Modification to Existing Operations . . . . . . . . .   6
       2.1.7.  Interactions with Other Capabilities  . . . . . . . .   6
     2.2.  CBOR and SID  . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  NETCONF Capability URNs . . . . . . . . . . . . . . . . .   6
     4.2.  New Registry  . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   NETCONF [RFC6241], by default, supports XML encoding for its payload.
   However, XML can be very verbose, specially for operational 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%, while
   preserving the original data.

   Several encoding mechanisms have been proposed, including CBOR
   [RFC7049] and JSON [RFC8259].  This document does not advocate any
   particular 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] and JSON
   Encoding of Data Modeled with YANG [RFC7951].

   This document updates NETCONF [RFC6241].

Jethanandani, et al.     Expires January 1, 2019                [Page 2]
Show full document text