Sharing Transaction Fraud Data
RFC 5941

 
Document Type RFC - Informational (August 2010; No errata)
Was draft-mraihi-inch-thraud (individual in sec area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 5941 (Informational)
Telechat date
Responsible AD Tim Polk
Send notices to dmraihi@verisign.com, draft-mraihi-inch-thraud@ietf.org
Internet Engineering Task Force (IETF)                        D. M'Raihi
Request for Comments: 5941                                      VeriSign
Category: Informational                                        S. Boeyen
ISSN: 2070-1721                                                  Entrust
                                                           M. Grandcolas
                                              Grandcolas Consulting, LLC
                                                                S. Bajaj
                                                                VeriSign
                                                             August 2010

                     Sharing Transaction Fraud Data

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5941.

M'Raihi, et al.               Informational                     [Page 1]
RFC 5941             Sharing Transaction Fraud Data          August 2010

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

M'Raihi, et al.               Informational                     [Page 2]
RFC 5941             Sharing Transaction Fraud Data          August 2010

Table of Contents

   1. Introduction ....................................................4
   2. Requirements Terminology ........................................5
   3. Anatomy of a Transaction Fraud ..................................6
   4. IODEF-Document Incident Class ...................................7
   5. Thraud Record Class Definitions .................................8
      5.1. FraudEventPaymentType Class ................................9
           5.1.1. PayeeName ..........................................10
           5.1.2. PostalAddress ......................................10
           5.1.3. PayeeAmount ........................................10
      5.2. FraudEventTransferType Class ..............................10
           5.2.1. BankID .............................................11
           5.2.2. AccountID ..........................................12
           5.2.3. AccountType ........................................13
           5.2.4. TransferAmount .....................................13
      5.3. FraudEventIdentityType Class ..............................13
           5.3.1. IdentityComponent ..................................13
      5.4. FraudEventOtherType Class .................................14
           5.4.1. OtherEventType .....................................15
           5.4.2. OtherEventDescription ..............................15
      5.5. AmountType Class ..........................................15
           5.5.1. Class Contents .....................................15
           5.5.2. Currency ...........................................15
      5.6. AccountTypeType Class .....................................16
   6. IODEF Profile for an Activity Thraud Report ....................16
      6.1. Mandatory Components ......................................16
      6.2. Recommended Components ....................................17
      6.3. Deprecated Components .....................................17
   7. IODEF Profile for a Signature Thraud Report ....................19
   8. IODEF Additional Attribute Values ..............................19
Show full document text