Agenda Karim - report from RWOT Snorre's question about whether we want endpoints Rodolfo - mediator demo10/24/2022
368 - move tracing?: Suggest we merge PR #372 and then close the issue. 351 - didcomm:// scheme: got proposal from Timo; added comments to ticket; added PR #373 326 - apu and apv in ECDH-ES: awaiting PR from Baha 321 - Yolan's big review: resolved by PR #377 315 - Crystals-Kyber ex: defer 311 - multiple presentations: defer 298 - P521: PR #374 from Daniel 285 - terminology section: suggest we defer. TOIP has tooling that can generate glossaries, and we can publish one as a separate artifact. Having it in the spec is a nice-to-have that we can skip. 269 - refactor kid/skid: defer or "won't fix" (we have wordsmithed this section to some extent already): PR #375 from Daniel 263 - media type rewords: suggest close as "wont fix"4/23/2022
Peer DIDs were invented before KERI was formally described. Once KERI came along, it became clear that KERI is a more sweeping generalization of the same principles that informed most of the peer DID design. Peer DIDs embody the main principles that KERI advocates, but use just a subset of KERI's features. This means that we can redefine peer DIDs in terms of KERI. The benefits of doing so are: The peer DID spec can be much, much simpler. Peer DIDs get an upgrade path. KERI gets added momentum. Communities can come together. The DID method landscape can consolidate. This document is a first cut at redefining peer DIDs this way.3/2/2022
This file has been moved to a PR agains the DIDComm User Group repo2/21/2022
By clicking below, you agree to our terms of service.
New to HackMD? Sign up