Last Call: <draft-ietf-marf-redaction-03.txt> (Redaction of Potentially Sensitive Data from Mail Abuse Reports) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 01 December 2011 16:21 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-marf-redaction-03.txt> (Redaction of Potentially Sensitive Data from Mail Abuse Reports) to Informational RFC
Message-ID: <20111201162104.1088.81619.idtracker@ietfa.amsl.com>
Date: Thu, 01 Dec 2011 08:21:04 -0800
Cc: marf@ietf.org
Precedence: list
Reply-To: ietf@ietf.org

The IESG has received a request from the Messaging Abuse Reporting Format
WG (marf) to consider the following document:
- 'Redaction of Potentially Sensitive Data from Mail Abuse Reports'
  <draft-ietf-marf-redaction-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-12-15. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-marf-redaction/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-marf-redaction/


No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-marf-redaction-03.txt> (Re… The IESG