RFC 8348: A YANG Data Model for Hardware Management
In plain English — editorial summary, not part of the RFC
This document defines a YANG data model for the management of hardware on a single server.
Document record
- Document ID
- RFC8348
- Published
- March 2018
- Authors
- A. Bierman; M. Bjorklund; J. Dong; D. Romascanu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 60
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2037Entity MIB using SMIv2Obsoleted
October 1996
- RFC 8349A YANG Data Model for Routing Management (NMDA Version)Current
March 2018
- RFC 8350Alternate Tunnel Encapsulation for Data Frames in Control and Provisioning of Wireless Access Points (CAPWAP)Current
April 2018
- RFC 8344A YANG Data Model for IP ManagementCurrent
March 2018
- RFC 8343A YANG Data Model for Interface ManagementCurrent
March 2018
- RFC 8342Network Management Datastore Architecture (NMDA)Updated
March 2018
- RFC 8341Network Configuration Access Control ModelCurrent
March 2018
- RFC 8340YANG Tree DiagramsUpdated
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?