An Open Specification for Pretty Good Privacy (openpgp)
| ||||||||||||||||||||||||||||||||||||||||||||
| Group | |
|---|---|
| Name: | An Open Specification for Pretty Good Privacy |
| Acronym: | openpgp |
| Area: | Security Area (sec) |
| State: | Concluded |
| Charter: | charter-ietf-openpgp-01 (Approved) |
| Personnel | |
| Chair: |
Derek Atkins <derek@ihtfp.com> |
| Area Director: | ? |
| Mailing List | |
| Address: | ietf-openpgp@imc.org |
| To Subscribe: | ietf-openpgp-request@imc.org |
| Archive: | http://www.imc.org/ietf-openpgp/mail-archive/ |
PGP, or Pretty Good Privacy, first appeared on the Internet in 1991.
It
has enjoyed significant popularity amongst the Internet Community.
PGP is used both for protecting E-mail and File Storage. It presents a
way to digitally sign and encrypt information "objects." As such it is
well suited for any store and forward application.
The goal of the OpenPGP working group is to provide IETF standards for
the algorithms and formats of PGP processed objects as well as
providing
the MIME framework for exchanging them via e-mail or other transport
protocols.
Because there is a significant installed base of PGP users, the
working
group will consider compatibilty issues to avoid disenfranchising the
existing community of PGP users.
Security Issues:
The whole purpose of Open-PGP is to provide security services.
| Done |
Submit Internet-Draft for PGP Key Format & Message Specification
|
| Done |
Submit Internet Draft for MIME encapsulation of PGP Messages Specification
|
| Done |
Issue WG Last Call for PGP Key Format & Message Specification Internet-Draft documents
|
| Done |
Submit PGP Key Format & Message Specification Internet-Draft to IESG for consideration as a Proposed Standard.
|
| Done |
WG Last Call for PGP/MIME draft
|
| Done |
Submit PGP/MIME draft to IESG for consideration as PROPOSED standard
|
| May 2001 |
Submit Multiple Sig draft to IESG for consideration as PROPOSED standard
|
| Jul 2001 |
Begin RFC2440, PGP/MIME Interoperability testing
|
| Aug 2001 |
Request DRAFT status for RFC2440
|