Subject: [Openpgp-dt] OpenPGP Design Team meeting 2022-03-09

From: Daniel Kahn Gillmor <[email-masked]>
Date: Wed, 09 Mar 2022 20:25:11 -0500

Here are the notes from today's meeting:

# OpenPGP Design Team Meeting

2022-03-09

Present:

  * dkg
  * stephen
  * justus
  * daniel H
  * jeffrey

Apologies from gniibe

# Agenda

## IETF 113

- who wants which bits of presenting?
  - draft agenda: https://datatracker.ietf.org/meeting/113/materials/agenda-113-openpgp-01
- 05 changes since -04 summary
  - we could do with one, justus has material
    - ACTION: justus to share his summary to the group (via https://gitlab.com/openpgp-wg/openpgp-wg-admin if possible)
  - gcm, key separation: daniel H volunteers
  - salted signatures
  - versioning, wireformat issues
- what issues/MRs to explictly raise:
  - list is the ones where we'd like confirmation from WG of what we figured or where we're still not sure
  - start making list today & continue by email
    - certificate structure: self-signatures discussion (#134)
    - gniibe's ECDH key encapsulation method (#67)
    - RSA mechanisms (#22)
      ACTION: dkg to summarize to dt mailing list
    - do we have a story about v5 keys and hardware tokens? (#63)
      ACTION: dkg to summarize to dt mailing list
    - fingerprint usability/representation, and human-in-the-loop key verification, QR codes (#44)
- other implementers?

- let's try get all that firmed up by next week
- SF will start a slide deck with administrivia, others can add to that (or whatever) and we'll aim to have one slide deck for the meeting (easier to handle)
  - we can keep changing that 'till say the Friday before the meeting
  - start with markdown or org mode
  - Docs can live in https://gitlab.com/openpgp-wg/openpgp-wg-admin

### Other topics for the WG?

- key transparency?

## followup on crypto-refresh-05

  - v5 key test vectors didn't make it into -05
    ACTION: dkg to propose an MR
    
## Interop testing

  - interoperability test suite should have some tests that confirm dealing with test vectors
  - justus says that alternate branches would be useful, each implementation that uses git should report a v5-enabled development branch so it can be added to the interop test suite
    ACTION: justus to ask specifically for what the interop test suite needs for v5 from each implementation