RFC 5941: Sharing Transaction Fraud Data
In plain English — editorial summary, not part of the RFC
This document describes a document format for exchanging transaction fraud (Thraud) information. It extends the Incident Handling Working Group (INCH WG) Incident Object Description Exchange Format (IODEF) incident reporting document format. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5941
- Published
- August 2010
- Authors
- D. M'Raihi; S. Boeyen; M. Grandcolas; S. Bajaj
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6546Transport of Real-time Inter-network Defense (RID) Messages over HTTP/TLSCurrent
April 2012
- RFC 5901Extensions to the IODEF-Document Class for Reporting PhishingCurrent
July 2010
- RFC 6045Real-time Inter-network Defense (RID)Obsoleted
November 2010
- RFC 6046Transport of Real-time Inter-network Defense (RID) MessagesObsoleted
November 2010
- RFC 7495Enumeration Reference Format for the Incident Object Description Exchange Format (IODEF)Current
March 2015
- RFC 8134Management Incident Lightweight Exchange (MILE) Implementation ReportCurrent
May 2017
- RFC 8600Using Extensible Messaging and Presence Protocol (XMPP) for Security Information ExchangeCurrent
June 2019
- RFC 8727JSON Binding of the Incident Object Description Exchange FormatCurrent
August 2020
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?