Open Specification for Pretty Good Privacy (openpgp)
|Open Specification for Pretty Good Privacy
|Security Area (sec)
|Show Changed 2016-07-20
Chair's message about using gitlab for document development
Get a new gitlab login, or sign in to an existing one
Issue tracker for revision of RFC 4880
Quickstart guide for gitlab
Working gitlab repository for revision of RFC 4880
|Daniel Kahn Gillmor, Stephen Farrell
Charter for Working Group
OpenPGP standardized mechanisms for object encryption, object signing, and identity certification.
The working group is chartered to work on improvements and additions to the OpenPGP format and ecosystem to address certain issues that have been identified by the community, as set out in the list of in-scope topics below. Due to the WG having been dormant for a number of years, there is somewhat of a backlog of topics, and as addressing all of these topics at once seems difficult, the WG will follow the process defined below to prioritize current lists of milestones, selected from this long list of in-scope topics.
The working group will produce a number of specifications that are adjacent to the OpenPGP specification and provide guidance to OpenPGP libraries and/or applications.
These improvements may include:
Post-Quantum Cryptography (PQC): The addition and facilitation of post-quantum algorithms for encryption and signing (using draft-wussler-openpgp-pqc) as initial input).
Forward secrecy: enable encrypted OpenPGP communication that cannot be decrypted when long-term keys are compromised.
Context binding: facilitate domain separation for signing and/or encryption.
Automatic Forwarding: using proxy re-encryption (using draft-wussler-openpgp-forwarding) as initial input).
Persistent Symmetric Keys: for long-term storage of symmetric key material, symmetrically encrypted messages, and symmetric attestations (using draft-huigens-openpgp-persistent-symmetric-keys as initial input).
First-Party Approval of Third-Party Certifications (1PA3PC): to mitigate certificate flooding attacks (using draft-dkg-openpgp-1pa3pc as initial input).
Superseded Keys: to facilitate transition to new keys without revoking the old ones.
Stateless OpenPGP Interface (SOP): using draft-dkg-openpgp-stateless-cli as initial input.
cert-d: A common certificate storage mechanism (using draft-nwjw-openpgp-cert-d as initial input).
Network-based Key Discovery Mechanisms
HTTP Keyserver Protocol (HKP): using draft-gallagher-openpgp-hkp as initial input.
Web Key Directory (WKD): using draft-koch-openpgp-webkey-service as initial input.
Key Verification Mechanisms
Web-of-Trust (WoT): Specifying semantics for the WoT calculus (using the OpenPGP Web of Trust draft as initial input).
Key Transparency: in collaboration with the Key Transparency Working Group, e.g., integrating its outputs.
Key Verification: Improved manual key verification, for example using a QR code.
Miscellaneous Cleanup Work
Semantics: Define semantics of mechanisms provided by OpenPGP.
This includes, but is not limited to, defining validity of signatures, acceptance and placement of signature subpackets, as well as structure and meaning of certificates and messages.
User ID Conventions: Properly document User ID conventions (using draft-dkg-openpgp-userid-conventions as initial input).
Revocation: Clarify and improve revocation semantics and workflows, including replacement of the deprecated Revocation Key mechanism (using draft-dkg-openpgp-revocation as initial input).
Message Grammar: Simplify the OpenPGP Message Grammar; e.g., by limiting nesting, or by constraining sequences of packet types.
Working Group Process
All work items will require demonstration of interoperable support by at least two independent implementations before being submitted to the IESG for publication.
The WG chairs will periodically poll the WG for which of the topics above to add as milestones, as participant interest, document editor, review and implementer resources permit. The WG chairs will ensure that the list of active topics is credible at all times, likely resulting in only 3-4 topics being "active" at any given time. Such polls will typically result in the addition of a call-for-adoption for one or two new topics from the list above, depending on resources, and as currently active work is completed. As calls-for-adoption are held, those will also consider the intended-status (PS, informational, BCP) for the documents concerned. Completion will typically mean that a draft has passed working group last call or IETF last call, but, if needed, the chairs will make use of other datatracker IETF document states (e.g., parked WG document) if some document is stalled for technical or personnel reasons, leaving space for tackling another topic.
The set of initial milestones below was selected following discussion on the WG list following the above process, and will be updated periodically as milestones are met.
|Call for adoption of drafts related to WKD and/or HKP to produce a proposed standard RFC
|Call for adoption of drafts related to persistent symmetric keys to produce a proposed standard RFC
|Call for adoption of drafts related to superseded keys to produce a proposed standard RFC
|Call for adoption of drafts related to post quantum cryptography to produce a proposed standard RFC