Skip to main content

OpenPGP
draft-ietf-openpgp-crypto-refresh-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-openpgp-crypto-refresh@ietf.org, openpgp-chairs@ietf.org, openpgp@ietf.org, rdd@cert.org, rfc-editor@rfc-editor.org, stephen.farrell@cs.tcd.ie
Subject: Protocol Action: 'OpenPGP' to Proposed Standard (draft-ietf-openpgp-crypto-refresh-12.txt)

The IESG has approved the following document:
- 'OpenPGP'
  (draft-ietf-openpgp-crypto-refresh-12.txt) as Proposed Standard

This document is the product of the Open Specification for Pretty Good
Privacy Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/


Ballot Text

Technical Summary

   This document specifies the message formats used in OpenPGP.  OpenPGP
   provides encryption with public-key or symmetric cryptographic
   algorithms, digital signatures, compression and key management.

   This document is maintained in order to publish all necessary
   information needed to develop interoperable applications based on the
   OpenPGP format.  It is not a step-by-step cookbook for writing an
   application.  It describes only the format and methods needed to
   read, check, generate, and write conforming packets crossing any
   network.  It does not deal with storage and implementation questions.
   It does, however, discuss implementation issues necessary to avoid
   security flaws.

   This document obsoletes: RFC 4880 (OpenPGP), RFC 5581 (Camellia in
   OpenPGP) and RFC 6637 (Elliptic Curves in OpenPGP).

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Personnel

   The Document Shepherd for this document is Stephen Farrell. The
   Responsible Area Director is Roman Danyliw.

IANA Note

  (Insert IANA Note here or remove section)

RFC Editor Note