Redaction of Potentially Sensitive Data from Mail Abuse Reports
draft-jdfalk-marf-redaction-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | J.D. Falk | ||
| Last updated | 2011-08-26 (Latest revision 2011-03-07) | ||
| Replaced by | draft-ietf-marf-redaction | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-marf-redaction | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Email messages often contain information which 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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)