IEEE 2842:2021 pdf download.IEEE Recommended Practice for Secure Multi-Party Computation.
IEEE 2842 provides a technical framework for secure multi-party computation (MPC), including specifying the following:
An overview of secure multi-party computation
A technical framework of secure multi-party computation
Security levels of secure multi-party computation
Use cases based on secure multi-party computation
1.2 Purpose
The purpose of this standard is to define the concepts of secure multi-party computation, providing the technical and standard basis to help stakeholders use secure multi-party computation to protect their sensitive data. It also lists some use cases for secure multi-party computation.
MPC’ is a broad area that is still under active academic research, and this standard will only cover a fraction of the area where it’s ready or close to deploy for industry stakeholders.
1.3 Word usage
The word shall indicates mandatory requirements strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to).’
The word should indicates that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required (should equals is recommended that).
The word may is used to indicate a course of action permissible within the limits of the standard (may equals is permitted to).
The word can is used for statements of possibility and capability, whether material. physical. or causal (can equals is able to).
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies.
There are no normative references in this recommended practice.
3. Definitions, acronyms, and abbreviations
3.1 Definitions
For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionaiy Online should be consulted for terms not defined in this clause.
adversary: An adversary is an entity whose aim is to prevent the participants of the protocol from achieving their designed goal. For example, it could try to affect the input privacy, result correctness, or result delivery.
computation factor: A computation factor is a special form of data and carries computation value, which satisfies the following:
a) It is generated from the MPC input data.
b) Any information about input data should not be leaked by a computation factor under a given security model.
c) The result obtained by computing over the computation factor following the given MPC protocol is lossless compared to that obtained by directly calculating with the original input data.
covert adversary: A covert adversary may deviate arbitrarily from the protocol (just like the malicious
adversaries) but does not wish to be “caught” by the honest parties.
dishonest majority: An adversary may corrupt greater than or equal to half of the participants in the protocol. honest majority: An adversary may only corrupt less than half of the participants in the protocol.
malicious adversary: A malicious adversary may take any actions it wants during the protocol execution when it corrupts some participants.IEEE 2842 pdf download.