The IETF is an international Standards Developing Organization that work in the development and standardization of Internet protocols. Thus, the IAB is organizing a workshop to understand the behaviour of the IETF and the process of standardization through the analysis of IETF data, such as email archives, I-Ds, RFCs, and the datatracker. This is done in order to improve the IETF’s work.
Destination Earth (DestinE) is an initiative initiated and coordinated by the European Commission’s Directorate-General for Communications Networks, Content and Technology (DG CNECT) in support of the European Green Deal and as contribution to the establishment of the Green Deal Data Space, one of several data spaces envisaged in the European Strategy for Data.
ISO/IEC 24727 specifies a set of programming interfaces and protocols enabling interactions between integrated circuit cards (ICCs) and applications resident on a variety of computer platforms. The ICCs provide generic services for multi-sector use by the applications. The organization and the operation of the ICCs conform to ISO/IEC 7816 4. It is anticipated that some application domains will seek to achieve interoperability through ISO/IEC 24727 facilities even though the applications pre-exist these facilities. To this end, various means of backward compatibility are established through mechanisms specified in ISO/IEC 24727.
ISO/IEC 24727-1:2014 specifies
system architecture and principles of operation,
the means for achieving interoperability among diverse application domains,
the conceptual service and data models that span the relevant application domains, and
the rationale for trusted processes enabled under these models.
This standard was last reviewed and confirmed in 2015. Therefore this version remains current.
This document establishes guidelines for the design format and data content of an ISO-compliant driving licence (IDL) in regard to both visual human-readable features and ISO machine-readable technologies. It creates a common basis for international use and mutual recognition of the IDL without impeding individual national/community/regional motor vehicle authorities in taking care of their specific needs.
This document provides a set of instructions for evaluation of MRPs which may incorporate contactless integrated circuits.
This evaluation is an instrument to establish the ability in principle of a specific type of document to fulfil the requirements of use. It supplies a structured approach to evaluate MRPs by:
— defining reproducible stress methods to submit the document(s) under evaluation to specific stress or environmental conditions;
— defining reproducible evaluation methods to measure numerical values for specific document properties;
— defining test sequences that specify the order in which stress methods and evaluation methods are to be performed;
— defining test plans to link specific user requirements to test sequences and related parameters.
It specifies the minimum criteria to be achieved in order to meet ICAO's expectations for durability of fully personalized MRPs.
ISO/IEC 19286:2018 aims to normalize privacy-enhancing protocols and services by
- using the mechanisms from parts of ISO/IEC 7816 and parts of ISO/IEC 18328 that contribute to security and privacy,
- providing discoverability means of privacy-enabling attributes,
- defining requirements for attribute-based credential handling, and
- identifying data objects and commands for ICCs.
Existing privacy-enhancing protocols available in a generic context are adopted for distributed systems including ICCs. Additionally, existing authentication protocols between an ICC and an external device used for establishing a secure channel are enhanced with privacy protection. Secure communication between an ICC and an on-card device is also considered.
All the protocols and services described in this document contribute to privacy. Annex B describes an example of privacy impact assessments of respective systems.
The DSP0263 specification describes the model and protocol for management interactions between a cloud Infrastructure as a Service (IaaS) Provider and the Consumers of an IaaS service. The basic resources of IaaS (machines, storage, and networks) are modeled with the goal of providing Consumer management access to an implementation of IaaS and facilitating portability between cloud implementations that support the specification. This document specifies a Representational State Transfer (REST)-style protocol using HTTP. However, the underlying model is not specific to HTTP, and it is possible to map it to other protocols as well.
CIMI addresses the management of the life cycle of an infrastructure provided by a Provider. CIMI does not extend beyond infrastructure management to the control of the applications and services that the Consumer chooses to run on the infrastructure provided as a service by the Provider. Although CIMI may be to some extent applicable to other cloud service models, such as Platform as a Service (PaaS) or Storage as a Service ("SaaS"), these uses are outside the design goals of CIMI.
This document makes use of the common meta-model used by CIM, the Common Information Model to describe the CIMI logical model. This is defined in DSP004, CIM Infrastructure Specification 2.7.
Transformation of the CIMI CIM into CIM metamodel conformant representations enables access of the services defined by CIMI in CIM-based environments. Such environments encompass a broad range of supported operating systems, languages, platforms, protocols, and other technologies.
This specification describes transformations in a manner that enables any CIM metamodel conformant representation. This document will utilize MOF for examples of such transformations.
Concerns over cloud provider security remain one of the top inhibitors to adoption of cloud deployment models. Potential consumers of cloud deployments need assurance that the security policies they require on their applications are consistently managed and enforced “in the cloud” as they would be in their enterprise.
A cloud provider’s ability to provide specific audit event, log, and report information on a per-tenant and application basis is essential. It is apparent that in order to meet these customer expectations, cloud providers must provide standard mechanisms for their tenant customers to self-manage and self-audit application security that includes information about the provider’s hardware, software, and network infrastructure used to run specific tenant applications.
A proven method to address such needs is to develop open standards to enable information sharing. Specifically, this specification provides a data format and interface definitions that support the federation of normative audit event data to and from cloud providers in the form of customized reports and logs. This specification also defines a means to attach domain-specific identifiers, event classification values, and tags that can be used to dynamically generate customized logs and reports for cloud subscribers or customers.
Adoption of this and other open standards by cloud providers’ management platforms would go far to instill greate trust in “cloud hosted applications” and be a significant step forward in fulfilling the promise of an open cloud marketplace.
The Cloud Data Management Interface defines the functional interface that applications will use to create, retrieve, update and delete data elements from the Cloud. As part of this interface the client will be able to discover the capabilities of the cloud storage offering and use this interface to manage containers and the data that is placed in them. In addition, metadata can be set on containers and their contained data elements through this interface.
This interface is also used by administrative and management applications to manage containers, accounts, security access and monitoring/billing information, even for storage that is accessible by other protocols. The capabilities of the underlying storage and data services are exposed so that clients can understand the offering.
The CDMITM International Standard specifies the interface to access cloud storage and to manage the data stored therein. This International Standard applies to developers who are implementing or using cloud storage. It documents how to access cloud storage and to manage the data stored there.
