Page 641 - Cloud computing: From paradigm to operation

XaaS 3

Figure
(optional)

Pre-conditions – CSP's IP carrier network support overlay network mechnism.
(optional)
Post-conditions – CSC's VMs that run in different CSP's data centres can communicate with each other.
(optional)

Derived – Logically isolated network partition (refer to clause 9.12)
requirements – Overlay network mechanism (refer to clause 9.13)

II.4.2.7 NaaS connectivity use case for private IP addresses and VPNs

Title NaaS connectivity use case for private IP addresses and VPNs
Description Case I: Public cloud site multi-tenant VPN gateway (GW) with overlapping private IP
addresses
Multi-tenant VPN GW in a public cloud site is shared by CSC-I-A and CSC-I-B. Both of them
are interested to use the same private IP address pool for their end points.
Both of CSCs are connected to the public cloud VPN GW through a given public IP address
of it. The cloud VPN GW should be able to switch the traffic from each CSC to a proper
subnet.
Case II: Interworking support for different types of VPNs
CSC-II has site-to-site proprietary MPLS-VPN connection between its headquarter (HQ) and
private data centre. According to the company progress, CSC-II is interested to establish
new site-to-site and site-to-client secure VPN connections (e.g., IP security (IPsec) VPN and
secure socket layer (SSL) VPN). New VPN connections are planned between their globally
distributed branch offices and mobile users, while keeping the CSC-II existing VPN
investments. NaaS CSP should be able to provide interworking between the CSC owned
existing VPN and different types of new VPNs.
Case III: On-demand network support for the distributed end points
CSC-III requires a solution of delivering reliable, predictable and on-demand network
connections for all their locations. This service should be able to be changed dynamically
according to the CSC-III's needs. The CSC-III is interested in elastic request parameters for
connectivity to their location over the existing links. The connectivity should be established
to one or more of the NaaS CSP's points of presence (PoPs) with minimum efforts for
deploying additional equipment.
Roles CSP, CSC

633