The present document provides a framework for concurrent tests of multiple services, using a top-level approach which is also modular and scalable with respect to new services. Also, the framework explicitly integrates measurement methodology, in particular reproducibility aspects.
The present document's scope is to provide guidance on OTT video streaming testing approach with a set of minimum desired and most meaningful QoE centric QoS parameters along with recommendations to create a figure of merit quantifying the OTT video streaming session quality, where possible. In addition, the set of introduced QoE centric QoS parameters aim to help with the identification of the possible roots of video quality degradation. The present document also offers means to understand aspects related with network and services optimization and troubleshooting, such as the trade-off between bandwidth usage or controlled throttling and end-to-end video quality.
The present document describes the Single Illumination System, which allows to deliver Parent Signals for direct reception by consumer receivers and, at the same time, for a deterministic generation of daughter streams for terrestrial retransmission. Parent Signals can be provided to the daughter site via all defined TS-based DVB means - be it satellite, cable or terrestrial. Metadata may be provided as part of the Parent Signal(s) (called "in-band" in the present document). Part of the metadata may also be provided "out-of-band".
Recommendation ITU‑T Y.3602 describes a model and operations for big data provenance. Also, this Recommendation provides the functional requirements for big data service provider (BDSP) to manage big data provenance. The reliability of data is an important factor in determining the reliability of the analysis result. Data provenance aims to ensure the reliability of data by providing transparency of the historical path of the data. In a big data environment, complex data processing and migration due to the big data lifecycle and data distribution cause various difficulties in managing data provenance.
The OASIS KMIP TC works to define a single, comprehensive protocol for communication between encryption systems and a broad range of new and legacy enterprise applications, including email, databases, and storage devices. By removing redundant, incompatible key management processes, KMIP will provide better data security while at the same time reducing expenditures on multiple products.
SCOPE: The aim of this Technical Report is to study and specify how to collect data and how to feedback data analytics to the network functions.
This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.
This specification describes an imperative API enabling a website to request a user’s credentials from a user agent, and to help the user agent correctly store user credentials for future use.
This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.
This specification defines a mechanism that allows developers to selectively enable and disable use of various browser features and APIs.
This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality
The LTFS Bulk Transfer standard defines a method by which a set of files, directories and objects from a source system can be transferred to a destination system. The bulk transfer of large quantities of data is well suited for LTFS due to the economic and environmental characteristics of tape. Building on top of the LTFS format, a standardized method for transferring data is defined that provides many advantages.
