RFC 989: 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 1040, RFC 1113.
Current document in this lineage: RFC 1421 — Privacy Enhancement for Internet Electronic Mail: Part I: Message Encryption and Authentication Procedures
In plain English — editorial summary, not part of the RFC
This RFC suggests a proposed protocol for the Internet community and requests discussion and suggestions for improvements. This RFC is the outgrowth of a series of IAB Privacy Task Force meetings and of internal working papers distributed for those meetings. This RFC 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. 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 authentication is anticipated.
Document record
- Document ID
- RFC989
- Published
- February 1987
- Authors
- J. Linn
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 23
- Also known as
- —
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 989 (1987)
- RFC 1040 (1988)
- RFC 1113 (1989)
- RFC 1421 (1993) ✓
Referenced by
2 later RFCs formally update or obsolete 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?