resources: acdc-tf-2023-04-11
This data as json
| id | type | name | url | maintainer | status | last_checked | date | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| acdc-tf-2023-04-11 | meeting | ACDC Task Force meeting, 2023-04-11 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22992873 | Trust over IP (ACDC Task Force) | quiet | 2026-10-15 | 2023-04-11 | 2023 | practitioner | official | public | Discussion covered binding an AID (autonomic identifier) to other key material, through a seal in the KEL (key event log), a TEL (transaction event log), or BADA (best available data acceptance), and how to do this in keripy, with references on BADA and RUN (read, update, nullify). The meeting planned IIW (Internet Identity Workshop) sessions, including KERI 101 and 201, Signify and KERIA, did:keri, SSH (Secure Shell) login with KERI, VC-ACDC proof formats and the vLEI (verifiable Legal Entity Identifier) in telecom, and listed ACDC privacy mechanisms. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22992873 | https://zoom.us/rec/share/2JzqR6t65xKbZ_qWWfRalkiMbD9c-aqMRZ44IFnVN-OchvHSOMKEdP9Gv7SJO50M.Lzo23Ud-DRqVW29z?startTime=1681222199000 | acdc-task-force | 1 | 0 |