RFC 8340: YANG Tree Diagrams
In plain English — editorial summary, not part of the RFC
This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language.
Document record
- Document ID
- RFC8340
- Published
- March 2018
- Authors
- M. Bjorklund; L. Berger
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- BCP215
- Updated by:
- RFC 8791
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8341Network Configuration Access Control ModelCurrent
March 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
- RFC 8343A YANG Data Model for Interface ManagementCurrent
March 2018
- RFC 8344A YANG Data Model for IP ManagementCurrent
March 2018
- RFC 8334Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)Current
March 2018
- RFC 8348A YANG Data Model for Hardware ManagementCurrent
March 2018
- RFC 8349A YANG Data Model for Routing Management (NMDA Version)Current
March 2018
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?