Standard

The scope of the present document is to specify the minimum set of key scenarios for the Next Generation Protocols (NGP), Industry Specific Group (ISG).

The document aims to define the protocols and interfaces of LTN systems. It goes along with the document GS LTN 002 [5] on LTN functional architecture.

The present document aims to:
• describe the characteristics of the architecture of a Low Throughput Network
• illustrate the applicability of LTN in industrial communication
• highlight the specificity of LTN deployment

The present document outlines the motivation for IPv6 in IoT, the technical challenges to address IoT on constrained devices and networks, the impact on the IPv6 technology and protocols, the technology guidelines, the step by step process, the benefits, the risks, as applicable to IoT domains including: M2M, Energy, Industrial, Mining, Oil and gas, Smart city, Transportation (including EVs), etc.

IPv6-based IoT in this context refers to the connectivity network layers needed to support the communication between things. It is understood that a complete IoT system may use of an IoT architecture including but not necessarily an abstraction layer part of an IoT platform. The description of such IoT platform is out of the scope of the present document. 2

The present document outlines the motivation for the deployment of IPv6 in enterprises, the objectives, the benefits, the risks, the challenges, the technology guidelines, the different choices that arise when designing IPv6-only or dual-stack enterprise network, step-by-step process, the addressing plan, and the milestones.

The present document discusses the concepts which are foundational for Cross-Cutting Context Information Management (C3IM) and their application to a selection of Use Cases from the domains of Smart Cities, Smart Agrifood and Smart Industry. These areas of application, together with the general area of Internet of Things (IoT) technology and services, are expected to especially benefit from usage of cross-cutting (cross domain) context information, and from a set of specifications for the APIs supporting C3IM. The present document covers the following:

• A definition of terms relevant to cross-cutting Context Information Management (C3IM).
• An introduction to the notions of C3IM and the potential role of C3IM in enabling services in cross-cutting inter-domain areas, for example Smart Cities, Smart Agrifood, and Smart Industry.
• A motivation for this project's key goal, i.e. defining an API for C3IM.
• A reference diagram illustrating possible architectures and functional entities involved in facilitating C3IM.
• A set of high level Use Cases which can potentially be supported using a C3IM system.
• A subset of detailed Use Cases (scenarios) illustrating potential information flows among functional entities.
• A summary of requirements extracted from the Use Case analysis.

The present document is a study of interworking between oneM2M Architecture and 3GPP Rel-13 architecture for Service Capability Exposure as defined in the release 13 version of ETSI TS 123 682 [i.5]. The key objective and value is analyzed and described. The document also investigates the potential solution in oneM2M by evaluating the existing technical solutions.

The present document is a study of the continuation and integration of some HGI Smart Home activities into oneM2M, following the (PT2) HGI announcement of its closure by June 2016. It includes the description of HGI SH deliverables versus the appropriate oneM2M deliverables for the integration of these HGI achievements.

It intends to be used as a liaison working document with HGI about the status progress of this continuation and integration and is expected to be useful for both HGI and oneM2M to check that all technical items from HGI SH Task Force expected to be integrated are appropriately handled by oneM2M.

The present document provides an analysis and comparison of existing M2M-related Architecture work undertaken by the founding partners of oneM2M, including: the Association of Radio Industries and Businesses (ARIB) and the Telecommunication Technology Committee (TTC) of Japan; the Alliance for Telecommunications Industry Solutions (ATIS) and the Telecommunications Industry Association (TIA) of the USA; the China Communications Standards Association (CCSA); the European Telecommunications Standards Institute (ETSI); and the Telecommunications Technology Association (TTA) of Korea. In addition, architectural work by other non-oneM2M Partner Type 1 organizations is provided for consideration.

The present document is intended to ensure a common understanding of existing M2M Architectural approaches, in order to facilitate future normative work resulting in oneM2M Technical Specifications (TS). The present document has been prepared under the auspices of the oneM2M Technical Plenary, by the oneM2M Architecture Working Group.

ISO/IEC 19086-1 seeks to establish a set of common cloud SLA building blocks (concepts, terms, definitions, contexts) that can be used to create cloud Service Level Agreements (SLAs).
This document specifies
a) an overview of cloud SLAs,
b) identification of the relationship between the cloud service agreement and the cloud SLA,
c) concepts that can be used to build cloud SLAs, and
d) terms commonly used in cloud SLAs.
ISO/IEC 19086-1 is for the benefit and use of both cloud service providers and cloud service customers. The aim is to avoid confusion and facilitate a common understanding between cloud service providers and cloud service customers. Cloud service agreements and their associated cloud SLAs vary between cloud service providers, and in some cases different cloud service customers can negotiate different contract terms with the same cloud service provider for the same cloud service. This document aims to assist cloud service customers when they compare cloud services from different cloud service providers.
ISO/IEC 19086-1 does not provide a standard structure that can be used for a cloud SLA or a standard set of cloud service level objectives (SLOs) and cloud service qualitative objectives (SQOs) that will apply to all cloud services or all cloud service providers. This approach provides flexibility for cloud service providers in tailoring their cloud SLAs to the particular characteristics of the offered cloud services.
ISO/IEC 19086-1 does not supersede any legal requirement

This part of ISO/IEC 18033 is general in nature, and provides definitions that apply in subsequent parts of this International Standard. The nature of encryption is introduced, and certain general aspects of its use and properties are described. The criteria used to select the algorithms specified in subsequent parts of this International Standard are defined in Annexes A and B.

This standard defines topology, functions, and governance for cloud-to-cloud interoperability and federation.
Topological elements include clouds, roots, exchanges (which mediate governance between clouds), and gateways (which mediate data exchange between clouds).
Functional elements include name spaces, presence, messaging, resource ontologies (including standardized units of measurement), and trust infrastructure.
Governance elements include registration, geo-independence, trust anchor, and potentially compliance and audit.
The standard does not address intra-cloud (within cloud) operation, as this is cloud implementation-specific, nor does it address proprietary hybrid-cloud implementations.
 
Under development
Working documents can be found here (prior registration required): https://ieee-sa.imeetcentral.com/2302/home