...
The High Assurance VID Task Force (HAVTF) is a task force of the ToIP Technology Stack Working Group, which will explore how to bridge . Its mission is to create a specification and implementation guidance for how the controller of a verifiable identifier (VID) can enable greater assurance in the integrity of that VID though mechanisms that enable the controller to bridge across different:
“VID Flavours”: including VID flavours—including Decentralized Identifiers (DIDs), X.509 certificates and the Domain Name System (DNS) records) with high records—to provide both higher cryptographic assurance and strong stronger semantic linkage; and,
“Trust Realms”: including how contrasting approaches to VID-based trust architecture can share common “Roots” of trust to establish interoperability between “trust realms”.
...
Trust realms (aka trust domains) so the same VID can be verified from more than one trust roots to increase human trust and enhance interoperability.
This “bridged approach” to VIDs will lay the foundation for High Assurance (HA) Trust over IP (ToIP) Profiles that remain agnostic to the underlying VIDVID Profiles that can work with many different types of VIDs. This approach allows decision-makers to choose the most suitable VID for specific contexts and purposes without foregoing interoperability between VID systems. Through Below is one example of how such an HA VID identifying an example company could be deployed based on a DID, a DNSSEC record (following the High Assurance DIDs with DNS RFC), and an X.509 digital certificate containing an LEI (following ISO 17442 Part 2).
...
By designing a framework that supports and acknowledges theunique benefits of each “VID flavour”VID flavour, different flavours can co-exist rather than compete, resulting . This should result in a more robust, scalable, flexible and High Assurance high assurance architecture for the internet implementation of ToIP digital trust ecosystems.
For a complete overview of the development process for the ToIP technology stack, see Evolution of the ToIP Stack.
...
The deliverable of this Task Force is the High Assurance VID Specification, intended to create common patterns for establishing trust between different “VID Flavours”VID flavours. Accordingly, a VID must meet the requirements of a Verifiable Identifier (VID) as specified in the ToIP Technology Architecture V1.0 Specification and the draft ToIP Trust Spanning Protocol Specification. The requirements in this specification must interoperate with other ToIP component specifications as explained in the Evolution of the ToIP Stack.
Please find the DRAFT HAVID Specification here
Leadership
Please add your name to this list if you wish to be a lead/ co-lead chair of this task force:
...
<name here, plus affiliation if an organizational member>
Meeting Schedule and Notes
...
Please check the ToIP Calendar for current times and Zoom links for these meetings.
Meeting Notes, including Zoom recordings, are kept for every meeting — see the HAVTF Meeting Pages for an index.
Meetings agendas are also announced on the ToIP Slack channel #HAVID. Please join us there.
Milestones
...
Copyright mode: OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0 )
Patent mode: OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0 )
Source code: Apache 2.0 (available at http://www.apache.org/licenses/LICENSE-2.0.html )
...