Standard

The present document describes how Network Functions Virtualisation (NFV) related interfaces and abstractions are to be derived and specified. It describes the concepts associated with these interfaces and abstractions. It covers the specification process / methodology in general. It presents a cross-cutting framework which covers compute, hypervisor and infrastructure network domains, also data, control and management planes.
 
The present document does not specify all the interfaces and abstractions as these are covered by other documents, e.g. the NFV INF domain specific documents. Examples of interfaces and abstractions are nevertheless supplied to illustrate the methodology.
 
The present document does not provide any detailed specification but makes reference to specifications developed by other bodies and to potential specifications, which, in the opinion of the NFV ISG could be usefully developed by an appropriate standards development organization (SDO). Furthermore the NFV INF domain specific documents will not provide detailed specifications either.

The present document enumerates metrics for NFV infrastructure, management and orchestration service qualities that can impact the end user service qualities delivered by VNF instances hosted on NFV infrastructure. These service quality metrics cover both direct service impairments, such as IP packets lost by NFV virtual networking which impacts end user service latency or quality of experience, and indirect service quality risks, such as NFV management and orchestration failing to continuously and rigorously enforce all anti-affinity rules which increases the risk of an infrastructure failure causing unacceptable VNF user service impact. Performance relationships exist between the metrics described in this document and in other specifications such as draft-ietf-ippm-model-based-metrics-02 (work in progress) (February 2014): "Model Based Bulk Performance Metrics", M. Mathis and A. Morton.
 
The present document does not consider:

• Units of measurement for reporting, such as whether VM premature release rates should be expressed as hourly rate (e.g. 0,0001 premature VM release events per hour), annualized rate (e.g. 0,88 premature VM release events per year), hours between events (e.g. 10 000 hour mean time between premature release events), or events per other unit of time (e.g. 100 000 FITs, meaning 100 000 premature release events in one billion hours of operation).
• Methods of Measurement which stipulate exactly how metrics will be measured.
• Rigorous counting and exclusion rules, like the precise details given in the TL 9000 Measurements Handbook TL 9000 Measurements Handbook, release 5.0, July 2012, QuestForum (http://www.tl9000.org/handbooks/measurements_handbook.html)
• Metrics that do not directly or indirectly impact VNF user service quality, like power efficiency.

The present document describes the management and orchestration framework required for the provisioning of virtualised network functions (VNF), and the related operations, such as the configuration of the virtualised network functions and the infrastructure these functions run on. The objectives are to define this framework, provide requirements for management and orchestration, identify topics that may serve in later gap analysis against current standards, identify best practices and provide guidance on how to address identified new topics. The focus of the present document is on aspects of management and orchestration that are specific to NFV.
 
The present document addresses the following topics of management and orchestration: architecture framework for management and orchestration of NFV, information elements, interfaces, provisioning, configuration, and operational management, including interworking with existing operations and management systems.

The present document objective is to identify the most common and relevant software architectural patterns present when virtualising network functions and therefore to identify and specify functional requirements necessary to enable such patterns. The information consolidated is reflecting the experience from vendors and operators going through virtualisation of a number of network functions, with a focus on the use case list provided by the NFV Use Cases GS document     ETSI GS NFV 001 (V1.1.1): "Network Functions Virtualisation (NFV); Use Cases”.
 
The present document describes the Network Function Virtualisation abstract software architecture comprising of the following topics:

• Defining the functions, and interfaces of software architecture relative to the NFV overall architecture.
• Supporting Management and Orchestration Functional requirements.
• Supporting Infrastructure requirements.
• Describing best practices for NFV Design.
• Functional Decomposition types and use cases.

The present document does not provide any detailed specification. However, the present document makes reference to specifications developed by other bodies, gap, and to potential specifications.

Recommendation ITU-T M.3371 defines the general and functional management requirements that support service management in a cloud-aware telecommunication management system (see Recommendation ITU-T M.3070) and provides a functional framework for service management in a cloud-aware telecommunication management system.

Recommendation ITU-T M.3372 introduces a functional framework and functional requirements for resource management in cloud-aware telecommunication management systems. It provides the composition of the functional framework and the functions of each component in the framework. In this Recommendation, the general background and status of cloud computing management are also analysed. The benefit of introducing a functional framework and functional requirements for resource management in cloud-aware telecommunication management systems is also explained.

This standard provides semi-autonomous processes using standards to create and maintain news purveyor ratings for purposes of public awareness. It standardizes processes to identify and rate the factual accuracy of news stories in order to produce a rating of online news purveyors and the online portion of multimedia news purveyors. This process will be used to produce truthfulness scorecards through multi-faceted and multi-sourced approaches. The standard defines an algorithm using open source software and a score card rating system as methodology for rating trustworthiness as a core tenant in an effort to establish trust and acceptance.

The standard identifies/addresses the manner in which personal privacy terms are proffered and how they can be read and agreed to by machines.

The standard provides phenotypic and demographic definitions that technologists and auditors can use to assess the diversity of face data used for training and benchmarking algorithmic performance, establishes accuracy reporting and data diversity protocols/rubrics for automated facial analysis, and outlines a rating system to determine contexts in which automated facial analysis technology should not be used.

This standard defines a model for ethical considerations and practices in the design, creation and use of empathic technology, incorporating systems that have the capacity to identify, quantify, respond to, or simulate affective states, such as emotions and cognitive states. This includes coverage of 'affective computing', 'emotion Artificial Intelligence' and related fields.

Draft Recommendation ITU-T Y.ccgmfdc:"Global Management Framework of Distributed Cloud"

This Recommendation describes the framework of risk management in cloud computing, including risk assessment, risk treatment, risk acceptance, risk communication, risk monitoring and review, etc. It focuses on the risk management processes of CSP.

- Overview of risk management in cloud computing;

- Framework of risk management in cloud computing.