Original text:
<del> Digital Map: Concept, Requirements, and Use Cases draft-ietf-nmop-digital-map-concept-latest </del>  Abstract <del> This document defines the concept of Digital Map, and identifies a set of Digital Map requirements and use cases. </del>  The document intends to be used as a reference for the assessment <del> effort of the various topology modules to meet Digital Map requirements. </del>  1. <del> Digital Map is a data model that provides a view of the operator's networks and services, including how it is connected to other models/ data (e.g. inventory, observability sources, and operational knowledge).  It specifically provides an approach to model multi- layered topology and appropriate mechanism to navigate amongs layers and correlate between them.  This includes layers from physical topology to service topology.  This model is applicable to multiple domains (access, core, data centers, etc.) and technologies (Optical, IP, etc.). The Digital Map modelling defines the core topological entities (network, node, link, and interface) at each layer, their role in the network topology, core topological properties, and topological relationships both inside each layer and between the layers.  It also defines how to access other external models from the topology. The Digital Map model is a topological model that is linked to the other functional models and connects them all: configuration, maintenance, assurance (KPIs, status, health, and symptoms), Traffic- Engineering (TE), different behaviors and actions, simulation, emulation, mathematical abstractions, AI algorithms, etc.  These other models exist outside of the digital map and are not defined during digital map modelling. The Digital Map data consists of virtual instances of network and service topologies at different layers.  The Digital Map provides access to this data via standard APIs for both read and write operations (write operations for offline simulations), with query capabilities and links to other YANG modules (e.g., Service Assurance for Intent-based Networking (SAIN) RFC9417, Service Attachement Points (SAPs) RFC9408, Inventory I-D.ietf-ivy-network-inventory-yang, and non-YANG models. </del>  2.

Reviewer comments:
Added Service & Infrastructure Maps (SIMAP) terminology Updated inventory use case to mention passive inventory Added requirements REQ-PASSIVE-TOPO: to include passive topology based on input from Brad Peters

Revised text:
 <ins> SIMAP: Concept, Requirements, and Use Cases draft-ietf-nmop-simap-concept-latest </ins> Abstract  <ins> This document defines the concept of Service & Infrastructure Maps (SIMAP), and identifies a set of SIMAP requirements and use cases. </ins> The document intends to be used as a reference for the assessment  <ins> effort of the various topology modules to meet SIMAP requirements. </ins> 1.  <ins> Service & Infrastructure Maps (SIMAP) is a data model that provides a view of the operator's networks and services, including how it is connected to other models/data (e.g. inventory, observability sources, and operational knowledge).  It specifically provides an approach to model multi-layered topology and appropriate mechanism to navigate amongs layers and correlate between them.  This includes layers from physical topology to service topology.  This model is applicable to multiple domains (access, core, data centers, etc.) and technologies (Optical, IP, etc.). The SIMAP modelling defines the core topological entities (network, node, link, and interface) at each layer, their role in the network topology, core topological properties, and topological relationships both inside each layer and between the layers.  It also defines how to access other external models from the topology. The SIMAP model is a topological model that is linked to the other functional models and connects them all: configuration, maintenance, assurance (KPIs, status, health, and symptoms), Traffic-Engineering (TE), different behaviors and actions, simulation, emulation, mathematical abstractions, AI algorithms, etc.  These other models exist outside of the SIMAP and are not defined during SIMAP modelling. The SIMAP data consists of virtual instances of network and service topologies at different layers.  The SIMAP provides access to this data via standard APIs for both read and write operations (write operations for offline simulations), with query capabilities and links to other YANG modules (e.g., Service Assurance for Intent-based Networking (SAIN) RFC9417, Service Attachement Points (SAPs) RFC9408, Inventory I-D.ietf-ivy-network-inventory-yang, and non-YANG models. </ins> 2.