RFC 8022: A YANG Data Model for Routing Management
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8349.
Current version: RFC 8349 — A YANG Data Model for Routing Management (NMDA Version)
In plain English — editorial summary, not part of the RFC
This document contains a specification of three YANG modules and one submodule. Together they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols.
Document record
- Document ID
- RFC8022
- Published
- November 2016
- Authors
- L. Lhotka; A. Lindem
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 64
- Also known as
- —
- Obsoleted by:
- RFC 8349
Topics
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 9403A YANG Data Model for RIB ExtensionsCurrent
November 2023
- RFC 7895YANG Module LibraryObsoleted
June 2016
- RFC 8309Service Models ExplainedCurrent
January 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 8407Guidelines for Authors and Reviewers of Documents Containing YANG Data ModelsObsoleted
October 2018
- RFC 9182A YANG Network Data Model for Layer 3 VPNsCurrent
February 2022
- RFC 9196YANG Modules Describing Capabilities for Systems and Datastore Update NotificationsCurrent
February 2022
- RFC 9890An Update to YANG Module Names RegistrationCurrent
October 2025
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?