trustoverip / tswg-keri-specification

Key Event Receipt Infrastructure (KERI)

Key Event Receipt Infrastructure (KERI)

This is the working area for the Trust over IP, "Key Event Receipt Infrastructure (KERI)" specification.

• Editor's Copy

Contributing

All Trust Over IP Foundation Technical Stack Working Group contributions are done so under the following licenses:

• Patent and Copyright Grants
• Source Code

Licensing

All Trust Over IP Foundation Technical Stack Working Group deliverables are published under the following licenses:

• Patent and Copyright Grants
• Source Code

Getting involved

Join a community of individuals and organizations solving the toughest technical and human-centric problems in digital trust. https://trustoverip.org/get-involved/membership/

Note

This work was migrated from https://github.com/WebOfTrust/ietf-keri.

tswg-keri-specification's Issues

Add definition for End-verifiability

around line 197

Add Section for Secure Signing in KERI using CESR encoding

Then the signing detail, which needs to be drafted, should be part of section 8 Secure signing in KERI using CESR encoding of the revised format.

Add Salt to terms and defs

Validator - terms and definitions

Shorten this description and move lengthy description to annex

• fix references

Add term definition for: Configuration traits, Modes

Add text from ACDC for Version String Field

Add descriptions for seals

define key state

Includes the set of currently authoritative keypairs for an AID and any other information necessary to secure or establish control authority over an AID.

Add term definition for: Backer

Add term definition for: KERI’s Algorithm for Witness Agreement (KAWA)

Add term definition for: Key state notice

Add term definition for: Witness

Need foreword section

Not sure what goes in the forward as opposed to the introduction

Verify example for Inception event pre-rotation

~ 578

Add term definition for: Autonomic identity system (AIS)

Normalize usage of event names

When using event names in the specification they should be capitalized

Fix informative references

Create First seen policy section under "Validator" annex

• fix reference under "Rotation using pre-rotation"

Add term definition for: Decentralized key management infrastructure (DPKI/DKMI)

Create an exmaple of a inception event for section 7

Fix references to WoT specs and update to ToIP

Add term definition for: Current threshold

Expand on namespaced AIDs

ToDo Explain agnosticism vis a vis namespaces

add additional formatting option for native CESR formats for messages

KERI foundational overview

We need to merge/align these paragraphs under the KERI foundational overview

[This section should be an overview of what would result from the use of all of the following concepts.
Starting with an inception event establishing the initial key state and the first entry on the KEL.
Witnesses and Watchers put in place.
This forms the basis for an ecosystem and infrastructure based on KERI to support the issuance, verification and revocation of ACDC credentials, leveraging CESR as the encoding protocol.
Plans for rotation events, planned and those in response to potential duplicitous activity]

This section needs to be added as section 4.1 KERI ecosystem and infrastructure overview of the revised format. Section 4.2 will follow in the revised format entitled Introduction to CESR encoding

Add term definition for: Key event receipt log (KERL)

Add Annex reconcilable duplicity

Add forward reference to new annex (to be created) on line 324

add missing examples to "Key event messages" section

Revise/shorten introduction

Currently the introduction is seven paragraphs

Add "first seen" description from white paper

fix format and rendering of all tables

Fix terms formatting

Define pre-rotation briefly in introduction and reference the section on pre-rotation

in abstract in first paragraph.

Add term definition for: SAD (Self-Addressed Data)

Diagram of Triad and Tetrad to include

Add term definition for: Self-addressing identifiers (SAIDs)

Clean up language in Scope section

Some awkward sentences

Add term definition for: Controller

Add example of labelling key events in KEL

~ line 542

Clean up language in Introduction

Some of the sentences got munged in all the back and forth.

Add section on reconciling duplicity

pull from keri white paper

Add term definition for: Autonomic namespaces (ANs)

Add term definition for: Next threshold

Add diagram of bound triad to KERI’s secure bindings

Flesh out terms and defintions

• Self-addressing identifiers (SAIDs)
• SAD (Self-Addressed Data)
• Autonomic namespaces (ANs)
• Autonomic identity system (AIS)
• Decentralized key management infrastructure (DPKI/DKMI)
• Key event receipt log (KERL)
• KERI’s Agreement Algorithm for Control Establishment (KA2CE)
• Controller
• Witness
• Watcher
• Key state notice
• Backer
• Configuration traits, Modes
• Seals/Anchors
• Current threshold
• Next threshold
• Ricardian contracts (RC)

Add referent to ISO OSI specification for Session and Presentation layer reference in Section 4

add reference to CESR to CESR encoding paragraph

• add cesr encoding paragraph to KERI foundation overview

Add term definition for: Watcher

Add term definition for: Seals

Add term definition for: Anchor