Page 626 - Cloud computing: From paradigm to operation

3 XaaS

8.5 Integration of software applications

– It is recommended that NaaS CSP supports integration of software applications deployed on the
NaaS platform by either the CSP or the CSC, or both, to allow building of the combined solutions.

9 Functional requirements of NaaS connectivity

This clause provides requirements of NaaS connectivity derived from the use cases described in Appendix II.

9.1 Common control mechanism for NaaS connectivity
– It is recommended that the NaaS connectivity control mechanism provided by the NaaS CSP
supports the negotiation of connectivity parameters (such as interface characteristics, connection
endpoints, IP version support, QoS, L3/L2VPN type, connectivity extension approach (e.g., clause 10
of [b-IETF RFC 4364], routing information (e.g., border gateway protocol (BGP) route target).
– It is recommended that NaaS CSP provides a common NaaS connectivity control mechanism
allowing identified NaaS connectivity to be provided in a secure and QoS guaranteed manner.
– It is recommended that the NaaS connectivity control mechanism is able to cope with potentially
different CSC identification schemes used on the NaaS CSP side and on the connected endpoint.
– NaaS CSP can optionally provide isolated connectivity for the network tenants.

9.2 Unified SLA for multiple optimized networks
– It is recommended that NaaS CSP provides network connectivity services using unified SLA for CSC's
management of multiple optimized networks in order to simplify and unify the control and
management of networks.
NOTE – This mechanism allows the CSP to create and add new features to their networks to provide high
quality services which can meet CSC's differentiated requirements.
– It is recommended that composite NaaS services policy should be expressed in the SLA.
NOTE 1 – NaaS service can be a composite service, where the service consists of more than one NaaS service.
NOTE 2 – This requirement is also applicable to the NaaS application and the NaaS platform.

9.3 Leveraging transport networks dynamically
– It is recommended that NaaS CSP leverages transport networks dynamically from multiple choices
of physical and virtual networks for the purpose of providing network connectivity services, such as
recovery, BoD, QoS guarantee, etc.
NOTE – The transport networks can be heterogeneous in terms of technology and administrative domain.

9.4 Unified network control mechanism
– It is recommended that NaaS CSP provides a unified control mechanism for the end-to-end NaaS
connectivity given to a CSC.
NOTE – NaaS connectivity could be provided either by multiple heterogeneous networks or by a network
employing one or more NaaS platforms or applications, which perform(s) network functions.

9.5 Elastic network reconfiguration
– It is recommended for the CSP to provide the elastic network reconfiguration in order to match the
computing and storage elasticity and to maintain service continuity.

9.6 Seamless and end-to-end solution of bandwidth allocation
– It is recommended that NaaS CSP provides seamless and end-to-end solution of bandwidth
allocation independent of network technology and architecture.

618