A YANG Network Data Model of Network Inventory Software Extensions
draft-ietf-ivy-network-inventory-software-04
| Document | Type | Active Internet-Draft (ivy WG) | |
|---|---|---|---|
| Authors | Bo Wu , Cheng Zhou , Qin Wu , Mohamed Boucadair | ||
| Last updated | 2026-07-06 | ||
| Replaces | draft-wzwb-ivy-network-inventory-software | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Yang Validation | 0 errors, 0 warnings | ||
| Reviews |
OPSDIR Early review
by Chongfeng Xie
Has issues
YANGDOCTORS Early review
by Reshad Rahman
Almost ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | I-D Exists | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-ietf-ivy-network-inventory-software-04
Network Inventory YANG B. Wu
Internet-Draft Huawei
Intended status: Standards Track C. Zhou
Expires: 7 January 2027 China Mobile
Q. Wu
Huawei
M. Boucadair
Orange
6 July 2026
A YANG Network Data Model of Network Inventory Software Extensions
draft-ietf-ivy-network-inventory-software-04
Abstract
This document extends the base Network Inventory YANG model to
support non-physical network elements (NEs), such as controllers,
virtual routers, and virtual firewalls, as well as software
components like platform operating systems and software modules. In
addition to the software revisions and patches already defined in the
base model, this extension introduces software status and time stamp
information.
Discussion Venues
This note is to be removed before publishing as an RFC.
Discussion of this document takes place on the Network Inventory YANG
mailing list (inventory-yang@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/inventory-yang/.
Source for this draft and an issue tracker can be found at
https://github.com/ietf-ivy-wg/network-inventory-software.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Wu, et al. Expires 7 January 2027 [Page 1]
Internet-Draft Network Inventory Software July 2026
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 7 January 2027.
Copyright Notice
Copyright (c) 2026 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 Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Editorial Note (To be removed by RFC Editor) . . . . . . 3
1.2. Terminology and Notations . . . . . . . . . . . . . . . . 4
2. Relationship to Other YANG Data Models . . . . . . . . . . . 4
3. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 5
4. Non-physical Network Elements . . . . . . . . . . . . . . . . 6
5. Software Components . . . . . . . . . . . . . . . . . . . . . 6
6. YANG Data model for Network Inventory Software Extensions . . 7
7. Operational Considerations . . . . . . . . . . . . . . . . . 11
8. Security Considerations . . . . . . . . . . . . . . . . . . . 12
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Examples of Software Attributes . . . . . . . . . . 15
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 17
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
Wu, et al. Expires 7 January 2027 [Page 2]
Internet-Draft Network Inventory Software July 2026
1. Introduction
The Network Inventory consists of the physical and non-physical
network elements (NEs), hardware components, firmware components, and
software components on a managed network domain. The non-physical
network elements (NEs) are network devices that support network
protocols and functions, e.g., routers, firewalls, and controllers,
which can reside in any network or compute devices, such as servers
in Data Center (DC), server-based virtual machines (VMs), or server-
based containers.
[I-D.ietf-ivy-network-inventory-yang] defines the base Network
Inventory YANG model for physical network element (NE) and hardware
components of NEs. Examples of hardware components could be rack,
shelf, slot, board and physical port.
The management of non-physical NE and software components information
is similar to the management of physical NE and hardware information.
For example, inventory data, including product names, serial numbers,
etc. are also applicable. This document defines a network inventory
software extension YANG model. In addition to inheriting the common
inventory attributes of the base network inventory model, this
document also adds some software-specific attributes of non-physical
NEs (such as controllers, virtual routers, and virtual firewalls) and
software components (such as operating system, software modules,
BIOS, and boot loader).
The Network Inventory software extension model is classified as a
network model (Section 4 of [RFC8309]).
The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) defined in [RFC8342].
1.1. Editorial Note (To be removed by RFC Editor)
Note to the RFC Editor: This section is to be removed prior to
publication.
This document contains placeholder values that need to be replaced
with finalized values at the time of publication. This note
summarizes all of the substitutions that are needed.
Please apply the following replacements:
* XXXX --> the assigned RFC number for this I-D
* AAAA --> the assigned RFC number for
[I-D.ietf-ivy-network-inventory-yang]
Wu, et al. Expires 7 January 2027 [Page 3]
Internet-Draft Network Inventory Software July 2026
1.2. Terminology and Notations
The following terms are defined in [RFC7950] and are not redefined
here:
* client
* server
* augment
* data model
* data node The following terms are defined in [RFC6241] and are not
redefined here:
* configuration data
* state data The tree diagram used in this document follows the
notation defined in [RFC8340].
Also, this document uses terms defined in
[I-D.ietf-ivy-network-inventory-yang].
2. Relationship to Other YANG Data Models
The base network inventory model supports the software versions of
NEs and software versions of hardware components. This document adds
more software component identifiers (e.g., platformos, software
patch) and more NE types (e.g., software NE, virtual NE) to provide
enhanced software information on the NE to facilitate software
compatibility check.
Figure 1 depicts the relationship between the Software Extension
model and the base network inventory model. The Software Extension
network inventory model enhances the model defined in the base
network inventory model with more software specific attributes.
Wu, et al. Expires 7 January 2027 [Page 4]
Internet-Draft Network Inventory Software July 2026
+----------------------+
| |
|Base Network Inventory|
| |
+----------^-----------+
|
|
|
|
+----------^-----------+
| |
| Software Extensions |
| e.g., SW module |
| |
+----------------------+
Figure 1: Relationship of SW Extension Model to the Base
Inventory Model
3. Model Overview
The tree diagram in Figure 2 provides an overview of the data model
for "ietf-network-inventory-sw-ext" module.
The model applies software extension attributes at two levels:
* NE-level "software-rev": Describes the main system software
revision of the network element, such as the network operating
system release of the whole device.
* Component-level "software-rev": Describes the independent software
or firmware revision of an individual component, such as a line
card software, a line card firmware, or a pluggable software
module.
Wu, et al. Expires 7 January 2027 [Page 5]
Internet-Draft Network Inventory Software July 2026
module: ietf-network-inventory-sw-ext
augment /nwi:network-inventory/nwi:network-elements
/nwi:network-element/nwi:software-rev:
+--ro status? identityref
+--ro installation-time? yang:date-and-time
+--ro activation-time? yang:date-and-time
augment /nwi:network-inventory/nwi:network-elements
/nwi:network-element/nwi:software-rev/nwi:patch:
+--ro status? identityref
+--ro installation-time? yang:date-and-time
+--ro activation-time? yang:date-and-time
augment /nwi:network-inventory/nwi:network-elements
/nwi:network-element/nwi:components/nwi:component
/nwi:software-rev:
+--ro status? identityref
+--ro installation-time? yang:date-and-time
+--ro activation-time? yang:date-and-time
augment /nwi:network-inventory/nwi:network-elements
/nwi:network-element/nwi:components/nwi:component
/nwi:software-rev/nwi:patch:
+--ro status? identityref
+--ro installation-time? yang:date-and-time
+--ro activation-time? yang:date-and-time
Figure 2: YANG Tree of Software Extensions
4. Non-physical Network Elements
In the base Network Inventory YANG model, "ne-type" is a YANG
identity that describes the type of the network element and only the
"physical-network-element" identity" is defined. This document adds
non-physical NE identity, such as "ne-software", "ne-virtual", and
"ne-container".
The base Network Inventory model also defines common inventory
attributes, including the software version, patch versions, product
name, and serial number. The data is also applicable to non-physical
NEs.
The Network Inventory software extension mode defines some new
software attributes, consisting of software status, installation
time, and activation time.
5. Software Components
Software components refer to the software installed on the NE, such
as operating system, software modules, BIOS, and boot loaders.
Wu, et al. Expires 7 January 2027 [Page 6]
Internet-Draft Network Inventory Software July 2026
Similar to the common inventory attributes of NEs, the common
attributes of software components (such as software revisions, patch
revisions, product name, and serial number) are also applicable to
software components. For software revisions and patch revisions, the
base inventory (Section 4 of [I-D.ietf-ivy-network-inventory-yang])
defines the "list" of "software-rev" and the "list" of "patch". For
example, on a router, software components may include a routing
protocol package (e.g., " foo-rt-protocol-suite"), or a firmware
module for a line card (e.g., " foo-lc-fw-21.5.3").
If more detailed installation and activation information is needed,
such as whether a component is active, pending-reboot, or rollback-
eligible, along with its install time or activation time stamp, the
extension attributes of software components can be used.
6. YANG Data model for Network Inventory Software Extensions
The "ietf-network-inventory-sw-ext" module uses types defined in
[RFC9911], [I-D.ietf-ivy-network-inventory-yang].
<CODE BEGINS> file "ietf-network-inventory-sw-ext@2026-07-06.yang"
module ietf-network-inventory-sw-ext {
yang-version 1.1;
namespace
"urn:ietf:params:xml:ns:yang:ietf-network-inventory-sw-ext";
prefix nwis;
import ietf-yang-types {
prefix yang;
reference
"RFC 9911: Common YANG Data Types";
}
import ietf-network-inventory {
prefix nwi;
reference
"RFCAAAA: A YANG Data Model for Network Inventory";
}
organization
"IETF Network Inventory YANG (ivy) Working Group";
contact
"WG Web: <https://datatracker.ietf.org/wg/ivy>
WG List: <mailto:inventory-yang@ietf.org>
Editor: Bo Wu
<lana.wubo@huawei.com>
Editor: Cheng Zhou
<zhouchengyjy@chinamobile.com>
Wu, et al. Expires 7 January 2027 [Page 7]
Internet-Draft Network Inventory Software July 2026
Editor: Qin Wu
<bill.wu@huawei.com>
Editor: Mohamed Boucadair
<mohamed.boucadair@orange.com>";
description
"This YANG module defines a model for network inventory software
extensions.
Copyright (c) 2026 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Revised BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices.";
revision 2026-07-06 {
description
"Initial version";
reference
"RFC XXXX: A YANG Data Model for Network Inventory Software
Extensions.";
}
identity ne-nonphysical {
base nwi:ne-type;
description
"Any network element implemented purely in software.
It performs protocol or forwarding functions but
does not correspond to a distinguishable hardware
chassis. It can be hosted on a bare-metal server,
VM, container, or cloud instance.";
}
identity ne-software {
base ne-nonphysical;
description
"Software NE that runs directly on a host OS
(also known as bare-metal deployment) or hypervisor.
Examples of software NEs are network controllers.";
}
identity ne-virtual {
Wu, et al. Expires 7 January 2027 [Page 8]
Internet-Draft Network Inventory Software July 2026
base ne-nonphysical;
description
"Virtual NE instantiated inside a virtual-machine
(VM). Provides virtual network function (VNF) implementations
such as vRouter, vFirewall, vPE.";
}
identity ne-container {
base ne-nonphysical;
description
"Container NE packaged as CNF (Containerised Network
Function). Runs under Docker/K8s.";
}
identity software-component {
base nwi:non-hardware-component-class;
description
"Base identity for software components in a managed device.";
}
identity operating-system {
base software-component;
description
"Operating system software type.";
}
identity bios {
base software-component;
description
"System firmware responsible for hardware initialization
and system boot.";
}
identity boot-loader {
base software-component;
description
"Software layer responsible for loading and booting the
device OS or network OS.";
}
identity software-module {
base software-component;
description
"Installable unit smaller than a full OS image,
e.g., feature package.";
}
identity software-status {
Wu, et al. Expires 7 January 2027 [Page 9]
Internet-Draft Network Inventory Software July 2026
description
"Base identity for software status.";
}
identity software-installed {
base software-status;
description
"Software or patch is installed on the network element
or component but not yet active.";
}
identity software-activated {
base software-status;
description
"Software or patch is active and taking effect
on the network element or component.";
}
grouping software-info-grouping {
description
"Specific attributes applicable to software.";
leaf status {
type identityref {
base software-status;
}
description
"Software status.";
}
leaf installation-time {
type yang:date-and-time;
description
"Time when the software or patch revision was
first installed.";
}
leaf activation-time {
type yang:date-and-time;
description
"Time when the currently installed revision became active
(i.e., was rebooted into).";
}
}
/* Main blocks */
augment "/nwi:network-inventory/nwi:network-elements"
+ "/nwi:network-element/nwi:software-rev" {
description
"Adds installation-/activation-time, status, etc. to the base
Wu, et al. Expires 7 January 2027 [Page 10]
Internet-Draft Network Inventory Software July 2026
NE software revision.";
uses software-info-grouping;
}
augment "/nwi:network-inventory/nwi:network-elements"
+ "/nwi:network-element/nwi:software-rev/nwi:patch" {
description
"Adds installation-/activation-time, status, etc. to the patch
level.";
uses software-info-grouping;
}
augment "/nwi:network-inventory/nwi:network-elements/"
+ "nwi:network-element/nwi:components/nwi:component/"
+ "nwi:software-rev" {
description
"Extends components, such as line-card/CPU/etc.
software revision with timestamp and state information.";
uses software-info-grouping;
}
augment "/nwi:network-inventory/nwi:network-elements/"
+ "nwi:network-element/nwi:components/nwi:component/"
+ "nwi:software-rev/nwi:patch" {
description
"Applies the software-info attributes to component-level
patches.";
uses software-info-grouping;
}
}
<CODE ENDS>
7. Operational Considerations
This section complements the operational considerations of the base
network inventory model [I-D.ietf-ivy-network-inventory-yang]. The
considerations of [I-D.ietf-ivy-network-inventory-yang] also apply to
this extension: the read-only perspective of inventory data, data
discovery by the server from underlying elements, aggregation at
hierarchical controller interfaces, and brownfield migration
scenarios.
This model provides read-only reporting of software status and
associated timestamps. It reflects the state of software revisions
and patches as discovered by the server; it does not track software
configuration intent or repository state.
Wu, et al. Expires 7 January 2027 [Page 11]
Internet-Draft Network Inventory Software July 2026
The software inventory data is discovered by the server from
underlying managed entities using implementation-specific mechanisms.
The installation-time and activation-time timestamps, as well as the
software status (installed or activated), are reported as discovered
from the managed entity.
Software lifecycle management operations (install, activate, remove,
etc.) are out of scope and could be defined in separate YANG modules.
8. Security Considerations
This section is modeled after the template described in Section 3.7
of [RFC9907].
The "ietf-network-inventory-sw-ext" YANG module augments the base
network inventory model defined in
[I-D.ietf-ivy-network-inventory-yang]. All security considerations
specified in the base model apply to this extension module. This
section complements the base model with additional security
considerations specific to software inventory extensions.
The "ietf-network-inventory-sw-ext" YANG module defines a data model
that is designed to be accessed via YANG-based management protocols,
such as NETCONF [RFC6241] and RESTCONF [RFC8040]. These YANG-based
management protocols (1) have to use a secure transport layer (e.g.,
SSH [RFC4252], TLS [RFC8446], and QUIC [RFC9000]) and (2) have to use
mutual authentication.
The Network Configuration Access Control Model (NACM) [RFC8341]
provides the means to restrict access for particular NETCONF or
RESTCONF users to a preconfigured subset of all available NETCONF or
RESTCONF protocol operations and content.
Some of the readable data nodes in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes.
Specifically, the following subtrees and data nodes have particular
sensitivities/vulnerabilities:
* "/nwi:network-elements/network-element/software-rev"
* "/nwi:network-elements/network-element/software-rev/patch"
* "/nwi:network-elements/network-element/components/component/
software-rev"
Wu, et al. Expires 7 January 2027 [Page 12]
Internet-Draft Network Inventory Software July 2026
* "/nwi:network-elements/network-element/component/component/
software-rev/patch" > These extension add status, installation
time, and activation time to both NE-level and component-level
software revisions and patches. Disclosure of detailed software
versions, patch levels, and lifecycle timestamps can reveal
unpatched vulnerabilities and operational maintenance windows,
enabling targeted attacks.
9. IANA Considerations
IANA is requested to register the following URI in the "ns"
subregistry within the "IETF XML Registry" [RFC3688]:
URI: urn:ietf:params:xml:ns:yang:ietf-network-inventory-sw-ext
Registrant Contact: The IESG.
XML: N/A; the requested URI is an XML namespace.
IANA is requested to register the following YANG module in the "YANG
Module Names" registry [RFC6020] within the "YANG Parameters"
registry group:
Name: ietf-network-inventory-sw-ext
Namespace: urn:ietf:params:xml:ns:yang:ietf-network-inventory-sw-ext
Prefix: nwis
Maintained by IANA? N
Reference: RFC XXXX
10. References
10.1. Normative References
[I-D.ietf-ivy-network-inventory-yang]
Yu, C., Belotti, S., Bouquier, J., Peruzzini, F., and P.
Bedard, "A Base YANG Data Model for Network Inventory",
Work in Progress, Internet-Draft, draft-ietf-ivy-network-
inventory-yang-18, 27 May 2026,
<https://datatracker.ietf.org/doc/html/draft-ietf-ivy-
network-inventory-yang-18>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004,
<https://www.rfc-editor.org/rfc/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010,
<https://www.rfc-editor.org/rfc/rfc6020>.
Wu, et al. Expires 7 January 2027 [Page 13]
Internet-Draft Network Inventory Software July 2026
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/rfc/rfc6241>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/rfc/rfc7950>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/rfc/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/rfc/rfc8342>.
[RFC9911] Schönwälder, J., Ed., "Common YANG Data Types", RFC 9911,
DOI 10.17487/RFC9911, December 2025,
<https://www.rfc-editor.org/rfc/rfc9911>.
10.2. Informative References
[RFC4252] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Authentication Protocol", RFC 4252, DOI 10.17487/RFC4252,
January 2006, <https://www.rfc-editor.org/rfc/rfc4252>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/rfc/rfc8040>.
[RFC8309] Wu, Q., Liu, W., and A. Farrel, "Service Models
Explained", RFC 8309, DOI 10.17487/RFC8309, January 2018,
<https://www.rfc-editor.org/rfc/rfc8309>.
[RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams",
BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018,
<https://www.rfc-editor.org/rfc/rfc8340>.
[RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol
Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018,
<https://www.rfc-editor.org/rfc/rfc8446>.
Wu, et al. Expires 7 January 2027 [Page 14]
Internet-Draft Network Inventory Software July 2026
[RFC9000] Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based
Multiplexed and Secure Transport", RFC 9000,
DOI 10.17487/RFC9000, May 2021,
<https://www.rfc-editor.org/rfc/rfc9000>.
[RFC9907] Bierman, A., Boucadair, M., Ed., and Q. Wu, "Guidelines
for Authors and Reviewers of Documents Containing YANG
Data Models", BCP 216, RFC 9907, DOI 10.17487/RFC9907,
March 2026, <https://www.rfc-editor.org/rfc/rfc9907>.
Appendix A. Examples of Software Attributes
This appendix illustrates, by means of two typical scenarios, how to
populate the software-specific nodes defined in ietf-network-
inventory-sw-ext and explains the common values that can be used.
Scenario 1: Whole-device base software (example-os) plus hot patches
(P3 already activated, P4 installed but not yet activated).
Scenario 2: Line-card programmable forwarding image (example-fpga-
image) plus its patch (2.1.0.P1 installed and awaiting activation).
=============== NOTE: '\' line wrapping per RFC 8792 ================
{
"ietf-network-inventory:network-inventory": {
"network-elements": {
"network-element": [
{
"ne-id": "example:NE-01",
"software-rev": [
{
"name": "example:ne-os",
"revision": "7.9.2",
"ietf-network-inventory-sw-ext:status": "software-\
activated",
"ietf-network-inventory-sw-ext:installation-time": "\
2024-08-01T12:00:00Z",
"ietf-network-inventory-sw-ext:activation-time": "2024\
-08-01T12:05:00Z",
"patch": [
{
"revision": "P3",
"ietf-network-inventory-sw-ext:status": "software-\
activated",
"ietf-network-inventory-sw-ext:installation-time"\
: "2024-09-15T10:30:00Z",
"ietf-network-inventory-sw-ext:activation-time": "\
Wu, et al. Expires 7 January 2027 [Page 15]
Internet-Draft Network Inventory Software July 2026
2024-09-15T10:32:00Z"
},
{
"revision": "P4",
"ietf-network-inventory-sw-ext:status": "software-\
installed",
"ietf-network-inventory-sw-ext:installation-time"\
: "2024-10-01T14:00:00Z",
"ietf-network-inventory-sw-ext:activation-time": \
null
}
]
}
],
"components": {
"component": [
{
"component-id": "example:lpu/1/0",
"class": "iana-hardware:module",
"software-rev": [
{
"name": "example-fp-image",
"revision": "2.1.0",
"ietf-network-inventory-sw-ext:status": "\
software-activated",
"ietf-network-inventory-sw-ext:installation-time\
": "2024-08-01T12:00:00Z",
"ietf-network-inventory-sw-ext:activation-time"\
: "2024-08-01T12:06:00Z",
"patch": [
{
"revision": "2.1.0.P1",
"ietf-network-inventory-sw-ext:status": "\
software-installed",
"ietf-network-inventory-sw-ext:installation-\
time": "2024-10-01T14:10:00Z",
"activation-time": null
}
]
}
]
}
]
}
}
]
}
}
Wu, et al. Expires 7 January 2027 [Page 16]
Internet-Draft Network Inventory Software July 2026
}
Acknowledgments
The authors would like to thank Prasenjit Manna, Phil Bedard, Diego
R. Lopez, Italo Busi, Adrian Farrel, and many others for their
helpful comments and suggestions.
Contributors
Yao Zhao
Huawei
Email: zhaoyao.zhaoyao@huawei.com
Authors' Addresses
Bo Wu
Huawei
Email: lana.wubo@huawei.com
Cheng Zhou
China Mobile
Email: zhouchengyjy@chinamobile.com
Qin Wu
Huawei
Email: bill.wu@huawei.com
Mohamed Boucadair
Orange
Email: mohamed.boucadair@orange.com
Wu, et al. Expires 7 January 2027 [Page 17]