RFC 9195: A File Format for YANG Instance Data
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9195
- Published
- February 2022
- Authors
- B. Lengyel; B. Claise
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9196YANG Modules Describing Capabilities for Systems and Datastore Update NotificationsCurrent
February 2022
- RFC 9197Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)Current
May 2022
- RFC 9198Advanced Unidirectional Route Assessment (AURA)Current
May 2022
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
- RFC 9181A Common YANG Data Model for Layer 2 and Layer 3 VPNsCurrent
February 2022
- RFC 9210DNS Transport over TCP - Operational RequirementsCurrent
March 2022
- RFC 9179A YANG Grouping for Geographic LocationsCurrent
February 2022
- RFC 9222Guidelines for Autonomic Service AgentsCurrent
March 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?