Key Transparency
bofreq-mcmillion-key-transparency-00
The information below is for an older version of this BOF request.
Document | Type | Proposed BOF request Snapshot | |
---|---|---|---|
Title | Key Transparency | ||
Last updated | 2023-01-26 | ||
State | Proposed | ||
Editor | Brendan McMillion | ||
Responsible leadership | |||
Send notices to | (None) |
bofreq-mcmillion-key-transparency-00
Key Transparency
Description
Key Transparency (KT) is a safe, publicly-auditable way to distribute public keys for end-to-end encryption. More generally, the same technology can also be used for tamper-evident logging, key usage detection, ensuring that a group of users agree on a shared value, and many other applications.
This effort aims to standardize a common protocol for Key Transparency that 1.) works for a large range of use-cases, 2.) provides clean security guarantees, 3.) is able to be thoroughly studied by security researchers, and 4.) has trustworthy open source implementations.
Required Details
- Status: Not WG Forming
- Responsible AD: Paul Wouters, Roman Danyliw
- BOF proponents: Brendan McMillion <brendanmcmillion@gmail.com>
- BOF chairs: TBD
- Number of people expected to attend: 20
- Length of session (1 or 2 hours): 1 hours
- Conflicts (whole Areas and/or WGs)
- Chair Conflicts: TBD
- Technology Overlap: TBD
- Key Participant Conflict: TBD
Information for IAB/IESG
- Protocols that already exist in this space:
- https://eprint.iacr.org/2014/1004
- https://eprint.iacr.org/2021/453
- Open source projects implementing this work:
- https://github.com/google/keytransparency
- https://github.com/facebook/akd
- https://github.com/Bren2010/katie
Agenda
- Problem statement
- Proposed scope of work
- Presentation of current draft protocol
- Wrap-up
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
N/A