A YANG Data Model for Hardware Management
RFC 8348

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08

draft-ietf-netmod-entity-08.txt:
xym 0.4:
Extracting 'ietf-hardware@2018-01-15.yang'
   Removed 0 empty lines
Extracting 'iana-hardware@2018-01-15.yang'
   Removed 0 empty lines
Extracting 'ietf-hardware-state@2017-12-18.yang'
   Removed 0 empty lines


iana-hardware@2018-01-15.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors


ietf-hardware-state@2017-12-18.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors


ietf-hardware@2018-01-15.yang:
pyang 1.7.4: pyang --verbose --ietf -p {libs} {model}:
No validation errors

yanglint 0.14.73: yanglint --verbose -p {rfclib} -p {draftlib} -p {tmplib} {model} -i:
No validation errors

Internet Engineering Task Force (IETF)                        A. Bierman
Request for Comments: 8348                                     YumaWorks
Category: Standards Track                                   M. Bjorklund
ISSN: 2070-1721                                           Tail-f Systems
                                                                 J. Dong
                                                     Huawei Technologies
                                                            D. Romascanu
                                                              March 2018

               A YANG Data Model for Hardware Management

Abstract

   This document defines a YANG data model for the management of
   hardware on a single server.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8348.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bierman, et al.              Standards Track                    [Page 1]
RFC 8348                YANG Hardware Management              March 2018

Table of Contents

   1. Introduction ....................................................3
      1.1. Terminology ................................................3
      1.2. Tree Diagrams ..............................................3
   2. Objectives ......................................................4
   3. Hardware Data Model .............................................4
      3.1. The Components Lists .......................................5
   4. Relationship to ENTITY-MIB ......................................6
   5. Relationship to ENTITY-SENSOR-MIB ...............................8
   6. Relationship to ENTITY-STATE-MIB ................................8
   7. Hardware YANG Modules ...........................................9
      7.1. "ietf-hardware" Module .....................................9
      7.2. "iana-hardware" Module ....................................34
   8. IANA Considerations ............................................38
      8.1. URI Registrations .........................................38
      8.2. YANG Module Registrations .................................39
   9. Security Considerations ........................................39
   10. References ....................................................40
      10.1. Normative References .....................................40
      10.2. Informative References ...................................41
   Appendix A.  Hardware State Data Model ............................42
     A.1.  Hardware State YANG Module ................................43
   Acknowledgments ...................................................60
   Authors' Addresses ................................................60

Bierman, et al.              Standards Track                    [Page 2]
RFC 8348                YANG Hardware Management              March 2018

1.  Introduction

   This document defines a YANG data model [RFC7950] for the management
   of hardware on a single server.

   The data model includes configuration and system state (status
   information and counters for the collection of statistics).

   The data model in this document is designed to be compliant with the
   Network Management Datastore Architecture (NMDA) [RFC8342].  For
   implementations that do not yet support NMDA, a temporary module with
   system state data only is defined in Appendix A.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

   The following terms are defined in [RFC8342] and are not redefined
   here:

   o  client