Try   HackMD

Goals for Trust Establishment

  • Standardize method for enumerating properties of trust, including expressions of trust beyond binary decisions
  • Standardized method providing foundations of credential issuer and verifier trust.
  • Support offline and near-offline evaluations via cacheable assets
  • Avoid leaking information about trust evaluations to parties other than the one performing the evalution.
  • Enable advice for humans making trust decisions
  • Enable automated trust decisions.
  • Produce relevant specifications and reference implementations.
  • Guide decisions of interoperability profiles using these specifications.

Disussed in WG

  • Standardized way to enumerate properties of trust
    • expression of trust beyond binary decisions
  • Provide mechanism for foundations (read: bottom turtle) of credential issuer and verifier trust
  • Integrity of published data/payload
  • versioning of published data/payload
  • Avoid leaking information about trust decisions to outside parties
  • Support offline and near offline evaluation via caching of relevent assets
  • Enable automated trust decisions
  • Enable advice for humans making trust decisions
  • Produce spec and reference implementation

Existing

  • Are you who you claim to be?
  • Are you to be trusted for what you claim to be trusted for?

(from https://github.com/decentralized-identity/trust-establishment#overview)

Existing Notes

  • From the perspective of the entity being evaluated, not from the perspective of the evaluator
Last changed by 
 
Sam Curren
0
173

Read more

Aries Interop Profile 3 Proposed

This is just a sketch to use in proposing what AIP 3.0 might look like. Note that the presence of DIDComm v2 as a referenced spec consolidates concepts that were present in a variety of Aries RFCs. The list is shorter, but no concepts have been dropped. Base Requirements RFC Type RFC/Link to RFC Version Note Spec

Mar 4, 2023
0000: did:legacypeer DID Method

Authors: Timo Glastra, Sam Curren Status: PROPOSED Since: 2023-02-08 Status Note: Start Date: 2018-12-26 Tags: feature Summary The identifier part of the DID is calculated in the same way as a did:sov DID. did:legacypeer DIDs cannot be resolved without being provided a DID Document via the Aries Connections or DID Exchange Protocols.

Feb 15, 2023
Mediator Related Protocols

References for both DIDComm v1 and DIDComm v2 Protocols are provided. Currently (Feb 8, 2023) Aries projects are still using DIDComm v1 protocols. DIDComm V2 and associated protocols will begin deployment over the next several months. Forward Protocol Used to send messages to a mediator for delivery to the message receipient DIDComm v1: https://github.com/hyperledger/aries-rfcs/blob/08653f21a489bf4717b54e4d7fd2d0bdfe6b4d1a/concepts/0094-cross-domain-messaging/README.md DIDComm v2: https://identity.foundation/didcomm-messaging/spec/#routing-protocol-20

Feb 8, 2023
KERI Lite & Aries

Aries goals: Replace did:peer:2 no external dependancies outside the relationship complete on initial communication, capable of dropping 'extra' for efficiency initially: Non-transferrable AIDs with no witnesses Needs Service Endpoint

Jan 10, 2023
Read more from Sam Curren
Published on HackMD