We have a community Discord server and we'd love to see you there! https://discord.gg/YEyTH5TfuB
The table below lists all deliverables of the KERI Community:
| Acronym | Full Name of Deliverable | Link to Deliverable | Lead Authors | Status / Notes |
|---|---|---|---|---|
| KERI | Key Event Receipt Infrastructure | IETF KERI Draft | Samuel Smith | |
| AID | Attributable (Autonomic) Identifiers (KERI) | IETF KERI Draft | Samuel Smith | |
| SAID | Self-Addressing Identifiers | IETF SAID Draft | Samuel Smith | Active Draft |
| CESR | Composable Event Streaming Representation | IETF CESR Draft | Samuel Smith | Active Draft |
| DID KERI | KERI DID Method | IETF DID KERI Method Draft | Phil Feairheller | |
| DID KERI W3C Reg | KERI DID Method Registration | Registration | Phil Feairheller | |
| ACDC | Authentic Chained Data Containers | IETF ACDC Draft | Samuel Smith | Active Draft |
| CESR Proof | CESR Proof Signatures | IETF CESR Proof Signatures Draft | Phil Feairheller | Active Draft |
| PTEL | Public Transaction Event Logs | IETF PTEL Draft | Phil Feairheller | Active Draft |
| IPEX | Issuance and Presentation Exchange protocol | IETF IPEX Draft | Sam Smith, Phil Feairheller | |
| OOBI | Out-Of-Band-Introduction | IETF OOBI Draft | Sam Smith | Active Draft |
The value statement and organizational principles of the IETF strongly resonate with KERI. Quoting from The Tao of IETF, emphasis added:
The IETF is a loosely self-organized group of people who contribute to the engineering and evolution of Internet technologies. It is the principal body engaged in the development of new Internet standard specifications. The IETF is unusual in that it exists as a collection of happenings, online and in-person, in which individuals voluntarily participate. It has no members, and no dues; see RFC 3935, "A Mission Statement for the IETF", for more detail.
Its mission includes the following:
- Identifying and proposing solutions to pressing operational and technical problems in the Internet
- Specifying the development or usage of protocols and the near-term architecture to solve such technical problems for the Internet
- Making recommendations to the Internet Engineering Steering Group (IESG) regarding the standardization of protocols and protocol usage in the Internet
- Facilitating technology transfer from the Internet Research Task Force (IRTF) to the wider Internet community
- Providing a forum for the exchange of information within the Internet community between vendors, users, researchers, agency contractors, operators, and network managers
The IETF mission further states that the Internet isn't value-neutral, and neither is the IETF. The IETF wants the Internet to be useful for communities that share our commitment to openness and fairness. The IETF embraces technical concepts such as decentralized control, edge-user empowerment and sharing of resources because those concepts resonate with the core values of the IETF community. These concepts have little to do with the technology that's possible, and much to do with the technology that we choose to create.
We always believed that the end state for KERI standards would be at IETF but were willing to incubate them elsewhere in advance of the formal IETF RFC standards track process if for no other reason than familiarity. We believe that there is now no longer any need for incubation. The last year has seen the keripy implementation reach beta status including support for fully functional verifiable credentials. We believe that this has sufficiently informed KERI to propose a set of IETF Internet-Draft submissions for KERI and related technology which are being pursued under the auspices of this project, WebOfTrust, with associated repositories for both code and IETF Internet-Drafts. Like a phoenix from the ashes, we believe that KERI fixes the limitations of the original PKI based Web-Of-Trust. With a KERI-enabled decentralized Web-Of-Trust we truly have a path forward to achieve a truly decentralized trust spanning layer for the Internet; (see Hourglass Model).
The work at DIF has been archived and any perceived IPR issues resolved. https://github.com/decentralized-identity/keri
See the documents in this repo titled LICENSE.md and CONTRIBUTING.md for licensing and contributing policy. Besides the IETF licensing terms, these include the comprehensive Apache2 license for all associated intellectual property (IP) including patents. The advantage of one comprehensive license for all contributions is that there will always be alignment between all contributors and for any type of contribution. This alignment includes an inbound=outbound policy for all related IP. We only want contributions to KERI made here in the WebOfTrust project that are licensed as free, and nonreciprocal open source be it software or specification.
We meet every Thursday at 10 a.m. EDT (or EST). The Zoom link is here: https://us06web.zoom.us/j/81679782107?pwd=cTFxbEtKQVVXSzNGTjNiUG9xVWdSdz09 Meeting ID: 816 7978 2107 Passcode: 379242
We meet every Tuesday at 10 a.m EDT (or EST) as part of the ACDC/KERI Task Force under the Technology Stack Working Group at the Trust over IP Foundation:
Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://us06web.zoom.us/meeting/tZUrcOCvpjkrGtMfRtTcLyp3nxnR2_7XMbgW/ics?icsToken=98tyKuGpqDwjHdyXsRmARpwcBI_CXe3xiHpcjbdwmi3xNyN_exOlOPpMAOBAR-D9
Join Zoom Meeting https://us06web.zoom.us/j/81679782107?pwd=cTFxbEtKQVVXSzNGTjNiUG9xVWdSdz09
Meeting ID: 816 7978 2107 Passcode: 379242
Community members have an education/documentation effort in progress here edu'. The repo for the Web of Trust terminology and glossaries is here.
Technical meetings on KERISSE take place twice a week. Drop us a line if you're considering participation by creating an issue here. The repo for the Web of Trust terminology and glossaries is here.
The reference implementation for KERI is the keripy implementation. This is hosted here by the WebOfTrust project. The repository may be found here:
- keripy – under development
The keripy implementation is Apache-2.0 licensed as are all repositories in the WebOfTrust project.
We also encourage the implementation of KERI in other languages. We are happy to host other implementations here in the WebOfTrust project as long as they are Apache-2.0 licensed.