metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 6590: Redaction of Potentially Sensitive Data from Mail Abuse Reports

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

Email messages often contain information that might be considered private or sensitive, per either regulation or social norms. When such a message becomes the subject of a report intended to be shared with other entities, the report generator may wish to redact or elide the sensitive portions of the message. This memo suggests one method for doing so effectively. [STANDARDS-TRACK]

Document record

Document ID
RFC6590
Published
April 2012
Authors
J. Falk; M. Kucherawy
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
8
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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/6590-redaction-of-potentially-sensitive-data-from-mail-abuse-reports