ITU-T Cloud Computing Event
Main Technical Results of
Focus Group Cloud Computing
Dr. Jamil Chawki
Vice Chair
January 9 2012
Committed to connecting the world
International
Telecommunication
Union
1
Main Focus Group Cloud results
1. Ecosystem: definition use cases & requirements
2. Functional requirements & Reference
Architecture
3. Infrastructure: network & computing
4. Security
5. Resource management
Input documents
Documents
500
450
400
350
300
250
200
150
100
50
0
Output documents
468
468 Input
documents
26
9
29 13
45
8
92
65
50
10
12
84
16
88
77
10
10
FG Cloud#1 FG Cloud#2 FG Cloud#3 FG Cloud#4 FG Cloud#5 FG Cloud#6 FG Cloud#7 FG Cloud#8
Total
Committed to connecting the world
2
1
Cloud ecosystem: definitions,
taxonomies, use cases & high
level requirements
Committed to connecting the world
3
Cloud ecosystem: definitions, taxonomies,
use cases & high level requirements
1. Cloud Computing related definitions & taxonomies: 5 Cloud
2.
3.
4.
5.
service categories (SaaS, CaaS, PaaS, IaaS, NaaS) with 2
new categories for Communication (real time) and network
(transport & inter-cloud)
Cloud ecosystem actors (provider, partner & user) and roles
Inter-cloud Scenarios : Peering, Federation & Service Broker
Telecommunication centric use cases: Service Delivery
Platform, Desktop as a Service, Call center, Cloud migration
and portability, Inter-cloud (SLA, performance, availability...)
High level requirements:
 For cloud infrastructure accessibility, massive data
processing, portability, responsiveness…
 For cloud services: SLA support, management, Inter-cloud
Committed to connecting the world
4
Cloud Ecosystem
Three actors playing different roles:
1. Cloud Service Provider CSP: XaaS Provider, Inter-Cloud…
2. Cloud Service User CSU: Consumer, Enterprise…
3. Cloud Service Partner CSN: Application Developer,
Integrator…
CSN 1
(application developer)
CSN 2 (content provider)
CSP 1
(SaaS/PaaS/IaaS/CaaS/
NaaS provider and
Inter-Cloud)
CSU1 (enterprise)
CSN 3
CSP 2
(Inter-Cloud)
CSP 3
(SaaS/PaaS/IaaS/
CaaS/NaaS provider
and Inter-Cloud)
CSU2 (consumer)
Committed to connecting the world
5
Inter-cloud Scenarios
Peering
Cloud Service
provider A
Federation
Cloud Service
provider B
API(B)
Cloud Service
provider A
Common API
Cloud Service
provider B
API(A)
Common API
API(X): API provided by Cloud Service provider X
Common API
Cloud Service
provider C
Service Broker
Committed to connecting the world
6
2
Functional Requirements &
Reference Architecture
Committed to connecting the world
7
Functional Requirements & Reference
Architecture
 Cloud Architecture Requirements: integration with
Network resources, Automation & Mobility, Multiple
Deployment model, Security and Audit…
 Introducing 4 Layers Cloud architecture: User, Access,
Services, Resources & Network
 Functional blocks of cloud computing architecture: First
cloud ICT architecture
 Endpoint Function
 Inter-Cloud Function: Peering, Federation & Brokering
 Service Orchestration (Business Process)
 Resources Orchestration
 Examples for DaaS, SDPaaS, User access,
Multimedia/Internet TV, Inter-Cloud…
Committed to connecting the world
8
Cloud Functional Architecture
First Cloud ICT architecture
User
Layer
End-User
Function
Partner
Function
Endpoint
Function
Access
Layer
Administrator
Function
Inter Cloud
Function
Operational
Management
Function
SaaS / CaaS
Services
Layer
PaaS
Service
Orchestration
IaaS
CrossLayer
Functions
NaaS
Cloud
Performance
Function
Security &
Privacy
Function
Resource Orchestration
Resources
&
Network
Layer
Pooling &
Virtualization
Physical
Resources
VN
VS
Intra Cloud
Network
VM
Storage
Software &
Platform Assets
Computing
Virtual Path
Virtual Circuit
Core
Transport
Network
Inter Cloud
Network
Committed to connecting the world
9
Main Cloud Layers and functions
 Access layer:
 Endpoint : controls cloud traffic and improves cloud
service delivery
 Inter Cloud: addresses delivering any cloud service
across two or more CSPs
 Services layer:
 Service Orchestration: is the process of deploying and
managing “Cloud Services“
 Cloud Services: provides instances (and composition)
of CaaS, SaaS, PaaS, IaaS & NaaS
 Resources & Network Layer:
 Resource orchestration
 Pooling Virtualization: compute, storage, network,
software & platform assets
 Physical resources
Committed to connecting the world
10
3
Cloud Infrastructure:
Requirements and
framework architecture
Committed to connecting the world
11
Cloud Infrastructure: Requirements
and framework architecture
 General requirements, Framework &
Network Model for cloud infrastructure
 Functional requirements for
 computing capability
 cloud network
 storage capability (& architecture)
 resource management
 Power management
