Internet Engineering Task Force B. Khasnabish
Internet-Draft ZTE USA, Inc.
Intended status: Informational C. JunSheng
Expires: June 30, 2013 ZTE
Y. Meng
.
December 27, 2012
Cloud Industry Workitem Survey Results
draft-khasnabish-cloud-industry-workitems-survey-04.txt
Abstract
This document presents a survey of the industry work items related to
cloud computing, networking and services. At the end of this survey
a section on gaps related to work items is presented.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 30, 2013.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Khasnabish, et al. Expires June 30, 2013 [Page 1]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Work Items Explanation . . . . . . . . . . . . . . . . . . . . 6
4. Survey of Cloud Industries . . . . . . . . . . . . . . . . . . 11
5. Standardization Consideration . . . . . . . . . . . . . . . . 12
5.1. WorkItem A: Cloud Client-side API . . . . . . . . . . . . 12
5.2. WorkItem B: Cloud Server-side API . . . . . . . . . . . . 12
5.3. WorkItem C: Clouds OS layer . . . . . . . . . . . . . . . 12
5.4. WorkItem D: Cloud Service and Resources Logging,
Auditing, and Reporting . . . . . . . . . . . . . . . . . 12
5.5. WorkItem E: Cloud Service Performance and Security
Monitoring and Reporting . . . . . . . . . . . . . . . . . 13
5.6. WorkItem F: Cloud Resources Definition and Description . . 13
5.7. WorkItem G: Cloud Resources and VM Mobility across
Private-Private, Private-Public, etc. . . . . . . . . . . 14
5.8. WorkItem H: Multi-Domain Distributed Scaling and
Filing of Information/Resources . . . . . . . . . . . . . 14
5.9. WorkItem I: Provisioning of advanced services over a
variety of Clouds . . . . . . . . . . . . . . . . . . . . 14
5.10. WorkItem J: Support and maintenance of advanced
services over a variety of Clouds . . . . . . . . . . . . 15
5.11. WorkItem K: Address resolution and extension . . . . . . . 15
5.12. WorkItem L: Risk, Resiliency, and SLA (RRS) for
Components and Apps/Services (End-to-End) . . . . . . . . 15
5.13. WorkItem M: Seamless support of Multi-tenancy . . . . . . 15
5.14. WorkItem N: Cloud/Cross-Domain Identification
Management . . . . . . . . . . . . . . . . . . . . . . . . 15
5.15. WorkItem O: Network Virtualization Overlays . . . . . . . 15
5.16. WorkItem P: Software Defined/Driven Networking (SDN) . . . 16
6. Summary and Analysis . . . . . . . . . . . . . . . . . . . . . 17
7. Security Considerations . . . . . . . . . . . . . . . . . . . 18
Khasnabish, et al. Expires June 30, 2013 [Page 2]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
8. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 19
9. Appendix A: Cloud Computing Vendor List. . . . . . . . . . . . 20
10. Appendix B: Survey of Cloud SDOs . . . . . . . . . . . . . . . 22
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
12. Normative references . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26
Khasnabish, et al. Expires June 30, 2013 [Page 3]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
1. Introduction
This draft presents a survey of the industry work items related to
cloud activities. By conducting a comprehensive survey, work items
in cloud standards can be determined. This will allow us to
determine the IETF work that would be required to address the work
items. Once these IETF work have been completed, seamless
interoperability of cloud services can be realized.
Khasnabish, et al. Expires June 30, 2013 [Page 4]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
2. Terminology
Cloud-based systems are conveniently-connected modular blocks of
resources
o Both physical and virtual modularizations of resources are
possible
o For this discussion, the resources include computing (CPU),
communications (network), memory, storage, management, database,
software, applications, services, interconnectivity, etc.
o The objective is to make the resources available ubiquitously for
mission-specific applications and services. These resources are
used to support the ultimate level of privacy/security,
scalability and reliability cost-effectively and without the
headache of owning and maintaining the infrastructure.
Clouds Discussion Archive:
http://www.ietf.org/mail-archive/web/clouds/current/maillist.html
IETF WiKi Website for slides from Clouds bar BoFs:
http://trac.tools.ietf.org/area/app/trac/wiki/Clouds
Service over Cloud
o Utilize (stitch, weave, embroider, ...) the resources from Cloud
to provision, create, deliver, and maintain an End-to-End Service
o Use the service only when you Need it
o Pay only for the time duration and type of use of service (incl.
the costs for resources used)
Khasnabish, et al. Expires June 30, 2013 [Page 5]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
3. Work Items Explanation
WorkItem A: Cloud Client-side API.
o Cloud Client-side API is the interface that is used to execute
assigned functions (such as login, get data, post change) at
client-side. In cloud environment, some clients need invoke the
API to process the returned results or to handle commands (such as
monitoring or logging request) from the server.
o Cloud Client-side API can also be utilized by users and 3-party
developers before accessing resources of the Cloud Computing
Platforms, such as making resource requests to the server.
o It is required to avoid the use of proprietary API in order to
support the interoperability.
WorkItem B: Cloud Server-side API.
o Cloud Server-side API is the interface that allows developers to
build their own unique solutions on top of Cloud Computing
Platform, to access the capabilities of the platform.
o In cloud environment, the API can be used to authenticate &
authorize login request, check resource status, allocate requisite
resources, configure virtual machines, etc.
o It is required to avoid the use of proprietary API in order to
support the interoperability.
WorkItem C: Clouds OS layer (what are added to the VM layer to hide
the complexity)
o Clouds OS layer refers to an Operating System (OS) or Hypervisor
and Virtual Machines (VM) that resides above the physical resource
layer to manage the physical resources.
o In OS-level virtualization, the kernel of an operating system
allows for multiple isolated user-space instances, instead of just
one. In addition to isolation mechanisms, the kernel often
provides resource management features to limit the impact of one
instance's activities on the other instances. In order to realize
the above features, sometimes, the OS needs to be modified.
Currently there are many virtualization technologies.
* Full virtualization: In full virtualization, the virtual
machine simulates enough hardware to allow an unmodified
"guest" OS to be run in isolation.
Khasnabish, et al. Expires June 30, 2013 [Page 6]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
* Hardware-assisted virtualization: In hardware-assisted
virtualization, the hardware provides architectural support
that facilitates building a virtual machine monitor and allows
guest OSes to be run in isolation.
* Partial virtualization: In partial virtualization, including
address space virtualization, the virtual machine simulates
multiple instances of much of an underlying hardware
environment, particularly address spaces.
* Paravirtualization: In paravirtualization, the virtual machine
does not necessarily simulate hardware, but instead (or in
addition) offers a special API that can only be used by
modifying the "guest" OS.
* Operating system-level virtualization: In operating system-
level virtualization, a physical server is virtualized at the
operating system level, enabling multiple isolated and secure
virtualized servers to run on a single physical server. The
"guest" OS environments share the same OS as the host system.
o It is required to investigate what needs to be added to the VM
layer in order to hide the complexity of the cloud systems.
WorkItem D: Cloud Service and Resources Logging, Auditing, and
Reporting
o Cloud Services are business or consumer products, services and
solutions that are delivered in cloud computing environment.
Three types of services have gained popularity, and each of them
addresses the standard definitions of cloud computing in their own
way.
* IaaS - Infrastructure as a Service: The concept of IaaS is to
provide the infrastructure to application's need, as a service.
You will usually pay an hourly or monthly fee for the
infrastructure you choose to use.
* PaaS - Platform as a Service: PaaS provides platform
environment that is required to run an application. All you
need to care about is the application itself and the model you
describe that tells the vendor how the application should be
run.
* SaaS - Software as a Service: SaaS sometimes referred to as
"on-demand software", is a software delivery model in which
software and its associated data are hosted centrally and are
typically accessed by users using a thin client, normally using
Khasnabish, et al. Expires June 30, 2013 [Page 7]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
a web browser over the Internet.
o Cloud Logging, Auditing, and Reporting are methods used to trace
cloud service, resource activities and status.
* Cloud logging means that an open and extensible log format to
be used by any cloud entity or cloud application to log and
trace users or system activities that occur in the cloud.
* Auditing and Reporting means that specific information can be
got from the Cloud system for diagnosis fault or analysis
system behavior.
WorkItem E: Cloud Service Performance and Security Monitoring and
Reporting
o Cloud Service Performance monitoring means the ability to monitor
the Quality of Services (QoS) services delivered over virtualized
systems. In order to guarantee the service performance, such
methods as resource scheduling, load balancing, simplicity system
configuring and application loading, and performance monitoring
need to be undertaken.
o Cloud Security Monitoring and Reporting aims to provide
interactive information and automated reports on resource
utilization, including real-time monitoring of services/
applications user accounts, files, access, intrusions, etc.
o The cloud security monitoring and reporting process helps
decision-makers and managers determine and understand the security
risks. Monitoring the system periodically and instantly helps
determine potential problems in early stages and can be used to
evaluate the effectiveness of the security control mechanisms.
WorkItem F: Cloud Resources Definition and Description
o Cloud Resources Definition and Description is the mechanism that
can be used as a general method for conceptual description or
modeling of information that is implemented in virtualized
resources, using a variety of syntax formats.
o Different types of virtualization platforms use different
definitions of resources. For each kind of resources, there may
be different types of attributes.
WorkItem G: Cloud Resources and VM Mobility across different
technology domains.
Khasnabish, et al. Expires June 30, 2013 [Page 8]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
o There are many reasons that require the cloud platform supports VM
mobility across clouds, such as load balancing, SLA requirements,
avoiding service interruption, etc. VM mobility can be divided
into 'cold' mobility which will interrupt the services/sessions in
progress, and 'hot' mobility which will not interrupt the ongoing
services/sessions. The resources need to be reserved in advance
on the target cloud domain during migration of the VM.
WorkItem H: Multi-Domain Distributed Scaling and Filing of
Information / Resources
o Multi-Domain Distributed Scaling means that the services are
distributed among multiple domains and can be scaled on on-demand
basis. The information/resources (such as billing, logging
record) are filed among multiple domains in the cloud.
WorkItem I: Provisioning of advanced services (voice, video,
streaming media, gaming, etc.) over a variety of cloud domains.
o This workitem is to investigate whether the cloud has the
capability to support the delivery of advanced services over a
variety of cloud domains. The applications are deployed over
clouds based on service provider's requirements, such as ensuring
service rubust, load balancing, service provision exceeding cloud
coverage, etc. The cloud which manages the advanced services over
other clouds (for example Service Management Cloud) is responsible
for the lifecycle of advanced services, and the cloud which is
selected by the Service Management Cloud to deploy advanced
services (for example Service Deployment Cloud) is responsible for
resource allocation and service maintenance.
WorkItem J: Support and maintenance of advanced services over a
variety of Clouds
o This workitem is to investigate whether the Cloud (as role of
Service Deployment Cloud) can provide support and maintenance of
advanced services deployed by other Service Management Cloud.
WorkItem K: Address resolution and extension (e.g., VPN extension to
private Clouds)
o ARP extension provides a scalable address resolution protocol to
map virtual host's identity to physical IP/MAC addresses in order
to solve client routing among multiple subnetworks.
o Service providers also have the requirements to support cloud
services interworking with the existing MPLS-based L2/L3 VPN
services. It is required to maintain separation of the enterprise
Khasnabish, et al. Expires June 30, 2013 [Page 9]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
traffic, and customer data, and queries.
WorkItem L: Risk, Resiliency, and SLA (RRS): Risk-tolerance, MTTF,
MTTR, etc. for cloud components and Apps/Services (on an end-to-end
basis)
o This workitem is related to ensuring long-term sustainability of
the application/service in cloud system. This includes risk-
tolerance, disaster recovery, and SLA maintenance of the system.
The measuring methods as MTTF and MTTR need to be considered.
WorkItem M: Seamless support of Multi-tenancy (domestic/International
customers)
o In a multi-tenant environment, multiple customers share the same
resources with applications running on the same operating system,
on the same hardware, with the same data-storage mechanism.
Therefore it is required to satisfy different requirements of the
customers such as security, data model, access control, workflow,
etc.
o This workitem is to investigate whether multi-tenancy can be
seamlessly supported. Because of the additional customization
complexity, and the need to maintain per-tenant metadata, multi-
tenancy applications may require a different development effort.
Khasnabish, et al. Expires June 30, 2013 [Page 10]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
4. Survey of Cloud Industries
A survey of Clouds Industry Companies is available in section 4 of
the earlier version of this draft, please see the following link:
http://tools.ietf.org/id/
draft-khasnabish-cloud-industry-workitems-survey-00.txt.
Khasnabish, et al. Expires June 30, 2013 [Page 11]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
5. Standardization Consideration
5.1. WorkItem A: Cloud Client-side API
In Virtual Desktop Infrastucture (VDI) technology, the interaction
between the client device and the hosted server needs standardized,
that is, the Client-Side API needs to be specified.
5.2. WorkItem B: Cloud Server-side API
There are many cloud resource management APIs currently in effect,
such as AWS EC2, GoGrid, Rackspace and Sun Cloud. They use different
protocols (such as SOAP, WS-*, REST, plain HTTP) and are applied in
different scenarios.
In IETF, we need converged resources provided by different platforms,
and also provide unified interface among resource client, resource
manager and resource provider. So, it is necessary to standardize
the Cloud Server-Side API to simplify system management.
The results of initial work in this area can be found in [VRM].
5.3. WorkItem C: Clouds OS layer
Cloud resource management is based on the virtual resource platforms
provided by different vendors, converges the different kinds of
virtual resources as a whole and provides resource management and
control functions according to applications/services requirements.
The cloud work in IETF does not touch the implementation of the
virtual resource layer, so it is not necessary to standardize the
Cloud OS layer. But if a virtualization platform provides resource
to the cloud, it'll support the unified interface.
5.4. WorkItem D: Cloud Service and Resources Logging, Auditing, and
Reporting
An open and extensible logging/auditing format needs to be specified
for use by any cloud entity or cloud application to log and trace
activities that occur in the cloud. It is equally applicable for
cloud infrastructure (IaaS), platform (PaaS), and application (SaaS)
services.
Standardized Log format is required for auditing and verification
purposes which are important parts of management and operations.
The results of initial work in this area can be found in [Cloud Log],
[VOCS], and [CSB].
Khasnabish, et al. Expires June 30, 2013 [Page 12]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
5.5. WorkItem E: Cloud Service Performance and Security Monitoring and
Reporting
Standards of Cloud Security Framework (CSF) are needed for the Cloud
Service Providers (CSP), which would enable CSP organizations and
development organizations using their service to practice safe
security techniques for their applications and intra & inter CSP
information exchange.
5.6. WorkItem F: Cloud Resources Definition and Description
In current Cloud and Virtual Data Centre (VDC) environment, the
manageable virtualized resources are supplied by different vendor's
hypervisors (such as VMware ESX/ESXi, Citrix Xen Server, Oracle VM,
Microsoft Hyper-V, etc.). The Resource Management Platform (RMP)
need support variety of proprietary or open APIs provided by
hypervisor vendors to access, manage and integrate the exposed
different types of resources. In order to decouple RMP from any
particular hypervisor, a unified cloud resource model is needed to
define and describe the resources the platform converged.
o Applications/Services running on a hypervisor may gain better
support or performance by running on the other different one.
o The existing hypervisor can't satisfy the needed features or
functions, such as disaster recovery, business continuity,
security, reporting, etc.
o New system requirements or virtual machine demands would be served
more effectively or cheaper on a different hypervisor.
o Elimination of hypervisor vendor lock-in and avoidance of service
unavailability when fail to upgrade or patch some same type of
hypervisor the service deployed on.
o Multiple choices can be offered to service providers or customers
to select their preferred platforms.
With multiple hypervisors providing resources to the cloud, it is
difficult for Cloud RMP to manage and coordinate these resources.
o Different hypervisors provide different VRM APIs and use different
transport protocols.
o Different virtualization platforms provide different views of
hierarchical resources.
Khasnabish, et al. Expires June 30, 2013 [Page 13]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
o Different hypervisors have different ways to describe resource
attributes.
When the cloud RMP consists of resources provided by multiple
vendor's hypervisors, it need support different kinds of APIs with
their transport protocols utilized by different vendors hypervisors.
Moreover, when a new hypervisor appears or existing hypervisor
upgrades, the cloud RMP need change accordingly to adapt the varies.
It'll complicate the implementation of the cloud RMP.
To solve these problems and simplify operations on the virtual
resource management, the following two requirements must be met.
o The API needs to be hypervisor-agnostic. It can be leveraged by
cloud RMP to form a unified resource pool.
o The API needs to be simple and lightweight. It can be implemented
with the popular technologies, such as HTTP, URI, XML, JSON, etc.
The results of initial work in this area can be found in [VRM] and
[VNet Model].
5.7. WorkItem G: Cloud Resources and VM Mobility across Private-
Private, Private-Public, etc.
Virtual switches on server virtualization platforms cause a problem
in managing data center networks containing several hundred switches.
Accordingly, a standardized management information model for the
network structure of data center networks containing virtual switches
is needed.
The results of initial work in this area can be found in [Cloud
Service Mobility] and [Cloud Workload Mobility].
5.8. WorkItem H: Multi-Domain Distributed Scaling and Filing of
Information/Resources
Current there is no draft available to address this work item.
5.9. WorkItem I: Provisioning of advanced services over a variety of
Clouds
Cloud Service Broker (CSB) entity provides brokering service between
different Cloud Service Providers. Operations and management aspects
of brokering need to be discussed and standardized.
The results of initial work in this area can be found in [CSB].
Khasnabish, et al. Expires June 30, 2013 [Page 14]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
5.10. WorkItem J: Support and maintenance of advanced services over a
variety of Clouds
Clouds Network Portability (CNP) mainly describes several possible
operation methods to provide network portability of virtual machine
migration in cloud systems.
The results of initial work in this area can be found in [CNP].
5.11. WorkItem K: Address resolution and extension
Virtual hosts come and go, but each service provider!_s IP/MAC
address space is no unlimited. Therefore, it is important to have a
scalable Address Resolution protocol to map virtual host!_s identity
to physical IP/MAC addresses.
The results of initial work in this area can be found in the drafts
of the ARMD WG (http://datatracker.ietf.org/wg/armd/).
5.12. WorkItem L: Risk, Resiliency, and SLA (RRS) for Components and
Apps/Services (End-to-End)
Current there is no draft available to address this work item.
5.13. WorkItem M: Seamless support of Multi-tenancy
Multi-tenancy helps to put multiple customers on the same physical
infrastructure, share the same application.
The results of initial work in this area can be found in [Seamless
Cloud], [VEPC].
5.14. WorkItem N: Cloud/Cross-Domain Identification Management
The objecive of this work is to develop interoperable methods for
creating, reading, searching, modifying, and deleting user identities
and identity-related objects across different administrative domains.
The results of initial work in this area can be found in [SCIM].
5.15. WorkItem O: Network Virtualization Overlays
Network virtualization overlays need to develop framework, control
plane, data plane, security, and operational requirements for
interconnecting multi-tenant Data centers that use virtual hosts/
machines (VH/M) using network layer (layer-3) technologies.
The key requirements include (a) traffic isolation, (b) address
Khasnabish, et al. Expires June 30, 2013 [Page 15]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
independence, (C) seamless migration of VH/M within and across Data
centers, etc.
The results of initial work in this area can be found in [NVO3].
5.16. WorkItem P: Software Defined/Driven Networking (SDN)
The objective of SDN is to develop open interfaces (Application
Programming Interfaces or APIs) for controlling the networking
entities that can be defined by software, thereby hiding the
complexity, limitation and technologies that are used by physical
networking entities. This allows development of customized network
based applications/services on an on-demand basis for specific time
duration.
The presentations and notes from SDN BoF/Side Meeting during IETF-82
in Taipei can be found at
http://www.ietf.org/proceedings/82/minutes/sdn.html. For further
details on this initiative that led to the BoF, please see [SDNP].
Khasnabish, et al. Expires June 30, 2013 [Page 16]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
6. Summary and Analysis
In this draft, we present a list of cloud industry work items. The
IETF drafts that are related to these work items are available in the
reference section.
Khasnabish, et al. Expires June 30, 2013 [Page 17]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
7. Security Considerations
Will be added in future, on as-needed basis.
Khasnabish, et al. Expires June 30, 2013 [Page 18]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
8. Acknowledgement
We would like to thank Ning So and Suren Karavettil for comments on
earlier versions of this draft. We invite comments, suggestions, and
feedback from other reviewers and contributors.
Khasnabish, et al. Expires June 30, 2013 [Page 19]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
9. Appendix A: Cloud Computing Vendor List.
http://virtualizationchat.com/cloud-computing-vendor-list/. This
Website documents the Type, Status and Cloud Provider of each Cloud
Industry.
3Tera:http://www.3tera.com/
Akamai:http://www.akamai.com/cloud
Amazon EC2:http://aws.amazon.com/ec2/
Dell DCS:http://www.dell.com/content/topics/global.aspx/sitelets/
solutions/cluster_grid/dcs_landingpage
Elastra:http://www.elastra.com/
Enki:http://www.enkiconsulting.net/
Enomaly:http://www.enomaly.com/
Flexiscale:http://www.flexiant.com/products/flexiscale/
Fortress ITX:http://www.fortressitx.com/
HP AiaaS:http://www.hp.com/hpinfo/newsroom/press/2008/080317xa.html
IBM:http://www.ibm.com/ibm/cloud/
Joyent:http://www.joyent.com/
Layered Technology:http://www.layeredtech.com/
Mosso/Rackspace:http://www.rackspacecloud.com/
Novell:http://www.novell.com/cloud/
Rightscale:http://www.rightscale.com/
Sun Caroline:https://www.projectcaroline.net/main/
Terremark:http://www.terremark.com/default.aspx
Adobe Air:http://www.adobe.com/products/air/
Areti Internet:http://www.alentus.co.uk/
Google Apps:http://www.google.com/apps/intl/en/business/index.html
Khasnabish, et al. Expires June 30, 2013 [Page 20]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
iCloud:http://icloud.com
SalesForce.com:http://www.salesforce.com/platform/
SAP:http://www.sap.com/usa/index.epx
Amazon S3:http://aws.amazon.com/s3/
Box-Net:http://www.box.net/
EMC:http://www.emc.com/
Mozy:http://mozy.com/home
ElasticDrive:http://www.elasticdrive.com/
JungleDisk:https://www.jungledisk.com/
Amazon SimpleDB:http://aws.amazon.com/simpledb/
Apache CouchDB:http://couchdb.apache.org/
EnterpriseDB:http://www.enterprisedb.com/
LongJump:http://www.longjump.com/
Microsoft:http://msdn.microsoft.com/en-us/windowsazure/default.aspx
Sun MySQL:http://www.mysql.com/
Appirio:http://www.appirio.com/
Cloud9Analytics:http://cloud9analytics.com/
CohesiveFT:http://www.cohesiveft.com/
MorphExchange:http://www.morphexchange.com/
Rollbase:http://www.rollbase.com/
VMWare:http://www.vmware.com/solutions/cloud-computing/
Khasnabish, et al. Expires June 30, 2013 [Page 21]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
10. Appendix B: Survey of Cloud SDOs
A survey of Cloud Standard Development Organizations (SDOs) and
Working Groups (WGs) that are focusing on cloud-based systems and
services is available in the following draft:
http://tools.ietf.org/id/draft-khasnabish-cloud-sdo-survey-03.txt.
Khasnabish, et al. Expires June 30, 2013 [Page 22]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
11. IANA Considerations
This document has no actions for IANA.
Khasnabish, et al. Expires June 30, 2013 [Page 23]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
12. Normative references
[CNP] Shima, K.,
"draft-shima-clouds-net-portability-reqs-and-models",
September 2011.
[CSB] Weixiang, S., "draft-shao-opsawg-cloud-service-broker-03",
March 2012.
[Cloud Framework]
Khasnabish, B.,
"draft-khasnabish-cloud-reference-framework-03",
June 2012.
[Cloud Log]
Golovinsky, G.,
"draft-golovinsky-cloud-services-log-format-02",
March 2012.
[Cloud ServiceMobility]
Yokota, H., "draft-yokota-cloud-service-mobility-01",
August 2011.
[Cloud WorkloadMobility]
Iyer, S., "draft-rfc-workload-mobility-iyer-00",
August 2011.
[NVO3] IETF, RTG., "Network Virtualization
Overlays(http://datatracker.ietf.org/wg/nvo3/charter/)",
September 2011.
[RFC2119] IETF, "Key words for use in RFCs to Indicate Requirement
Levels", March 1997.
[SCIM] IETF, APPS., "System for Cross-domain Identity
Management(http://datatracker.ietf.org/wg/scim/charter/)",
January 2012.
[SDNP] Pan, P., "Software Driven Network Protocol
(http://lucidvision.com/pipermail/sdnp/)", July 2011.
[Seamless Cloud]
Hasan, M., "draft-rfc-seamless-Cloud-masum-01",
August 2011.
[VEPC] So, Ning., "draft-so-vepc-00", November 2011.
[VNet Model]
Khasnabish, et al. Expires June 30, 2013 [Page 24]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
Okita, H., "draft-okita-ops-vnetmodel-04", September 2011.
[VOCS] So, Ning., "draft-so-vpn-o-cs-00", March 2011.
[VRM] Junsheng, C.,
"draft-junsheng-virtual-resource-management-00",
September 2011.
Khasnabish, et al. Expires June 30, 2013 [Page 25]
Internet-Draft Cloud Industry Workitem Survey Results December 2012
Authors' Addresses
Bhumip Khasnabish
ZTE USA, Inc.
55 Madison Avenue, Suite 160
Morristown, NJ 07960
USA
Phone: +001-781-752-8003
Email: vumip1@gmail.com, bhumip.khasnabish@zteusa.com
Chu JunSheng
ZTE
No.50 Ruanjian Dadao Road, Yuhuatai District
Nanjing
China
Phone: +86-25-8801-4630
Email: chu.junsheng@zte.com.cn
Meng Yu
.
Nanjing
China
Phone:
Email: zjumengyu@hotmail.com
Khasnabish, et al. Expires June 30, 2013 [Page 26]