[netmod] RFC 9195 on A File Format for YANG Instance Data

rfc-editor@rfc-editor.org Thu, 17 February 2022 20:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB833A12EF; Thu, 17 Feb 2022 12:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74F_-G954Isx; Thu, 17 Feb 2022 12:56:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 227EC3A12EB; Thu, 17 Feb 2022 12:56:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 6E4BD6A9C2; Thu, 17 Feb 2022 12:56:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, netmod@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220217205603.6E4BD6A9C2@rfc-editor.org>
Date: Thu, 17 Feb 2022 12:56:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/52uMU-mZCutVU5a4T6aqMzbcLQg>
Subject: [netmod] RFC 9195 on A File Format for YANG Instance Data
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2022 20:56:16 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9195

        Title:      A File Format for YANG Instance Data 
        Author:     B. Lengyel,
                    B. Claise
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2022
        Mailbox:    balazs.lengyel@ericsson.com,
                    benoit.claise@huawei.com
        Pages:      24
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netmod-yang-instance-file-format-21.txt

        URL:        https://www.rfc-editor.org/info/rfc9195

        DOI:        10.17487/RFC9195

There is a need to document data defined in YANG models at design
time, implementation time, or when a live server is unavailable. 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.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC