YANG Data Extensions
draft-bierman-netmod-yang-data-ext-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

draft-bierman-netmod-yang-data-ext-00.txt:
xym 0.4:
Extracting 'yang-data-ext@2017-07-03.yang'


yang-data-ext@2017-07-03.yang:
pyang 1.7.3: pyang --verbose --ietf -p {libs} {model}:
yang-data-ext@2017-07-03.yang:1: warning: RFC 6087: 4.1: the module name should start with one of the strings "ietf-" or "iana-"

yanglint 0.13.69: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors

Network Working Group                                         A. Bierman
Internet-Draft                                                 YumaWorks
Intended status: Standards Track                            July 3, 2017
Expires: January 4, 2018

                          YANG Data Extensions
                 draft-bierman-netmod-yang-data-ext-00

Abstract

   This document describes YANG mechanisms for extending the utility of
   the 'yang-data' extension statement defined in RFC 8040.

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 January 4, 2018.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bierman                  Expires January 4, 2018                [Page 1]
Internet-Draft            YANG Data Extensions                 July 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.1.  NETCONF . . . . . . . . . . . . . . . . . . . . . . .   2
       1.1.2.  YANG  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Restrictions on Conceptual YANG Data  . . . . . . . . . .   3
     2.2.  YANG Data Extensions Module . . . . . . . . . . . . . . .   3
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  YANG Module Registry  . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   There is a need for standard mechanisms to allow the definition of
   abstract data that is not intended to be implemented as configuration
   data or state data.  The 'yang-data' extension statement from RFC
   8040 [RFC8040] is defined for this purpose, however it is limited in
   its functionality.

   The intended use of the "yang-data" extension is to model all or part
   of a protocol message, such as the "errors" definition in ietf-
   restconf.yang [RFC8040].  However, protocols are often layered such
   that the header or payload portions of the message can be extended by
   external documents.  The YANG statements that model a protocol need
   to support this extensibility that is already found in that protocol.

   This document defines a new YANG extension statement called
   "augment-yang-data", which allows abstract data structures to be
   augmented from external modules, similar to the existing YANG
   "augment" statement, which cannot be used because a YANG compiler or
   other tool is not required to understand the "yang-data" extension.

1.1.  Terminology

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

1.1.1.  NETCONF

   The following terms are defined in [RFC6241]:

   o  configuration data

Bierman                  Expires January 4, 2018                [Page 2]
Internet-Draft            YANG Data Extensions                 July 2017

   o  state data

1.1.2.  YANG