]> Futurewei

aihuaguo.ietf@gmail.com

Nokia

tom.van_caenegem@nokia.com

Ciena

ndavis@ciena.com

FiberCop

mauro.tilocca@fibercop.it

NBN

bradpeters@nbnco.com.au

Operations and Management Network Inventory YANG next generation unicorn sparkling distributed ledger This document presents a YANG data model for tracking and managing passive network inventory. The model augments the base network inventory model. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the Network Inventory YANG Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction Passive infrastructure refers to the underlying infrastructure of a telecommunication network that is not actively detectable or manageable. It typically includes non-powered, non-communicating devices and components, such as cabinets, cables, connectors, splitters, antennas, distribution frames, etc., that are either hosted within an actively managed device or deployed along the physical pathway between active devices. Passive infrastructure serves as physical connections between active network devices, forming the backbone for network topology. As a crucial part of communication networks,the inventory information for these devices is also essential for inventory management. Passive inventory contains a collection of inventory objects pertaining to the physical network infrastructure that are not powered and may have no direct management communication, and that are used to realize the underlying physical infrastructure carrying signals through a network. Passive inventory includes elements such as optical cables, fiber segments, splice points, closures, ducts, and supporting structures that do not perform active processing, forwarding, or control functions. These objects are maintained for purposes such as identification, location, connectivity, and lifecycle management. While passive inventory generally refers to non-powered infrastructure with no direct management communication, certain exceptions exist within the scope of passive inventory with respect to these characteristics. Following are a non-exhausive list of exceptions:

• Fibers used in Raman amplification, where the fiber itself participates in amplification stimulated by an externally supplied pump laser. In this scenario, the fiber is still considered as a passive element.
• Passive optical components embedded within an active device, such as an optical splitter located inside a managed network element.
• Fibers or other passive elements that are not currently lit or carrying traffic, but are still part of the physical infrastructure and require inventory representation.
• Passive devices that may have auxiliary or incidental powering (e.g., for environmental monitoring or enclosure heating) but do not perform active forwarding, processing, or control functions. incorporates the component concept from to detail the equipment and holder information of a NE. This encompasses chassis, slot/sub-slot, board/sub-board, port, and transceiver. As these items are recognized by the NE through internal protocols, the passive devices that cannot be discovered by the NE are thus not included in the modeling and needs to be addressed.

emphasizes the relative and geographic location, e.g. equipment room, geo-loation for NE. A passive device is deployed in a certain location visible by the operator, and thus can reference the location defined by . This document focuses on modeling passive device inventory. The scope of this model is intended to be applicable to a varity types of networks, including but not limited to, IP/MPLS, optical access, optical transport and microwave networks. The methods for learning about these devices are implementation-specific and fall outside the scope of this document.

Examples of Passive Network Inventory Network segments built on different technologies share many common passive infrastructure components across the system. To explore the practical applications of these components, we can examine example scenarios for optical access networks, optical transport systems, and microwave networks.

Passive Infrastructure in Optical Transport Networks Passive infrastructure in optical transport networks serves as the backbone for high-capacity data transmission. Key components include fiber optic cables, which act as the primary medium of long distance transmission. Optical connectors, patch panels, and splice enclosures are crucial for joining and managing fiber links. Couplers and splitters are used for signal distribution and combining. Within a phyical network element (NE) there are also presence of passive components. For example, fiber optic cables are used to connect the ports of different modules within the same or between different chassises. Attenuators, on the other hand, are placed at places through connectors or built-in modules for reducing optical power. illustrates a typical passive infrastructure for a point-to-point optical transport network.

