ObsoletedLegacy stream

RFC 1040: Privacy enhancement for Internet electronic mail: Part I: Message encipherment and authentication procedures

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1113.

Current document in this lineage: RFC 1421Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures

In plain English — editorial summary, not part of the RFC

This RFC is the Outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This memo defines message encipherment and authentication procedures, as the initial phase of an effort to provide privacy enhancement services for electronic mail transfer in the Internet. Detailed key management mechanisms to support these procedures will be defined in a subsequent RFC. As a goal of this initial phase, it is intended that the procedures defined here be compatible with a wide range of key management approaches, including both conventional (symmetric) and public-key (asymmetric) approaches for encryption of data encrypting keys. Use of conventional cryptography for message text encryption and/or integrity check computation is anticipated.

Document record

Document ID
RFC1040
Published
January 1988
Authors
J. Linn
Status
UNKNOWN
Stream
Legacy
Area
Pages
29
Also known as
Obsoletes:
RFC 989
Obsoleted by:
RFC 1113

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 989 (1987)
  2. RFC 1040 (1988)
  3. RFC 1113 (1989)
  4. RFC 1421 (1993)

Read the full history of Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures

Referenced by

One later RFC formally updates or obsoletes part of this document.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/1040-privacy-enhancement-for-internet-electronic-mail-part-i-message-encipherment-and