YANG Instance Data File Format
draft-ietf-netmod-yang-instance-file-format-10
Document Type Active Internet-Draft (netmod WG)
Last updated 2020-03-20
Replaces draft-lengyel-netmod-yang-instance-data
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized bibtex
Yang Validation ☯ 0 errors, 0 warnings.
Reviews
YANGDOCTORS Last Call Review (of -04): Ready with Issues
Additional URLs
- Yang catalog entry for ietf-yang-instance-data@2020-03-19.yang
- Yang impact analysis for draft-ietf-netmod-yang-instance-file-format
- Mailing list discussion
Stream WG state In WG Last Call
Document shepherd Kent Watsen
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to Kent Watsen <kent+ietf@watsen.net>
Email authors Email WG IPR References Referenced by Nits 
Netmod                                                        B. Lengyel
Internet-Draft                                                  Ericsson
Intended status: Standards Track                               B. Claise
Expires: September 21, 2020                          Cisco Systems, Inc.
                                                          March 20, 2020

                     YANG Instance Data File Format
             draft-ietf-netmod-yang-instance-file-format-10

Abstract

   There is a need to document data defined in YANG models when a live
   server is not available.  Data is often needed already at design or
   implementation time or needed by groups that do not have a live
   running server available.  This document specifies a standard file
   format for YANG instance data, which follows the syntax and semantics
   of existing YANG models, and annotates it with metadata.

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 September 21, 2020.

Copyright Notice

   Copyright (c) 2020 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

Lengyel & Claise       Expires September 21, 2020               [Page 1]
Internet-Draft             YANG Instance Data                 March 2020

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

Table of Contents

   1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Principles  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Delivery of Instance Data . . . . . . . . . . . . . . . .   4
     2.3.  Data Life cycle . . . . . . . . . . . . . . . . . . . . .   5
   3.  Instance Data File Format . . . . . . . . . . . . . . . . . .   5
     3.1.  Specifying the Content Schema . . . . . . . . . . . . . .   7
       3.1.1.  Inline Method . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  Simplified-Inline Method  . . . . . . . . . . . . . .   8
       3.1.3.  URI Method  . . . . . . . . . . . . . . . . . . . . .   8
     3.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  YANG Instance Data Model  . . . . . . . . . . . . . . . . . .  12
     4.1.  Tree Diagram  . . . . . . . . . . . . . . . . . . . . . .  12
     4.2.  YANG Model  . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
     6.1.  URI Registration  . . . . . . . . . . . . . . . . . . . .  19
     6.2.  YANG Module Name Registration . . . . . . . . . . . . . .  20
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  20
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  21
   Appendix A.  Changes between revisions  . . . . . . . . . . . . .  22
   Appendix B.  Backwards Compatibility  . . . . . . . . . . . . . .  24
   Appendix C.  Detailed Use Cases - Non-Normative . . . . . . . . .  25
     C.1.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . .  25
       C.1.1.  Use Case 1: Early Documentation of Server
               Capabilities  . . . . . . . . . . . . . . . . . . . .  25
       C.1.2.  Use Case 2: Preloading Data . . . . . . . . . . . . .  26
       C.1.3.  Use Case 3: Documenting Factory Default Settings  . .  27
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  27

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
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
Show full document text
RFC Editor IASA & IETF LLC IETF Trust IRTF IETF IESG IAB IANA Privacy Statement IETF Tools