RFC 8345: A YANG Data Model for Network Topologies
In plain English — editorial summary, not part of the RFC
This document defines an abstract (generic, or base) YANG data model for network/service topologies and inventories. The data model serves as a base model that is augmented with technology-specific details in other, more specific topology and inventory data models.
Document record
- Document ID
- RFC8345
- Published
- March 2018
- Authors
- A. Clemm; J. Medved; R. Varga; N. Bahadur; H. Ananthakrishnan; X. Liu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 57
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8346A YANG Data Model for Layer 3 TopologiesCurrent
March 2018
- RFC 7752North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGPObsoleted
March 2016
- RFC 9656A YANG Data Model for Microwave TopologyCurrent
September 2024
- RFC 9666Area Proxy for IS-ISCurrent
October 2024
- RFC 9667Dynamic Flooding on Dense GraphsCurrent
October 2024
- RFC 3258Distributing Authoritative Name Servers via Shared Unicast AddressesCurrent
April 2002
- RFC 8347A YANG Data Model for the Virtual Router Redundancy Protocol (VRRP)Current
March 2018
- RFC 8339Definition of P2MP PW TLV for Label Switched Path (LSP) Ping MechanismsCurrent
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?