draft-ietf-netmod-entity-03.txt   draft-ietf-netmod-entity-04.txt 
Network Working Group A. Bierman Network Working Group A. Bierman
Internet-Draft YumaWorks Internet-Draft YumaWorks
Intended status: Standards Track M. Bjorklund Intended status: Standards Track M. Bjorklund
Expires: September 14, 2017 Tail-f Systems Expires: February 22, 2018 Tail-f Systems
J. Dong J. Dong
Huawei Technologies Huawei Technologies
D. Romascanu D. Romascanu
March 13, 2017 August 21, 2017
A YANG Data Model for Hardware Management A YANG Data Model for Hardware Management
draft-ietf-netmod-entity-03 draft-ietf-netmod-entity-04
Abstract Abstract
This document defines a YANG data model for the management of This document defines a YANG data model for the management of
hardware on a single server. hardware on a single server.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017. This Internet-Draft will expire on February 22, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 2 1.1.1. Tree Diagrams . . . . . . . . . . . . . . . . . . . . 3
2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Hardware Data Model . . . . . . . . . . . . . . . . . . . . . 3 3. Hardware Data Model . . . . . . . . . . . . . . . . . . . . . 4
3.1. The Components Lists . . . . . . . . . . . . . . . . . . 5 3.1. The Components Lists . . . . . . . . . . . . . . . . . . 5
4. Relationship to ENTITY-MIB . . . . . . . . . . . . . . . . . 5 4. Relationship to ENTITY-MIB . . . . . . . . . . . . . . . . . 5
5. Relationship to ENTITY-SENSOR-MIB . . . . . . . . . . . . . . 6 5. Relationship to ENTITY-SENSOR-MIB . . . . . . . . . . . . . . 6
6. Relationship to ENTITY-STATE-MIB . . . . . . . . . . . . . . 7 6. Relationship to ENTITY-STATE-MIB . . . . . . . . . . . . . . 7
7. Hardware YANG Module . . . . . . . . . . . . . . . . . . . . 7 7. Hardware YANG Module . . . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
9. Security Considerations . . . . . . . . . . . . . . . . . . . 38 9. Security Considerations . . . . . . . . . . . . . . . . . . . 35
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36
11. Normative References . . . . . . . . . . . . . . . . . . . . 39 11. Normative References . . . . . . . . . . . . . . . . . . . . 36
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for the management This document defines a YANG [RFC7950] data model for the management
of hardware on a single server. of hardware on a single server.
The data model includes configuration data and state data (status The data model includes configuration and system state (status
information and counters for the collection of statistics). information and counters for the collection of statistics).
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 14, [RFC2119].
The following terms are defined in
[I-D.ietf-netmod-revised-datastores] and are not redefined here:
o client
o server
o configuration
o system state
o operational state datastore
o intended configuration datastore
1.1.1. Tree Diagrams 1.1.1. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is as
follows: follows:
o Brackets "[" and "]" enclose list keys. o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration o Abbreviations before data node names: "rw" means configuration
data (read-write) and "ro" state data (read-only). data (read-write) and "ro" state data (read-only).
skipping to change at page 3, line 43 skipping to change at page 4, line 11
o The data model should support pre-provisioning of hardware o The data model should support pre-provisioning of hardware
components. components.
3. Hardware Data Model 3. Hardware Data Model
This document defines the YANG module "ietf-hardware", which has the This document defines the YANG module "ietf-hardware", which has the
following structure: following structure:
module: ietf-hardware module: ietf-hardware
+--ro hardware-state +--rw hardware
| +--ro last-change? yang:date-and-time +--ro last-change? yang:date-and-time
| +--ro component* [name]
| +--ro name string
| +--ro class identityref
| +--ro physical-index? int32 {entity-mib}?
| +--ro description? string
| +--ro parent? -> ../../component/name
| +--ro parent-rel-pos? int32
| +--ro contains-child* -> ../../component/name
| +--ro hardware-rev? string
| +--ro firmware-rev? string
| +--ro software-rev? string
| +--ro serial-num? string
| +--ro mfg-name? string
| +--ro model-name? string
| +--ro alias? string
| +--ro asset-id? string
| +--ro is-fru? boolean
| +--ro mfg-date? yang:date-and-time
| +--ro uri* inet:uri
| +--ro uuid? yang:uuid
| +--ro state {hardware-state}?
| | +--ro state-last-changed? yang:date-and-time
| | +--ro admin-state? admin-state
| | +--ro oper-state? oper-state
| | +--ro usage-state? usage-state
| | +--ro alarm-state? alarm-state
| | +--ro standby-state? standby-state
| +--ro sensor-data {hardware-sensor}?
| +--ro value? sensor-value
| +--ro value-type? sensor-value-type
| +--ro value-scale? sensor-value-scale
| +--ro value-precision? sensor-value-precision
| +--ro oper-status? sensor-status
| +--ro units-display? string
| +--ro value-timestamp? yang:date-and-time
| +--ro value-update-rate? uint32
+--rw hardware {hardware-config}?
+--rw component* [name] +--rw component* [name]
+--rw name string +--rw name string
+--rw class identityref +--rw class identityref
+--rw parent? -> /hardware-state/component/name +--ro physical-index? int32 {entity-mib}?
+--ro description? string
+--rw parent? -> ../../component/name
+--rw parent-rel-pos? int32 +--rw parent-rel-pos? int32
+--ro contains-child* -> ../../component/name
+--ro hardware-rev? string
+--ro firmware-rev? string
+--ro software-rev? string
+--ro serial-num? string
+--rw mfg-name? string +--rw mfg-name? string
+--rw serial-num? string +--ro model-name? string
+--rw alias? string +--rw alias? string
+--rw asset-id? string +--rw asset-id? string
+--ro is-fru? boolean
+--ro mfg-date? yang:date-and-time
+--rw uri* inet:uri +--rw uri* inet:uri
+--rw admin-state? admin-state {hardware-state}? +--ro uuid? yang:uuid
+--rw state {hardware-state}?
| +--ro state-last-changed? yang:date-and-time
| +--rw admin-state? admin-state
| +--ro oper-state? oper-state
| +--ro usage-state? usage-state
| +--ro alarm-state? alarm-state
| +--ro standby-state? standby-state
+--ro sensor-data {hardware-sensor}?
+--ro value? sensor-value
+--ro value-type? sensor-value-type
+--ro value-scale? sensor-value-scale
+--ro value-precision? sensor-value-precision
+--ro oper-status? sensor-status
+--ro units-display? string
+--ro value-timestamp? yang:date-and-time
+--ro value-update-rate? uint32
notifications: notifications:
+---n hardware-state-change +---n hardware-state-change
+---n hardware-state-oper-enabled {hardware-state}? +---n hardware-state-oper-enabled {hardware-state}?
| +--ro name? -> /hardware-state/component/name | +--ro name? -> /hardware/component/name
| +--ro admin-state? | +--ro admin-state? -> /hardware/component/state/admin-state
| | -> /hardware-state/component/state/admin-state | +--ro alarm-state? -> /hardware/component/state/alarm-state
| +--ro alarm-state?
| -> /hardware-state/component/state/alarm-state
+---n hardware-state-oper-disabled {hardware-state}? +---n hardware-state-oper-disabled {hardware-state}?
+--ro name? -> /hardware-state/component/name +--ro name? -> /hardware/component/name
+--ro admin-state? +--ro admin-state? -> /hardware/component/state/admin-state
| -> /hardware-state/component/state/admin-state +--ro alarm-state? -> /hardware/component/state/alarm-state
+--ro alarm-state?
-> /hardware-state/component/state/alarm-state
3.1. The Components Lists 3.1. The Components Lists
The data model for hardware presented in this document uses a flat The data model for hardware presented in this document uses a flat
list of components. Each component in the list is identified by its list of components. Each component in the list is identified by its
name. Furthermore, each component has a mandatory "class" leaf. name. Furthermore, each component has a mandatory "class" leaf.
The "iana-hardware" module defines YANG identities for the hardware The "iana-hardware" module defines YANG identities for the hardware
types in the IANA-maintained "IANA-ENTITY-MIB" registry. types in the IANA-maintained "IANA-ENTITY-MIB" registry.
The "class" leaf is a YANG identity that describes the type of the The "class" leaf is a YANG identity that describes the type of the
hardware. Vendors are encouraged to either directly use one of the hardware. Vendors are encouraged to either directly use one of the
common IANA-defined identities, or derive a more specific identity common IANA-defined identities, or derive a more specific identity
from one of them. from one of them.
There is one optional list of configured components ("/hardware/
component"), and a separate list for the operational state of all
components ("/hardware-state/component").
4. Relationship to ENTITY-MIB 4. Relationship to ENTITY-MIB
If the device implements the ENTITY-MIB [RFC6933], each entry in the If the device implements the ENTITY-MIB [RFC6933], each entry in the
"/hardware-state/component" list is mapped to one EntPhysicalEntry. "/hardware-state/component" list is mapped to one EntPhysicalEntry.
Objects that are writable in the MIB are mapped to nodes in the Objects that are writable in the MIB are mapped to nodes in the
"/hardware/component" list. "/hardware/component" list.
The "physical-index" leaf MUST contain the value of the corresponding The "physical-index" leaf MUST contain the value of the corresponding
entPhysicalEntry's entPhysicalIndex. entPhysicalEntry's entPhysicalIndex.
skipping to change at page 6, line 8 skipping to change at page 6, line 5
corresponding IANAPhysicalClass enumeration value. Otherwise, corresponding IANAPhysicalClass enumeration value. Otherwise,
entPhysicalClass contains the IANAPhysicalClass value "other(1)". entPhysicalClass contains the IANAPhysicalClass value "other(1)".
Vendors are encouraged to define an identity (derived from an Vendors are encouraged to define an identity (derived from an
identity in "iana-hardware" if possible) for each enterprise-specific identity in "iana-hardware" if possible) for each enterprise-specific
registration identifier used for entPhysicalVendorType, and use that registration identifier used for entPhysicalVendorType, and use that
identity for the "class" leaf. identity for the "class" leaf.
The following tables list the YANG data nodes with corresponding The following tables list the YANG data nodes with corresponding
objects in the ENTITY-MIB. objects in the ENTITY-MIB.
+----------------------------------+--------------------------------+ +--------------------------------+----------------------------------+
| YANG data node in /hardware- | ENTITY-MIB object | | YANG data node in | ENTITY-MIB object |
| state/component | | | /hardware/component | |
+----------------------------------+--------------------------------+ +--------------------------------+----------------------------------+
| name | entPhysicalName | | name | entPhysicalName |
| class | entPhysicalClass | | class | entPhysicalClass |
| | entPhysicalVendorType | | | entPhysicalVendorType |
| physical-index | entPhysicalIndex | | physical-index | entPhysicalIndex |
| description | entPhysicalDescr | | description | entPhysicalDescr |
| parent | entPhysicalContainedIn | | parent | entPhysicalContainedIn |
| parent-rel-pos | entPhysicalParentRelPos | | parent-rel-pos | entPhysicalParentRelPos |
| contains-child | entPhysicalChildIndex | | contains-child | entPhysicalChildIndex |
| hardware-rev | entPhysicalHardwareRev | | hardware-rev | entPhysicalHardwareRev |
| firmware-rev | entPhysicalFirmwareRev | | firmware-rev | entPhysicalFirmwareRev |
| software-rev | entPhysicalSoftwareRev | | software-rev | entPhysicalSoftwareRev |
| serial-num | entPhysicalSerialNum | | serial-num | entPhysicalSerialNum |
| mfg-name | entPhysicalMfgName | | mfg-name | entPhysicalMfgName |
| model-name | entPhysicalModelName | | model-name | entPhysicalModelName |
| alias | entPhysicalAlias | | alias | entPhysicalAlias |
| asset-id | entPhysicalAssetID | | asset-id | entPhysicalAssetID |
| is-fru | entPhysicalIsFRU | | is-fru | entPhysicalIsFRU |
| mfg-date | entPhysicalMfgDate | | mfg-date | entPhysicalMfgDate |
| uri | entPhysicalUris | | uri | entPhysicalUris |
| uuid | entPhysicalUUID | | uuid | entPhysicalUUID |
+----------------------------------+--------------------------------+ +--------------------------------+----------------------------------+
YANG data nodes and related ENTITY-MIB objects YANG Data Nodes and Related ENTITY-MIB Objects
5. Relationship to ENTITY-SENSOR-MIB 5. Relationship to ENTITY-SENSOR-MIB
If the device implements the ENTITY-SENSOR-MIB [RFC3433], each entry If the device implements the ENTITY-SENSOR-MIB [RFC3433], each entry
the in "/hardware-state/component" list where the container in the "/hardware/component" list where the container "sensor-data"
"sensor-data" exists is mapped to one EntPhySensorEntry. exists is mapped to one EntPhySensorEntry.
+-------------------------------------+-----------------------------+ +-------------------------------------+-----------------------------+
| YANG data node in /hardware- | ENTITY-SENSOR-MIB object | | YANG data node in | ENTITY-SENSOR-MIB object |
| state/component/sensor-data | | | /hardware/component/sensor-data | |
+-------------------------------------+-----------------------------+ +-------------------------------------+-----------------------------+
| value | entPhySensorValue | | value | entPhySensorValue |
| value-type | entPhySensorType | | value-type | entPhySensorType |
| value-scale | entPhySensorScale | | value-scale | entPhySensorScale |
| value-precision | entPhySensorPrecision | | value-precision | entPhySensorPrecision |
| oper-status | entPhySensorOperStatus | | oper-status | entPhySensorOperStatus |
| units-display | entPhySensorUnitsDisplay | | units-display | entPhySensorUnitsDisplay |
| value-timestamp | entPhySensorValueTimeStamp | | value-timestamp | entPhySensorValueTimeStamp |
| value-update-rate | entPhySensorValueUpdateRate | | value-update-rate | entPhySensorValueUpdateRate |
+-------------------------------------+-----------------------------+ +-------------------------------------+-----------------------------+
YANG data nodes and related ENTITY-SENSOR-MIB objects YANG Data Nodes and Related ENTITY-SENSOR-MIB Objects
6. Relationship to ENTITY-STATE-MIB 6. Relationship to ENTITY-STATE-MIB
If the device implements the ENTITY-STATE-MIB [RFC4268], each entry If the device implements the ENTITY-STATE-MIB [RFC4268], each entry
the in "/hardware-state/component" list where the container "state" in the "/hardware/component" list where the container "state" exists
exists is mapped to one EntStateEntry. is mapped to one EntStateEntry.
+--------------------------------------------+----------------------+ +------------------------------------------+------------------------+
| YANG data node in /hardware- | ENTITY-STATE-MIB | | YANG data node in | ENTITY-STATE-MIB |
| state/component/state | object | | /hardware/component/state | object |
+--------------------------------------------+----------------------+ +------------------------------------------+------------------------+
| state-last-changed | entStateLastChanged | | state-last-changed | entStateLastChanged |
| admin-state | entStateAdmin | | admin-state | entStateAdmin |
| oper-state | entStateOper | | oper-state | entStateOper |
| usage-state | entStateUsage | | usage-state | entStateUsage |
| alarm-state | entStateAlarm | | alarm-state | entStateAlarm |
| standby-state | entStateStandby | | standby-state | entStateStandby |
+--------------------------------------------+----------------------+ +------------------------------------------+------------------------+
YANG data nodes and related ENTITY-SENSOR-MIB objects YANG Data Nodes and Related ENTITY-SENSOR-MIB Objects
7. Hardware YANG Module 7. Hardware YANG Module
<CODE BEGINS> file "ietf-hardware@2017-03-07.yang" <CODE BEGINS> file "ietf-hardware@2017-08-21.yang"
module ietf-hardware { module ietf-hardware {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-hardware"; namespace "urn:ietf:params:xml:ns:yang:ietf-hardware";
prefix hw; prefix hw;
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-yang-types { import ietf-yang-types {
skipping to change at page 8, line 18 skipping to change at page 8, line 18
prefix ianahw; prefix ianahw;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (NETCONF Data Modeling Language) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
WG Chair: Lou Berger
<mailto:lberger@labn.net>
WG Chair: Kent Watsen
<mailto:kwatsen@juniper.net>
Editor: Andy Bierman Editor: Andy Bierman
<mailto:andy@yumaworks.com> <mailto:andy@yumaworks.com>
Editor: Martin Bjorklund Editor: Martin Bjorklund
<mailto:mbj@tail-f.com> <mailto:mbj@tail-f.com>
Editor: Jie Dong Editor: Jie Dong
<mailto:jie.dong@huawei.com> <mailto:jie.dong@huawei.com>
Editor: Dan Romascanu Editor: Dan Romascanu
<mailto:dromasca@gmail.com>"; <mailto:dromasca@gmail.com>";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX and YYYY with actual RFC numbers and
// note. // remove this note.
description description
"This module contains a collection of YANG definitions for "This module contains a collection of YANG definitions for
managing hardware. managing hardware.
This data model is designed for the Network Management Datastore
Architecture defined in RFC YYYY.
Copyright (c) 2017 IETF Trust and the persons identified as Copyright (c) 2017 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision 2017-03-07 { revision 2017-08-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Hardware Management"; "RFC XXXX: A YANG Data Model for Hardware Management";
} }
/* /*
* Features * Features
*/ */
feature entity-mib { feature entity-mib {
description description
"This feature indicates that the device implements "This feature indicates that the device implements
the ENTITY-MIB."; the ENTITY-MIB.";
reference "RFC 6933: Entity MIB (Version 4)"; reference "RFC 6933: Entity MIB (Version 4)";
} }
feature hardware-config {
description
"Indicates that the server supports configuration of
hardware components.";
}
feature hardware-state { feature hardware-state {
description description
"Indicates the ENTITY-STATE-MIB objects are supported"; "Indicates the ENTITY-STATE-MIB objects are supported";
reference "RFC 4268: Entity State MIB"; reference "RFC 4268: Entity State MIB";
} }
feature hardware-sensor { feature hardware-sensor {
description description
"Indicates the ENTITY-SENSOR-MIB objects are supported"; "Indicates the ENTITY-SENSOR-MIB objects are supported";
reference "RFC 3433: Entity Sensor MIB"; reference "RFC 3433: Entity Sensor MIB";
skipping to change at page 10, line 36 skipping to change at page 10, line 27
description description
"Represents the various possible administrative states."; "Represents the various possible administrative states.";
reference "RFC 4268: EntityAdminState"; reference "RFC 4268: EntityAdminState";
} }
typedef oper-state { typedef oper-state {
type enumeration { type enumeration {
enum unknown { enum unknown {
value 1; value 1;
description description
"The resource is unable to report operational state."; "The resource is unable to report its operational state.";
} }
enum disabled { enum disabled {
value 2; value 2;
description description
"The resource is totally inoperable."; "The resource is totally inoperable.";
} }
enum enabled { enum enabled {
value 3; value 3;
description description
"The resource is partially or fully operable."; "The resource is partially or fully operable.";
skipping to change at page 19, line 33 skipping to change at page 19, line 25
fluctuating readings."; fluctuating readings.";
} }
} }
description description
"A node using this data type represents the operational status "A node using this data type represents the operational status
of a physical sensor."; of a physical sensor.";
reference "RFC 3433: EntitySensorStatus"; reference "RFC 3433: EntitySensorStatus";
} }
/* /*
* Operational state data nodes * Data nodes
*/ */
container hardware-state { container hardware {
config false;
description description
"Data nodes for the operational state of components."; "Data nodes representing components.
If the server supports configuration of hardware components,
then this data model is instantiated in the configuration
datastores supported by the server. The leaf-list 'datastore'
for the module 'ietf-hardware' in the YANG library provides
this information.";
leaf last-change { leaf last-change {
type yang:date-and-time; type yang:date-and-time;
config false;
description description
"The time the '/hardware-state/component' list changed."; "The time the '/hardware/component' list changed in the
operational state datastore.";
} }
list component { list component {
key name; key name;
description description
"List of components. "List of components.
When the server detects a new hardware component, it When the server detects a new hardware component, it
initializes an entry in this list. initializes a list entry in the operational state datastore.
If the server does not support the feature If the server does not support configuration of hardware
'hardware-config', the entry is initialized with values for components, list entries in the operational state datastore
all nodes as detected by the implementation. are initialized with values for all nodes as detected by the
implementation.
Otherwise, the following procedure is followed: Otherwise, the following procedure is followed:
1. If there is an entry in the /hardware/component list 1. If there is an entry in the /hardware/component list in
with values for the nodes 'class', 'parent', the intended configuration datastore with values for
'parent-rel-pos' that are equal to the detected values, the nodes 'class', 'parent', 'parent-rel-pos' that are
then: equal to the detected values, then:
1a. If the configured entry has a value for 'mfg-name' 1a. If the configured entry has a value for 'mfg-name'
that is equal to the detected value, or if the that is equal to the detected value, or if the
'mfg-name' value cannot be detected, then the entry is 'mfg-name' value cannot be detected, then the list
entry in the operational state datastore is
initialized with the configured values for all initialized with the configured values for all
configured leafs, including the 'name'. configured nodes, including the 'name'.
Otherwise, the entry is initialized with values for Otherwise, the list entry in the operational state
all nodes as detected by the implementation. The datastore is initialized with values for all nodes as
implementation may raise an alarm that informs about detected by the implementation. The implementation
the 'mfg-name' mismatch condition. How this is done may raise an alarm that informs about the 'mfg-name'
is outside the scope of this document. mismatch condition. How this is done is outside the
scope of this document.
1b. Otherwise (i.e., there is no matching configuration 1b. Otherwise (i.e., there is no matching configuration
entry), the entry is initialized with values for all entry), the list entry in the operational state
nodes as detected by the implementation. datastore is initialized with values for all nodes as
detected by the implementation.
If the /hardware/component list is modified (i.e., someone
changed the configuration), then the system MUST behave as
if it re-initializes itself, and follow the procedure in
(1).";
If the /hardware/component list in the intended
configuration datastore is modified, then the system MUST
behave as if it re-initializes itself, and follow the
procedure in (1).";
reference "RFC 6933: entPhysicalEntry"; reference "RFC 6933: entPhysicalEntry";
leaf name { leaf name {
type string; type string;
description description
"The name assigned to this component. "The name assigned to this component.
This name is not required to be the same as This name is not required to be the same as
entPhysicalName."; entPhysicalName.";
} }
skipping to change at page 21, line 18 skipping to change at page 21, line 20
"An indication of the general hardware type of the "An indication of the general hardware type of the
component."; component.";
reference "RFC 6933: entPhysicalClass"; reference "RFC 6933: entPhysicalClass";
} }
leaf physical-index { leaf physical-index {
if-feature entity-mib; if-feature entity-mib;
type int32 { type int32 {
range "1..2147483647"; range "1..2147483647";
} }
config false;
description description
"The entPhysicalIndex for the entPhysicalEntry represented "The entPhysicalIndex for the entPhysicalEntry represented
by this list entry."; by this list entry.";
reference "RFC 6933: entPhysicalIndex"; reference "RFC 6933: entPhysicalIndex";
} }
leaf description { leaf description {
type string; type string;
config false;
description description
"A textual description of component. This node should "A textual description of component. This node should
contain a string that identifies the manufacturer's name contain a string that identifies the manufacturer's name
for the component and should be set to a distinct value for the component and should be set to a distinct value
for each version or model of the component."; for each version or model of the component.";
reference "RFC 6933: entPhysicalDescr"; reference "RFC 6933: entPhysicalDescr";
} }
leaf parent { leaf parent {
type leafref { type leafref {
path "../../component/name"; path "../../component/name";
require-instance false;
} }
description description
"The name of the component that physically contains this "The name of the component that physically contains this
component. component.
If this leaf is not instantiated, it indicates that this If this leaf is not instantiated, it indicates that this
component is not contained in any other component. component is not contained in any other component.
In the event that a physical component is contained by In the event that a physical component is contained by
more than one physical component (e.g., double-wide more than one physical component (e.g., double-wide
skipping to change at page 22, line 21 skipping to change at page 22, line 27
components are defined as components that share the same components are defined as components that share the same
instance values of each of the 'parent' and 'class' instance values of each of the 'parent' and 'class'
nodes."; nodes.";
reference "RFC 6933: entPhysicalParentRelPos"; reference "RFC 6933: entPhysicalParentRelPos";
} }
leaf-list contains-child { leaf-list contains-child {
type leafref { type leafref {
path "../../component/name"; path "../../component/name";
} }
config false;
description description
"The name of the contained component."; "The name of the contained component.";
reference "RFC 6933: entPhysicalChildIndex"; reference "RFC 6933: entPhysicalChildIndex";
} }
leaf hardware-rev { leaf hardware-rev {
type string; type string;
config false;
description description
"The vendor-specific hardware revision string for the "The vendor-specific hardware revision string for the
component. The preferred value is the hardware revision component. The preferred value is the hardware revision
identifier actually printed on the component itself (if identifier actually printed on the component itself (if
present)."; present).";
reference "RFC 6933: entPhysicalHardwareRev"; reference "RFC 6933: entPhysicalHardwareRev";
} }
leaf firmware-rev { leaf firmware-rev {
type string; type string;
config false;
description description
"The vendor-specific firmware revision string for the "The vendor-specific firmware revision string for the
component."; component.";
reference "RFC 6933: entPhysicalFirmwareRev"; reference "RFC 6933: entPhysicalFirmwareRev";
} }
leaf software-rev { leaf software-rev {
type string; type string;
config false;
description description
"The vendor-specific software revision string for the "The vendor-specific software revision string for the
component."; component.";
reference "RFC 6933: entPhysicalSoftwareRev"; reference "RFC 6933: entPhysicalSoftwareRev";
} }
leaf serial-num { leaf serial-num {
type string; type string;
config false;
description description
"The vendor-specific serial number string for the "The vendor-specific serial number string for the
component. The preferred value is the serial number component. The preferred value is the serial number
string actually printed on the component itself (if string actually printed on the component itself (if
present). present).";
If a serial number has been configured for this component
in /hardware/component/serial-num, this node contains the
configured value.";
reference "RFC 6933: entPhysicalSerialNum"; reference "RFC 6933: entPhysicalSerialNum";
} }
leaf mfg-name { leaf mfg-name {
type string; type string;
description description
"The name of the manufacturer of this physical component. "The name of the manufacturer of this physical component.
The preferred value is the manufacturer name string The preferred value is the manufacturer name string
actually printed on the component itself (if present). actually printed on the component itself (if present).
skipping to change at page 23, line 38 skipping to change at page 23, line 44
mfg-name. mfg-name.
If the manufacturer name string associated with the If the manufacturer name string associated with the
physical component is unknown to the server, then this physical component is unknown to the server, then this
node is not instantiated."; node is not instantiated.";
reference "RFC 6933: entPhysicalMfgName"; reference "RFC 6933: entPhysicalMfgName";
} }
leaf model-name { leaf model-name {
type string; type string;
config false;
description description
"The vendor-specific model name identifier string "The vendor-specific model name identifier string
associated with this physical component. The preferred associated with this physical component. The preferred
value is the customer-visible part number, which may be value is the customer-visible part number, which may be
printed on the component itself. printed on the component itself.
If the model name string associated with the physical If the model name string associated with the physical
component is unknown to the server, then this node is not component is unknown to the server, then this node is not
instantiated."; instantiated.";
reference "RFC 6933: entPhysicalModelName"; reference "RFC 6933: entPhysicalModelName";
} }
leaf alias { leaf alias {
type string; type string;
description description
"An 'alias' name for the component, as specified by a "An 'alias' name for the component, as specified by a
network manager, and provides a non-volatile 'handle' for network manager, and provides a non-volatile 'handle' for
the component. the component.
If an alias has been configured for this component in If no configured value exists, the server MAY set the
/hardware/component/alias, this node contains the value of this node to a locally unique value in the
configured value. If no such alias has been configured, operational state datastore.
the server may set the value of this node to a locally
unique value."; A server implementation MAY map this leaf to the
entPhysicalAlias MIB object. Such an implementation needs
to use some mechanism to handle the differences in size
and characters allowed between this leaf and
entPhysicalAlias. The definition of such a mechanism is
outside the scope of this document.";
reference "RFC 6933: entPhysicalAlias"; reference "RFC 6933: entPhysicalAlias";
} }
leaf asset-id { leaf asset-id {
type string; type string;
description description
"This node is a user-assigned asset tracking identifier for "This node is a user-assigned asset tracking identifier for
the component. the component.
If an asset tracking identifier has been configured for A server implementation MAY map this leaf to the
this component in /hardware/component/asset-id, this node entPhysicalAssetID MIB object. Such an implementation
contains the configured value."; needs to use some mechanism to handle the differences in
size and characters allowed between this leaf and
entPhysicalAssetID. The definition of such a mechanism is
outside the scope of this document.";
reference "RFC 6933: entPhysicalAssetID"; reference "RFC 6933: entPhysicalAssetID";
} }
leaf is-fru { leaf is-fru {
type boolean; type boolean;
config false;
description description
"This node indicates whether or not this component is "This node indicates whether or not this component is
considered a 'field replaceable unit' by the vendor. If considered a 'field replaceable unit' by the vendor. If
this node contains the value 'true', then this component this node contains the value 'true', then this component
identifies a field replaceable unit. For all components identifies a field replaceable unit. For all components
that are permanently contained within a field replaceable that are permanently contained within a field replaceable
unit, the value 'false' should be returned for this unit, the value 'false' should be returned for this
node."; node.";
reference "RFC 6933: entPhysicalIsFRU"; reference "RFC 6933: entPhysicalIsFRU";
} }
leaf mfg-date { leaf mfg-date {
type yang:date-and-time; type yang:date-and-time;
config false;
description description
"The date of manufacturing of the managed component."; "The date of manufacturing of the managed component.";
reference "RFC 6933: entPhysicalMfgDate"; reference "RFC 6933: entPhysicalMfgDate";
} }
leaf-list uri { leaf-list uri {
type inet:uri; type inet:uri;
description description
"This node contains identification information about the "This node contains identification information about the
component. component.";
If uris have been configured for this component in
/hardware/component/uri, this node contains the configured
values.";
reference "RFC 6933: entPhysicalUris"; reference "RFC 6933: entPhysicalUris";
} }
leaf uuid { leaf uuid {
type yang:uuid; type yang:uuid;
config false;
description description
"A Universally Unique Identifier of the component."; "A Universally Unique Identifier of the component.";
reference "RFC 6933: entPhysicalUUID"; reference "RFC 6933: entPhysicalUUID";
} }
container state { container state {
if-feature hardware-state; if-feature hardware-state;
description description
"State-related nodes"; "State-related nodes";
reference "RFC 4268: Entity State MIB"; reference "RFC 4268: Entity State MIB";
leaf state-last-changed { leaf state-last-changed {
type yang:date-and-time; type yang:date-and-time;
config false;
description description
"The date and time when the value of any of the "The date and time when the value of any of the
admin-state, oper-state, usage-state, alarm-state, or admin-state, oper-state, usage-state, alarm-state, or
standby-state changed for this component. standby-state changed for this component.
If there has been no change since the last If there has been no change since the last
re-initialization of the local system, this node re-initialization of the local system, this node
contains the date and time of local system contains the date and time of local system
initialization. If there has been no change since the initialization. If there has been no change since the
component was added to the local system, this node component was added to the local system, this node
skipping to change at page 26, line 16 skipping to change at page 26, line 31
administrative state values. Some components cannot be administrative state values. Some components cannot be
locked, and hence this node exhibits only the 'unlocked' locked, and hence this node exhibits only the 'unlocked'
state. Other components cannot be shutdown gracefully, state. Other components cannot be shutdown gracefully,
and hence this node does not exhibit the 'shutting-down' and hence this node does not exhibit the 'shutting-down'
state."; state.";
reference "RFC 4268: entStateAdmin"; reference "RFC 4268: entStateAdmin";
} }
leaf oper-state { leaf oper-state {
type oper-state; type oper-state;
config false;
description description
"The operational state for this component. "The operational state for this component.
Note that this node does not follow the administrative Note that this node does not follow the administrative
state. An administrative state of down does not predict state. An administrative state of down does not predict
an operational state of disabled. an operational state of disabled.
Note that some implementations may not be able to Note that some implementations may not be able to
accurately report oper-state while the admin-state node accurately report oper-state while the admin-state node
has a value other than 'unlocked'. In these cases, this has a value other than 'unlocked'. In these cases, this
node MUST have a value of 'unknown'."; node MUST have a value of 'unknown'.";
reference "RFC 4268: entStateOper"; reference "RFC 4268: entStateOper";
} }
leaf usage-state { leaf usage-state {
type usage-state; type usage-state;
config false;
description description
"The usage state for this component. "The usage state for this component.
This node refers to a component's ability to service This node refers to a component's ability to service
more components in a containment hierarchy. more components in a containment hierarchy.
Some components will exhibit only a subset of the usage Some components will exhibit only a subset of the usage
state values. Components that are unable to ever state values. Components that are unable to ever
service any components within a containment hierarchy service any components within a containment hierarchy
will always have a usage state of 'busy'. Some will always have a usage state of 'busy'. Some
components will only ever be able to support one components will only ever be able to support one
component within its containment hierarchy and will component within its containment hierarchy and will
therefore only exhibit values of 'idle' and 'busy'."; therefore only exhibit values of 'idle' and 'busy'.";
reference "RFC 4268, entStateUsage"; reference "RFC 4268, entStateUsage";
} }
leaf alarm-state { leaf alarm-state {
type alarm-state; type alarm-state;
config false;
description description
"The alarm state for this component. It does not "The alarm state for this component. It does not
include the alarms raised on child components within its include the alarms raised on child components within its
containment hierarchy."; containment hierarchy.";
reference "RFC 4268: entStateAlarm"; reference "RFC 4268: entStateAlarm";
} }
leaf standby-state { leaf standby-state {
type standby-state; type standby-state;
config false;
description description
"The standby state for this component. "The standby state for this component.
Some components will exhibit only a subset of the Some components will exhibit only a subset of the
remaining standby state values. If this component remaining standby state values. If this component
cannot operate in a standby role, the value of this node cannot operate in a standby role, the value of this node
will always be 'providing-service'."; will always be 'providing-service'.";
reference "RFC 4268: entStateStandby"; reference "RFC 4268: entStateStandby";
} }
} }
container sensor-data { container sensor-data {
when 'derived-from-or-self(../class, when 'derived-from-or-self(../class,
"ianahw:sensor")' { "ianahw:sensor")' {
description description
"Sensor data nodes present for any component of type "Sensor data nodes present for any component of type
'sensor'"; 'sensor'";
} }
if-feature hardware-sensor; if-feature hardware-sensor;
config false;
description description
"Sensor-related nodes."; "Sensor-related nodes.";
reference "RFC 3433: Entity Sensor MIB"; reference "RFC 3433: Entity Sensor MIB";
leaf value { leaf value {
type sensor-value; type sensor-value;
description description
"The most recent measurement obtained by the server "The most recent measurement obtained by the server
for this sensor. for this sensor.
skipping to change at page 29, line 17 skipping to change at page 29, line 39
- the sensor value is updated when the sensor - the sensor value is updated when the sensor
value changes (event-driven), value changes (event-driven),
- the server does not know the update rate."; - the server does not know the update rate.";
reference "RFC 3433: entPhySensorValueUpdateRate"; reference "RFC 3433: entPhySensorValueUpdateRate";
} }
} }
} }
} }
/* /*
* Configuration data nodes
*/
container hardware {
if-feature hardware-config;
description
"Configuration parameters for components.";
list component {
key name;
description
"List of configuration data for components.
See the description of /hardware-state/component for
information on how this list is used by a server.";
leaf name {
type string;
description
"Administrative name for this component. No restrictions
apply.";
}
leaf class {
type identityref {
base ianahw:hardware-class;
}
mandatory true;
description
"An indication of the general hardware type of the
component.";
reference "RFC 6933: entPhysicalClass";
}
leaf parent {
type leafref {
path "/hardware-state/component/name";
require-instance false;
}
description
"The name of the component that contains this component.";
reference "RFC 6933: entPhysicalContainedIn";
}
leaf parent-rel-pos {
type int32 {
range "0 .. 2147483647";
}
description
"An indication of the relative position of this child
component among all its sibling components. Sibling
components are defined as components that share the same
instance values of each of the 'parent' and 'class'
nodes.";
reference "RFC 6933: entPhysicalParentRelPos";
}
leaf mfg-name {
type string;
description
"The name of the manufacturer of this physical component.";
reference "RFC 6933: entPhysicalMfgName";
}
leaf serial-num {
type string;
description
"The vendor-specific serial number string for the
component. The preferred value is the serial number
string actually printed on the component itself (if
present).
This node is indented to be used for components for which
the server cannot determine the serial number.";
reference "RFC 6933: entPhysicalSerialNum";
}
leaf alias {
type string;
description
"This node is an 'alias' name for the component, as
specified by a network manager, and provides a non-
volatile 'handle' for the component.
A server implementation MAY map this leaf to the
entPhysicalAlias MIB object. Such an implementation needs
to use some mechanism to handle the differences in size
and characters allowed between this leaf and
entPhysicalAlias. The definition of such a mechanism is
outside the scope of this document.";
reference "RFC 6933: entPhysicalAlias";
}
leaf asset-id {
type string;
description
"This node is a user-assigned asset tracking identifier (as
specified by a network manager) for the component.
A server implementation MAY map this leaf to the
entPhysicalAssetID MIB object. Such an implementation
needs to use some mechanism to handle the differences in
size and characters allowed between this leaf and
entPhysicalAssetID. The definition of such a mechanism is
outside the scope of this document.";
reference "RFC 6933: entPhysicalAssetID";
}
leaf-list uri {
type inet:uri;
description
"This node contains identification information about the
component.";
reference "RFC 6933: entPhysicalUris";
}
leaf admin-state {
if-feature hardware-state;
type admin-state;
description
"The administrative state for this component.
This node refers to a component's administrative
permission to service both other components within its
containment hierarchy as well other users of its services
defined by means outside the scope of this module.
Some components exhibit only a subset of the remaining
administrative state values. Some components cannot be
locked, and hence this node exhibits only the 'unlocked'
state. Other components cannot be shutdown gracefully,
and hence this node does not exhibit the 'shutting-down'
state.";
reference "RFC 4268, entStateAdmin";
}
}
}
/*
* Notifications * Notifications
*/ */
notification hardware-state-change { notification hardware-state-change {
description description
"A hardware-state-change notification is generated when the "A hardware-state-change notification is generated when the
value of /hardware-state/last-change changes."; value of /hardware/last-change changes in the operational
state datastore.";
reference "RFC 6933, entConfigChange"; reference "RFC 6933, entConfigChange";
} }
notification hardware-state-oper-enabled { notification hardware-state-oper-enabled {
if-feature hardware-state; if-feature hardware-state;
description description
"A hardware-state-oper-enabled notification signifies that a "A hardware-state-oper-enabled notification signifies that a
component has transitioned into the 'enabled' state."; component has transitioned into the 'enabled' state.";
leaf name { leaf name {
type leafref { type leafref {
path "/hardware-state/component/name"; path "/hardware/component/name";
} }
description description
"The name of the component that has transitioned into the "The name of the component that has transitioned into the
'enabled' state."; 'enabled' state.";
} }
leaf admin-state { leaf admin-state {
type leafref { type leafref {
path "/hardware-state/component/state/admin-state"; path "/hardware/component/state/admin-state";
} }
description description
"The administrative state for the component."; "The administrative state for the component.";
} }
leaf alarm-state { leaf alarm-state {
type leafref { type leafref {
path "/hardware-state/component/state/alarm-state"; path "/hardware/component/state/alarm-state";
} }
description description
"The alarm state for the component."; "The alarm state for the component.";
} }
reference "RFC 4268, entStateOperEnabled"; reference "RFC 4268, entStateOperEnabled";
} }
notification hardware-state-oper-disabled { notification hardware-state-oper-disabled {
if-feature hardware-state; if-feature hardware-state;
description description
"A hardware-state-oper-disabled notification signifies that a "A hardware-state-oper-disabled notification signifies that a
component has transitioned into the 'disabled' state."; component has transitioned into the 'disabled' state.";
leaf name { leaf name {
type leafref { type leafref {
path "/hardware-state/component/name"; path "/hardware/component/name";
} }
description description
"The name of the component that has transitioned into the "The name of the component that has transitioned into the
'disabled' state."; 'disabled' state.";
} }
leaf admin-state { leaf admin-state {
type leafref { type leafref {
path "/hardware-state/component/state/admin-state"; path "/hardware/component/state/admin-state";
} }
description description
"The administrative state for the component."; "The administrative state for the component.";
} }
leaf alarm-state { leaf alarm-state {
type leafref { type leafref {
path "/hardware-state/component/state/alarm-state"; path "/hardware/component/state/alarm-state";
} }
description description
"The alarm state for the component."; "The alarm state for the component.";
} }
reference "RFC 4268, entStateOperDisabled"; reference "RFC 4268, entStateOperDisabled";
} }
} }
<CODE ENDS> <CODE ENDS>
<CODE BEGINS> file "iana-hardware@2017-03-07.yang" <CODE BEGINS> file "iana-hardware@2017-08-21.yang"
module iana-hardware { module iana-hardware {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:iana-hardware"; namespace "urn:ietf:params:xml:ns:yang:iana-hardware";
prefix ianahw; prefix ianahw;
organization "IANA"; organization "IANA";
contact contact
" Internet Assigned Numbers Authority " Internet Assigned Numbers Authority
skipping to change at page 34, line 19 skipping to change at page 31, line 48
description description
"IANA defined identities for hardware class."; "IANA defined identities for hardware class.";
reference reference
"https://www.iana.org/assignments/ianaentity-mib/ianaentity-mib"; "https://www.iana.org/assignments/ianaentity-mib/ianaentity-mib";
// RFC Ed.: replace XXXX with actual RFC number and remove this // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision 2017-03-07 { revision 2017-08-21 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Hardware Management"; "RFC XXXX: A YANG Data Model for Hardware Management";
} }
/* /*
* Identities * Identities
*/ */
identity hardware-class { identity hardware-class {
description description
skipping to change at page 38, line 34 skipping to change at page 36, line 13
'shutting-down' can cause disruption of services ranging from 'shutting-down' can cause disruption of services ranging from
those running on a port to those on an entire device, depending on those running on a port to those on an entire device, depending on
the type of component. the type of component.
Some of the readable data nodes in this YANG module may be considered Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability: nodes and their sensitivity/vulnerability:
/hardware-state/component: The leafs in this list expose information /hardware/component: The leafs in this list expose information about
about the physical components in a device, which may be used to the physical components in a device, which may be used to identify
identify the vendor, model, version, and specific device- the vendor, model, version, and specific device-identification
identification information of each system component. information of each system component.
/hardware-state/component/sensor-data/value: This node may expose /hardware/component/sensor-data/value: This node may expose the
the values of particular physical sensors in a device. values of particular physical sensors in a device.
/hardware-state/component/state: Access to this node allows one to /hardware/component/state: Access to this node allows one to figure
figure out what the active and standby resources in a device are. out what the active and standby resources in a device are.
10. Acknowledgments 10. Acknowledgments
The authors wish to thank the following individuals, who all provided The authors wish to thank the following individuals, who all provided
helpful comments on various draft versions of this document: Bart helpful comments on various draft versions of this document: Bart
Bogaert, Timothy Carey, William Lupton, Juergen Schoenwaelder. Bogaert, Timothy Carey, William Lupton, Juergen Schoenwaelder.
11. Normative References 11. Normative References
[I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-03
(work in progress), July 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor [RFC3433] Bierman, A., Romascanu, D., and K. Norseth, "Entity Sensor
Management Information Base", RFC 3433, Management Information Base", RFC 3433,
DOI 10.17487/RFC3433, December 2002, DOI 10.17487/RFC3433, December 2002, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3433>. editor.org/info/rfc3433>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 4268, [RFC4268] Chisholm, S. and D. Perkins, "Entity State MIB", RFC 4268,
DOI 10.17487/RFC4268, November 2005, DOI 10.17487/RFC4268, November 2005, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc4268>. editor.org/info/rfc4268>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<http://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6536>. editor.org/info/rfc6536>.
[RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M. [RFC6933] Bierman, A., Romascanu, D., Quittek, J., and M.
Chandramouli, "Entity MIB (Version 4)", RFC 6933, Chandramouli, "Entity MIB (Version 4)", RFC 6933,
DOI 10.17487/RFC6933, May 2013, DOI 10.17487/RFC6933, May 2013, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6933>. editor.org/info/rfc6933>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
Authors' Addresses Authors' Addresses
Andy Bierman Andy Bierman
YumaWorks YumaWorks
Email: andy@yumaworks.com Email: andy@yumaworks.com
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
 End of changes. 97 change blocks. 
349 lines changed or deleted 234 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/