@@ -328,7 +328,7 @@ In telecom deployments of NMS it is common to provide an in-house Public Key Inf
#### 4.4.3 Alternative deployments
As the use of extremely large scale network services, or hyperscalers, becomes increasingly popular and the networked services perform an ever greater number of software functions, how we understand network structures depends on how we model their connectivity. The following use cases consider such deployment and other complex deployments primarily by focusing on two factors. These complex networks can be modeled by examining [how much RDPS](#4432-physical-network-deployment-with-rdps) is involved in the design or how the functions are [virtualised in the network](#4431-logical-network-deployment).
As the use of extremely large scale network services, or hyperscalers, becomes increasingly popular and the networked services perform an ever greater number of software functions, how we understand network structures depends on how we model their connectivity. The following two use cases in sub chapters consider such deployment and other complex deployments primarily by focusing two approaches. These complex networks can be modeled by how the functions are virtualised in the network [4.4.3.1 Logical network deployment](#4431-logical-network-deployment) or examining how much RDPS is involved in the design [4.4.3.2 Physical network deployment with RDPS](#4432-physical-network-deployment-with-rdps).
Yet, the protocols used for all network deployments remain consistent. TCP and UDP dominate the network and trasport layers in the OSI-model. DNS root servers are still trusted to point to the desired IP address and browser maintained TLS CA pools builds trust beyond that provided by the DNS.
