The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The MPAI-AIF V2 Call for Technologies was a 2022 solicitation for technologies to help develop the second version of MPAI’s AI Framework. It focused on trusted execution of AI applications, and it is now closed. MPAI’s call page gives the submission deadline as October 24, 2022, at 23:59 UTC. MPAI’s AI Framework page labels the call closed.
What was the MPAI-AIF V2 Call for Technologies?
MPAI-AIF is a system-oriented framework for environments that execute AI applications, which MPAI calls AI Workflows (AIWs). A workflow is assembled from AI Modules (AIMs). Application standards specify workflow and module functions, the syntax and semantics of their inputs and outputs, and how modules connect; the internal design of each module can be software, hardware, or a combination.
The call invited parties with relevant technology to propose it for possible inclusion in MPAI-AIF V2. MPAI could modify selected technologies and was not required to select any proposal. The official call described the invitation as applying to parties willing to release their technology to third parties under the MPAI-AIF V2 Framework Licence if selected. Read the MPAI-AIF V2 Call for Technologies.
What problem did V2 target?
The central issue was trusted execution. MPAI said the first framework version assumed that AI applications would run in a Trusted Zone but did not specify how an environment with the required attributes could be implemented. V2’s requirements addressed that gap with trusted services and other security-related capabilities.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
The call sought functional capabilities, not a particular security product or vendor device. Its Annex C checklist described implementation-independent APIs for encryption, attestation, trusted communication, trusted AIM storage, and trusted AIM model services.
Storage and model services
Trusted storage requirements covered initialization, reading and writing, and de-initialization. Model services covered secure and non-secure model storage. The call set out what services an implementation should support without prescribing a specific underlying product.
Rank #2
Security configuration context
A July 2022 MPAI newsletter excerpt described drawing on hardware and operating-system security features already available in an implementation environment. It also discussed letting application developers choose standard security levels or define their own feature sets, alongside security-supporting metadata. The excerpt welcomed use cases that included threat models. MPAI’s newsletter archive provides this background; it does not replace the requirements in the call document.
Who could respond, and what did acceptance mean?
Membership was not required to submit a response. A non-member whose technology was accepted for inclusion had to join MPAI; otherwise, the submission would be discarded. Respondents also had to accept the V2 Framework Licence for technologies proposed for selection. Mandatory Annex E text addressed agreement to MPAI’s standards process and licensing essential patents under the licence after approval of the technical specification and before commercial implementations became available.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Being accepted for further evaluation could also entail an implementation commitment: submitters could be required to make a working implementation, including source code, available for development of MPAI-AIF V2 reference software. The call allowed implementations in compiled or interpreted programming languages and hardware description languages.
What had to be included in a response?
The required response combined technical documentation, forms, and a live presentation:
- Detailed documentation describing the proposed technologies.
- A final Annex A information form.
- A completed Annex B evaluation sheet mapping the proposal to functional requirements, including explanations for requirements it did not meet.
- The mandatory Annex E text.
- A presentation at a teleconference announced by the MPAI Secretariat. The call said that a submission would be discarded if its presenter did not attend.
Respondents were advised to use the Annex C checklist. Comments on requirements, a preliminary demonstration with documentation, and other relevant material were optional. The call also invited feedback such as suggested changes to AIM inputs and outputs, alternative AIM partitioning, additional use cases, and technologies beyond those explicitly listed.
How were proposals evaluated?
The call described an evaluation panel made up of attending AIF-DC members, respondent non-members, and invited experts who had not submitted proposals. Respondents presented their proposals and answered questions. The panel could define and run tests, appoint reviewers, complete Annex B evaluations, receive replies from respondents, and prepare an evaluation report. Evaluation sessions were scheduled to last two hours, with a calendar to be agreed at MPAI-25.
Best Value
What was the deadline, and is the call still open?
No. MPAI marks the V2 call closed. The call document and MPAI’s general calls overview give October 24, 2022, at 23:59 UTC as the response deadline. A July 2022 newsletter excerpt instead gives October 10, 2022, at 23:39 UTC. Because the primary call page and general overview agree, October 24 is the best-supported stated deadline; the conflicting newsletter date is worth noting rather than treating as current submission guidance. MPAI AI Framework page · MPAI calls overview · MPAI newsletter archive
| Milestone | Date and time stated in the call |
|---|---|
| Online presentation | July 11, 2022, 15:00 UTC |
| Call issued | July 19, 2022, 17:00 UTC |
| Notice of intention to submit | September 13, 2022, 23:59 UTC |
| Response deadline | October 24, 2022, 23:59 UTC |
| Evaluation scheduled to begin | October 26, 2022, at MPAI-25 |
| Expected V2 publication | Spring 2023 |
What is known about the outcome?
MPAI’s current AI Framework page says the V2 call is closed and reports that MPAI-AIF V2 was subsequently developed using call responses. The available official material does not identify which individual proposals were accepted or connect particular submissions to specific features in the final standard. It therefore supports describing the call’s purpose and process, but not naming successful technologies or attributing final features to particular respondents. MPAI AI Framework page
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