Passive Infrastructure for Optical Transport Networks | +-+ |<--Cable--->| +++ | | | | ++* +---+ | | / \ | | +---+ *++ | | | |NE |\+++ | |Cable- Cable| / \ |Cable- Cable| | +++/| NE| | | +---+ *++ +++|<-->| |<-->+++/ \+++<->| |<--->|+++ ++* +---+ | | | + +|----| |----+ |----------| +---| |-----|+ + | | | +++ +++|----| |----+++\ /+++---| |-----|+++ +++ | | +---+/*++ | | - | \ / | - | | ++*\+---+ | | | +*+ |ODF| | Joint | \ / | Joint | |ODF| +*+ | | | | +++ +---+ | Box | \ / | Box | +---+ +++ | | | |NE | | | *-+ | | | NE| | | +---+ | +-----+ +----+ | +---+ | |Central Office| +-+ |Central Office| +--------------+ Fiber +--------------+ Distribution Terminal ]]>

Passive Infrastructure in Optical Access Networks Passive Optical Networks (PONs) are a typical type of optical access network with significant passive infrastructure. The passive infrastructure in PON, often referred to as Optical Distribution Network (ODN), is the physical optical fiber-based network that connects the Optical Line Terminal (OLT) typically hosted in a central office to the Optical Network Unit/Terminal (ONU/ONT) typically deployed at the user's location. The ODN is equipped with one or multiple cascaded passive optical splitter thus creating a physical point-to-multipoint fiber network between an OLT port and the multiple connected ONU/ONTs. The feeder segment of an ODN refers to the cabling between the OLT and the first splitter, whereas the distribution segment of the ODN comprises the fiber cabling between the first and second splitter stage. The drop segment comprises the drop fibers between the ONT/ONU and the second splitter stage. The PON ODN hence comprises optical fiber cables and splitters but also many auxiliary components, such as connectors, fiber distribution terminals (FDT), fiber access terminals (FAT), wavelength co-existence elements, etc. The passive components where the optical signals entering or leaving the optical fibers are split/combined or cross-connected are typically hosted in mini cabinets e.g. at street corners, manholes, attached to utility poles, etc. illustrates a typical passive infrastructure for optical access networks.

Passive Infrastructure for Optical Access Networks | +---+ | Cable | | +++ |<-Feeder Cable-> <--Distr.--> /|----------+-+ONU | | ++* +---+ | Cable / | +-+ | |NE |\+++ | | Cable - Cable /|------------x |FDT | +---+ *++ +++|<---->/ \<----> / | \ | | (OLT) | + +|------| |------x/ | \|----------+-+ONU | +++ +++|------| |------x | cccccccc +-+ | +---+/*++ | | \ / \ | c /| c | | +*+ |ODF| | - \ | c / | c | | +++ +---+ | Joint \|-c-x | c | |NE | | Box FDT c \ | c<---Drop Cable-->+-+ONU | +---+ | c \|-c-----------------+-+ | (OLT) | c FDT

Passive Infrastructure in Microwave Networks To be developed.

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
• YYYY --> the assigned RFC number for
• ZZZZ --> the assigned RFC number for

Please replace the revision date of the latest revision of the 'ietf-nwi-passive-inventory' module with the publication date of this I-D, using the the format (year-month-day). Please manually fix the YANG trees in which have been generated by pyang and have some bugs.

Terminology and Notations

Terminology The following terms are defined in and are not redefined here:

• client
• server
• augment
• data model
• data node

The following terms are defined in and are not redefined here:

• configuration data
• state data

The following terms are defined and used in this document.

• Passive device: refers to a physical device within a network that does not require external power to function, and simply manipulates signals through processes like transmission, reflection, splitting, filtering, or attenuation without actively amplifying or generating the signal. Examples include optical fibers, splitters, couplers, and optical filters, all of which are used to direct signals within a system without needing power. A passive device typically does not have management interfaces and is typically deployed in a location tracked by the network operator.
• Active device: refers to a physical device that contains hardware and software and is managable through communication interfaces. Network elements defined by are examples of active device.
• Guiding media: refers to physical transmission pathways - such as optical fiber cables, electrical cables, and coaxial cables - that direct and confine electromagnetic signals along a specific route. These media provide a bounded channel for data transmission, ensuring signal integrity, minimizing interference, and enabling high-speed communication over varying distances. This category is also commonly known as guided media or wired transmission media. Guiding media can be concatenated to form longer guiding media.
• Optical Cable: refers to a type of guiding media that uses optical fiber as media to transmit optical signals. An optical cable can contain one or multiple fiber cores, also known as fiber strands, each serving as an independent guiding media for data transmission. Optical cables can be spliced or fused through joint boxes, optical distribution frames (ODF), or fiber jumpers.
• Electrical Cable: refers to a type of guiding media that uses metal conductors (such as copper or aluminum wires) as a medium to carry electrical signals for communication or power distribution. Common examples include twisted-pair cables (such as CAT-5/6 and DSL cables), and coaxial cables, which feature a single-core conductor commonly used in DOCSIS and MoCA-based broadband access networks. Electrical cables can be connected through splicing, connectors, or junction boxes.

Tree Diagram Tree diagrams used in this document follow the notation defined in .

Prefixes in Data Node Names In this document, names of data nodes and other data model objects are prefixed using the standard prefix associated with the corresponding YANG imported modules, as shown in . Prefixes and corresponding YANG module

Prefix	YANG module	Reference
nwi	ietf-network-inventory	[RFCYYYY]
nil	ietf-ni-location	[RFCZZZZ]
l0-types	ietf-layer0-types	RFC XXXX

Modeling Considerations

Relationship with Network Inventory TBD

Relationship with Topology TBD

YANG Model Overview The YANG data model in this draft augments the model defined in with the following information:

• Passive devices: a list of passive devices with extended attributed reported by the domain controller.
• Cables: a list of cables with each containing an optional list of child cables.

YANG Modules

YANG Data Model for Passive Device Inventory

YANG model for passive network inventory WG List: Editor: Chaode Yu Editor: Aihua Guo Editor: Italo Busi "; description "This YANG module specifies a data model for passive devices, such as fibers, cables, and passive sites, deployed within and between network elements. 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-03-19 { description "Initial version"; reference "RFC XXXX: A YANG Data Model for Passive Device Info in Network Inventory."; } /* Identities */ identity fiber-type { description "Base identity for fiber types."; } identity G652A { base fiber-type; description "ITU-T G.652A fiber."; } identity G652B { base fiber-type; description "ITU-T G.652B fiber."; } identity G652C { base fiber-type; description "ITU-T G.652C fiber."; } identity G652D { base fiber-type; description "ITU-T G.652D fiber."; } identity G653 { base fiber-type; description "ITU-T G.653 fiber."; } identity G654 { base fiber-type; description "ITU-T G.654 fiber."; } identity G655 { base fiber-type; description "ITU-T G.655 fiber."; } identity G656 { base fiber-type; description "ITU-T G.656 fiber."; } identity G657A1 { base fiber-type; description "ITU-T G.657A1 fiber."; } identity G657A2 { base fiber-type; description "ITU-T G.657A2 fiber."; } identity G657B { base fiber-type; description "ITU-T G.657B fiber."; } identity other { base fiber-type; description "Other type of fiber."; } identity cable-type { description "Base identity for cable types."; } identity optical-fiber { base cable-type; description "Fiber optic cable."; } identity electrical-cable { base cable-type; description "Electrical cable."; } identity coaxial-cable { base electrical-cable; description "Coaxial cable."; } identity cable-role { description "Base identity for cable roles."; } identity backbone { base cable-role; description "Backbone cable."; } identity aggregation { base cable-role; description "Aggregation cable."; } identity access { base cable-role; description "Access cable."; } identity trunk { base cable-role; description "Trunk cable."; } identity distribution { base cable-role; description "Distribution cable."; } identity branch { base cable-role; description "Branch cable."; } identity passive-port-type { description "Base identity for passive port types."; } identity service-port { base passive-port-type; description "Service port."; } identity input-port { base passive-port-type; description "Input port."; } identity output-port { base passive-port-type; description "Output port."; } identity p2mp-port { base passive-port-type; description "Input port."; } identity connected-device-type { description "Base identity for connected device types."; } identity passive-device { base connected-device-type; description "Passive/unmanaged device."; } identity active-device { base connected-device-type; description "Active device, e.g. network element."; } identity passive-device-type { description "Base identity for passive device types."; } identity ODF { base passive-device-type; description "Optical Distribution Frame."; } identity WDM { base passive-device-type; description "Wavelength Division Multiplexer."; } identity FAT { base passive-device-type; description "Fiber Access Terminal."; } identity FDT { base passive-device-type; description "Fiber Distribution Terminal."; } identity ATB { base passive-device-type; description "Access Terminal Box."; } /* Groupings */ grouping connected-device-end { description "Attributes applicable to connected device end."; leaf device-type { type identityref { base connected-device-type; } description "Type of connected device."; } choice connected-device-type { description "Device end based on the type of connected device."; case passive { leaf device-id { type string; must "derived-from-or-self(../device-type, 'nwi-passive:passive-device')"; description "Connected passive device identifier."; } } case active { leaf ne-ref { type leafref { path "/nwi:network-inventory/nwi:network-elements" + "/nwi:network-element/nwi:ne-id"; } must "derived-from-or-self(../device-type, 'nwi-passive:active-device')"; description "Referenced Network Element (NE)."; } leaf component-ref { type leafref { path "/nwi:network-inventory/nwi:network-elements" + "/nwi:network-element[nwi:ne-id=current()/.." + "/ne-ref]/nwi:components/nwi:component" + "/nwi:component-id"; } must "derived-from-or-self(../device-type, 'nwi-passive:active-device')"; description "Referenced connected active device's component, e.g. port component."; } } } } grouping connected-device-ref { description "Attributes applicable to connected devices."; container a-end { description "A-end device reference"; uses connected-device-end; } container z-end { description "Z-end device reference"; uses connected-device-end; } } grouping common-cable-attributes { description "Common attributes of cables applicable to the cable and its child cables."; leaf id { type string; description "Cable identifier."; } leaf length { type uint32; units "meter"; description "Length of the cable in meter."; } uses connected-device-ref; } grouping optical-cable-attributes { description "Attributes applicable to fiber optic cables."; container optical-cable { when "derived-from-or-self(../cable-type, 'optical-fiber')"; description "Container for attributes associated with fiber optic cables."; leaf fiber-core-num { type uint32; description "Number of fiber cores within the cable."; } leaf fiber-type { type identityref { base fiber-type; } description "Type of fiber contained in the cable."; } leaf attenuation { type decimal64 { fraction-digits 2; } units "dB"; description "The fiber attenuation in dB."; } } } grouping cable-attributes { description "Attributes of cables."; uses common-cable-attributes; uses nwi:basic-common-entity-attributes; leaf cable-type { type identityref { base cable-type; } description "Type of cable."; } leaf cable-role { type identityref { base cable-role; } description "Role of cable."; } uses optical-cable-attributes; } grouping child-cables { description "Attributes applicable to child cables that are concatnated to form the cable."; list child-cable { key "index"; min-elements 2; description "Ordered list of concatenated child cables."; leaf index { type uint8; description "An index number used to identify the concatenation order of the child cables."; } uses common-cable-attributes; } } grouping cables { description "Attributes applicable to cables."; list cable { key "id"; description "List of cables."; uses cable-attributes; uses child-cables; } } grouping passive-device-ports { description "Attributes applicable to passive device ports."; list passive-port { key "id"; description "List of ports on a passive device."; leaf id { type string; description "Port identifier."; } uses nwi:basic-common-entity-attributes; leaf port-type { type identityref { base passive-port-type; } description "Type of passive port."; } leaf fiber-core-num { type uint32; description "Number of fiber cores within the port."; } } } grouping passive-devices { description "Attributes applicable to passive devices."; list passive-device { key "id"; description "List of passive devices."; leaf id { type string; description "Cable identifier."; } uses nwi:basic-common-entity-attributes; leaf device-type { type identityref { base passive-device-type; } description "Type of passive device."; } leaf-list custom-tags { type string; description "Customized tags, e.g. RFID, QR code that are attached to the device."; } leaf location-ref { type nil:ni-location-ref; description "Referenced location for the passive device."; } uses passive-device-ports; } } /* Augmentation */ augment "/nwi:network-inventory" { description "Augment network inventory with information for optical cables and passive devices."; uses cables; uses passive-devices; } } ]]>

