@@ -154,12 +154,14 @@ Network management systems (“NMS”) have been identified as “important prod
## 1.2 Products in scope
> NOTE: This section is a technical definition outside of the standards context. The definition will be later replaced with references to the official documentation when the work is done and approved.
Products in scope include products whose core purpose is to serve as a network management systems intended to manage the network devices.
This standard applies to Network management systems Products with digital elements that manage IP-connected network elements, such as servers, routers, switches, workstations, printers or mobile devices, by tracking them and controlling their network configuration.
This category includes but is not limited to end-to-end management systems and dedicated configuration management systems, such as controllers for software-defined networking.
<mark>IP-connected may exclude other means of remote management. E.g., provisining via Bluetooth is common for consumer devices. “tracking them and” would seem to exclude devices that are not ‘tracked’ (which would need to be defined). NMS’ often control more than just network configuration - e.g., MDM systems.</mark>
The IP-connection may exclude other means of remote management, such as the management provisioning via Bluetooth which is common for consumer devices. Bluetooth consumer devices are usually not managed by an NMS, however, if they are capable, a NMS management could control them too, as Bluetooth is just a communication media and can be used also for management traffic. Such, NMS’s often control more than just network configuration - e.g., MDM systems.
## 1.3 Products not in scope
@@ -235,6 +237,8 @@ For the purposes of the present document, the following abbreviations apply:
| CSP | Communication System Provider |
| SDN | Software Defined Networks |
| GUI | Graphical User Interface |
| NE | One or more connected Network Elements |
| MDM | Mobile Device Management system |
# 4 Product context
@@ -270,7 +274,7 @@ The following are products and features that are covered by separate standards:
Network management systems are often deployed <mark>in a star pattern, where all command and control functionality is focused on a centralized set of services, that are providing all required functionality</mark>.
Depending on the connected element design and degree of autonomy, the element can often operate fully without constant connectivity to an NMS. <mark>In larger network deployments, the connectivity can start to erode over time, if there is no adjustments made to the routing or other operation parameters.</mark>
Depending on the connected element design and degree of autonomy, the element can often operate fully without constant connectivity to an NMS. In larger network deployments and without adjustments in routing or other operation parameters, the connectivity to the NMS can erode over time.
@@ -284,7 +288,7 @@ NMS’ can interface with PKI and SIEM systems if it is justified by the require
The main functionality of an NMS is to interface and manage Routers and Modems.<mark>This is very restrictive as presumably MDMs, etc. are in scope?</mark>
More about assets in [Annex C.1 Assets](#c1-assets) and [Annex C.2 Data](#c11-data)
More about assets in [Annex C.1 Assets](#c1-assets) and [Annex C.2 Data](#c11-data).