Committed to connecting the world
12
Network Model for cloud infrastructure
2-Intra-Cloud
1-Core Transport
3-Inter-Cloud
2-Intra-Cloud
Committed to connecting the world
13
Functional requirements for
Cloud Network
Scalability
Performance
Agility and flexibility
Convergence of Data & Storage Networks
Network interface card virtualization
Dynamic & Seamless migration of Virtual
machine
 IPv4/IPv6 Support






Committed to connecting the world
14
Functional requirements for
Computing & Storage capability
Computing
 CPU virtualization &






scheduling
Memory virtualization
I/O Device virtualization
Duplication of VM
Static migration of VM
Multi-tenancy Self-Service
Automation
Storage
•Storage space
•Storage Interface
•Management
•Availability
•Scale-out storage
Committed to connecting the world
15
4
Cloud Security: Threats &
Requirements
Committed to connecting the world
16
Cloud Security: Threats & Requirements
 Threats for Cloud Computing Security are
identified for :
Cloud Service User and
Cloud Service Provider
 Requirements for Cloud Computing are
captured:
 Cloud Service User and
Cloud Service Provider
 Study Subjects Proposal
Committed to connecting the world
17
Threats for Cloud Computing
Users
 Responsibility Ambiguity
 Loss of Governance
 Loss of Trust
 Service Provider Lock-in
 Cloud Service User
Remote Access
 Lack of Information/Asset
Management
 Data loss and leakage
 Loss of Account/Service
management
Providers
•Responsibility Ambiguity
•Protection Inconsistency
•Evolutional Risks
•Business Discontinuity
•Supplier Lock-in
•License Risks
•Bylaw Conflict
•Bad Integration
•Unsecure Administration API
•Shared Environment
•Hypervisor Isolation Failure
•Service Unavailability
•Data Unreliability
•Abuse Right
Committed to connecting the world
18
Requirements for Cloud Computing
Users
 Method to trust cloud
providers' security level
 Information/asset
management.
 Confidentiality/integrity
of data
 Proper account/identity
management
 Service interoperability,
portability & reversibility
 Interoperable Service
interface & virtualization
mechanisms
 Secure Virtual Machine
Providers
• Hypervisor Protection
• Storage & Network Isolation
• Protection for Network Elasticity
• Interoperability
• Identity Management
• Disaster Recovery
• Data Traceability
• Secure VM Migration
• Trusted Compute Pools
• Different Security Models
• Multi-tenancy
• IP, License management &
Jurisdictional Compliance
• Segregation of Role, Resource &
responsibility
• Information & Data Quality
Assurance
Committed to connecting the world
19
Security Study Subjects proposal











Security architecture/model and framework
Security management and audit technology
Business Continuity Planning /disaster recovery
Storage security
Data and privacy protection
Account/identity management
Network monitoring and incident response
Network security management
Interoperability and Portability Security
Virtualization Security
Obligatory predicates
Committed to connecting the world
20
5
Cloud Resource Management
Gap Analysis
Committed to connecting the world
21
Cloud Resource Management:
Requirements & Gap Analysis
 Overview of Cloud Resource Management SDO




activities
Cloud Resource management Capabilities
Vision for ITU-T
 To develop service delivery management
frameworks, architecture, design patterns
and best practices
 To provide guidance to build manageable
end-to-end service mashups
Gap analysis
Future study areas on Cloud Computing
resource management
Committed to connecting the world
22
Cloud Computing Resource
Management capabilities
 Resource and service status monitoring
 Resource performance estimation and




selection
Resource discovery and reservation
Resource setup and service activation
Alteration and reversion of the user
access to the cloud service
Releasing resources
 Inter-Cloud Resource Management
Committed to connecting the world
23
Resource Management Study
Subjects proposal
 To build and maintain dynamically reconfigure multi-





cloud based OSS/BSS systems
To develop best practices, architectural guidelines and
frameworks to further expose diverse, application
defined service / resource management interfaces
To provide flexible cloud application to expose desired
service / resource management interfaces
To use cloud computing environment to enable flexible,
end-to-end management of composed services
To take into consideration the Service Creation Lifecycle
Management
To audit the security controls and implementation
Committed to connecting the world
24
Focus Group Cloud Computing
TOR
&
Results

Leverage expertise within the ITUT in building telecom networks to
take advantage of cloud concepts 
and capabilities
Proposal of ICT Cloud Ecosystem with 3
main players “Users, Partners & Provider”

Terminology and taxonomy and to 
develop new definition when
necessary
Introducing Cloud services definitions with
2 new telecom related categories CaaS
(Communication) & NaaS (Network)

Analysis of
telecommunication/ICT
networking requirements
functions and capabilities to
support cloud computing
services/applications


Use cases of services and
reference models for
telecommunication/ICT to support
cloud computing
Finalization of first 4 layers Telecom/ICT
Cloud Functional Architecture (User,
Access, Service & Resource & Network)

Requirements for Cloud infrastructure
including network compute and storage

Threats & Requirements for Security

Requirements for Resource Management

Exploring Telecom /ICT use cases for
Service Delivery Platform as a Service,
Desktop as a Service, Call center, Cloud
migration and portability, Inter-cloud
(Peering, Federation & Broker)
Committed to connecting the world
25
Thank You
Committed to connecting the world