 The cloud framework is defined by the International Telecommunication Union, ITUT, in the form of Y-Series. So we wouldn't go into too much of details because these are documents after documents. But we'd quickly look at the Y-Series and we just look at some of the names as key documents. Then we'll see what are the recommendations in terms of deployments by ITUT and what are some critical cross-cutting aspects, that is, aspects which have to be taken care of and then service categories and corresponding service requirements. So what is Y-Series? After X comes Y-Series. Y-Series actually deals with general guidelines regarding the identification of infrastructure, but Y-Series is particular to cloud. The global information infrastructure, internet protocol aspects and next generation networks are all dealing with Y-Series, particularly in Y.3500 to Y.3999. Is the range of documents which are dealing with cloud essentially. So Y.3500 is a very basic document that gives the glossary or the vocabulary for cloud computing. Some key characteristics are defined and roles and activities are defined. And then Y.3501 defines the framework and the high level requirements. Let's look at some key documents. I've taken it from the ITUT documentation. So we have the X-Series I was mentioning. Recommendations for security. Security framework for cloud computing. Recommendation for security techniques. The best practice code for information security controls. Then we have already discussed 3500, 3500 and 3502 deals with the reference architecture. 3510 is the infrastructure requirement for cloud computing. Then for inter-cloud computing, that is coordination between the two clouds, we have 3511, 3512 deals with the network as a service functional requirements, 3513 deals with infrastructure as a service functional requirements. I'm just naming these because these are dedicated documents and depending upon the implementer, the service provider or the cloud provider, they are going to refer to a certain document and they are going to make sure that their implementation is as per the ITUT recommendation. So let's continue. We have 3520 for the end-to-end resource management, 3521 for the end-to-end cloud computing management. I'm just going to mention the last one. That is cloud computing based requirements for big data. So it means that these are some of the documents, but as I said, we have a complete range. So if you really want to appreciate the efforts which have been put in by the ITUT community, these documents are publicly available on the ITU website. The ITUT framework also defines the deployment models. We could have public clouds, private community or hybrid clouds. Public clouds are where anybody like myself or you could subscribe to the cloud services. Like we know we have Amazon and Microsoft Azure and AWS kind of Amazon services, which are available as cloud services for all of us to access. Then we have private cloud, which is for a dedicated community. The customers are responsible for maintaining the cloud themselves, because it's their own private cloud. Then we have a community cloud, which involves a certain dedicated community like scientists, researchers, for instance, people who are working in mining sector, automobile sector, they could have their own community-based cloud, which is application-specific or business-specific cloud. Then we could have a hybrid that's a combination of either of the above. Then certain cross-cutting aspects are important. I'll just name these and quickly go over these. Auditability means something that is retractable, that could be traced. So any transaction that takes place on cloud has to be retractable through certain logs. Then we have the availability requirement in terms of three nines up to five nines. Then governance is basically the control of execution, revocation, and management of cloud services. Interoperability means that a certain cloud provider has to provide interoperability to certain end hosts, operating systems, etc. Then maintenance and version control is something which is highly desirable, because a good cloud has to keep itself updated for any service packs or any patches or any update. Then performance has to be measured against certain performance indicators like throughput, response time, customer-specific quality of service parameters. Then portability means that a client has to be given the option to move from one place to the other while maintaining the same service level with the cloud provider. Then, personally, identifier information has to be protected. Usernames, passwords, other security credentials like your bank account details, etc. Then regulatory aspects of certain countries have to be respected. So it means if AWS by Amazon has to operate in Pakistan, they have to be agreeing to respect the regulatory aspects in Pakistan. Then resiliency means the ability to recover out of any failure like power outage, service outage, or software failure, etc. Reverseability is once a client or a customer is done with the service availing, then the service subscription has to be revoked. So all the information has to be deleted. So the customer is certain or sure that his information is now not going to be abused. Then security aspects have to be taken care like certain DOS attacks could take place and then some contractual obligations have to be respected in which a client requests for a certain platinum, gold, silver service, etc. Let's look at some service categories and cloud capabilities type. The service categories could be computing as a simple service, communication, data storage, infrastructure, network as a service, platform or software as a service. Let's take one odd example, let's take compute as a service. If computing is only required, it means that no certain operating system platform is is required, no certain application has to be used, only the infrastructure has to be used. The infrastructure could be the computing resource, the processing power expected out of the cloud. Then we could we can think about the network as a service and data storage as a service, which essentially require to incorporate the capabilities like infrastructure has to be incorporated, the platform has to be there and the application has to be utilized. So it means that the service categories are going to determine the cloud capabilities which have to be provisioned by the cloud provider. Certain emerging cloud service categories are also on the rise. Let's look at certain names. For instance, we have database as a service, we could have desktop or email as a service, identity, management or security as a service. Something, let's look at the email as a service. We all are using email like Gmail or mail.com from Microsoft or Yahoo Mail, or we have our own email servers in our universities, in our official setups like offices, etc. Now, how could we think of cloud email as a service? Now, this service is going to be a very thorough complete service in which we have the customer who is interested in getting all the features related to email like storage, acknowledgements, transmission, backup, recovery of emails, not for a single email provided like Gmail, but for all the email services that a client is interested in for an organization. Now, if that has to be provided, Gmail wouldn't take care of Microsoft mail server MSN, which would also not take care of Yahoo mail services. So if you really want to have all of these under one system in terms of management, we need to subscribe to email as a service. With this, I think we are now ready to go deeper into the cloud related aspects.