Network inventory is a foundation for network management in all types of networks: Network operators need to keep a record of what equipment is planned and installed in their networks (including a variety of information such as product name, vendor, product series, embedded software, and hardware/software versions). For auditing purposes, inventories may also be used to collect information from the network, as well as for cataloging and exposing that information. The purpose of the NIMBY WG is to provide a venue for discussion of inventory YANG models from across IETF Areas and Working Groups under a common umbrella to facilitate distribution of the work, clarify the scope of each model, and minimize overlap between them. An objective of this effort is to derive common building-blocks for inventory modeling that can be augmented, imported, or reused by other IETF models. The WG will also identify a set of requirements and some guidelines to ensure consistency across models related to inventory. The Working Group may also act as a coordinator of the inventory work, dispatching it toward Working Groups in the Operations and Management Area as well as other Areas. The scope of the work extends to the inventory of network elements that operate at layers 0-3 and will include both hardware and software inventory. Mapping the inventory models that will be produced by the WG into existing IETF models (e.g., ietf-network-topology) is also in scope. The Working Group will consider existing IETF work, including RFC 8348 and RFC 8345. Details of how the inventory content is used is outside the scope of the Working Group. The NIMBY WG will focus on the following activities. It is expected that many of these items will not lead to the publication of RFCs, although Internet-Drafts may be used to track discussions and establish consensus: A. Hardware/Software components including licenses: Hardware and Software component management to allow network operators to keep track of which physical/virtual devices are deployed in the network, including software and hardware versions as well as licenses/entitlement. B. Physical locations: Indicate the physical position of the network elements (such as, site, room, rack, shelf, slot) to provide precise location information. C. Terminology and Scope: Definition of the scope of inventory as well as a common architecture and terminology. An effort will be made to keep terminology aligned with, or mapped to, industry-wide activities including initiatives in the ITU-T, TMF, MEF, Openconfig, and ONF. D. Features and Capabilities: Report the available/supported capabilities and features facilitating function, usability, and accessibility. E. Multi-domain and multi-layer: Consistent representation and reporting of network inventory to maintain a centralized view of all network element component types across multiple network segments and layers of the underlying network under the same management and ownership. F. Mapping and correlation semantics: Correlating the inventory with existing IETF models e.g., topology, service attachment points (SAP), etc. G. Security and privacy issues: The information in a network inventory is highly sensitive as it exposes critical information about the internal topology and characterization of the components that are used to build that topology. Mechanisms to ensure topology hiding and prevent unauthorized access are expected to be in place. However, the Working Group may consider whether additional security mechanisms are needed to protect this information from unauthorized access and manipulation.