Operational Considerations TBC per .

Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The NETCONF access control model 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. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. Considerations in Section 8 of are also applicable to their subtrees in the module defined in this document. 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. Considerations in Section 8 of are also applicable to their subtrees in the module defined in this document.

IANA Considerations IANA is requested to register the following URI in the "ns" registry within the "IETF XML Registry" group : IANA is requested to register the following YANG module in the "YANG Module Names" registry within the "YANG Parameters" registry group.

References Normative References Huawei Technologies Nokia Vodafone FiberCop Cisco This document defines a base YANG data model for reporting network inventory. The scope of this base model is set to be application- and technology-agnostic. The base data model can be augmented with application- and technology-specific details. This document defines a YANG data model for the management of hardware on a single server. Huawei Nokia Vodafone FiberCop Cisco This document defines a YANG data model for Network Inventory location (e.g., site, room, rack, geo-location data), which provides location information with different granularity levels for inventoried network elements. Accurate location information is useful for network planning, deployment, and maintenance. However, such information cannot be obtained or verified from the Network Elements themselves. This document defines a location model for network inventory that extends the base inventory with comprehensive location data. YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document obsoletes RFC 6536. This document defines a YANG data model for representing, retrieving, and manipulating Traffic Engineering (TE) Topologies. The model serves as a base model that other technology-specific TE topology models can augment. Informative References Everything OPS Cisco Old Dog Consulting Nokia Blue Fern Consulting ZTE New Protocols or Protocol Extensions are best designed with due consideration of the functionality needed to operate and manage them. Retrofitting operations and management considerations is suboptimal. The purpose of this document is to provide guidance to authors and reviewers on what operational and management aspects should be addressed when defining New Protocols or Protocol Extensions. This document obsoletes RFC 5706, replacing it completely and updating it with new operational and management techniques and mechanisms. It also introduces a requirement to include an "Operational Considerations" section in new RFCs in the IETF Stream. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]

The Complete Schema Trees This appendix presents the complete tree of the Passive Network Inventory data model. See for an explanation of the symbols used. The data type of every leaf node is shown near the right end of the corresponding line.

Tree diagram for passive network inventory

Acknowledgments TODO acknowledge.

Contributors Huawei

yuchaode@huawei.com

Highstreet

mohammad.boroon@highstreet-technologies.com

Huawei

italo.busi@huawei.com

Nokia

s.belotti.ietf@gmail.com

Nokia

swaminathan.1.s@nokia.com

Nokia

swaminathan.b@nokia.com

ETRI

byyun@etri.re.kr

China Mobile

liuyucongyjy@chinamobile.com

China Mobile

zhaoyangyjy@chinamobile.com

Radisys

Avinash.Sakalabhaktula@radisys.com