RFC 5901 on Extensions to the IODEF-Document Class for Reporting Phishing
rfc-editor@rfc-editor.org Tue, 20 July 2010 21:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 155B03A67BD for <ietf-announce@core3.amsl.com>; Tue, 20 Jul 2010 14:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.113
X-Spam-Level:
X-Spam-Status: No, score=-2.113 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPLxVxzlQFms for <ietf-announce@core3.amsl.com>; Tue, 20 Jul 2010 14:04:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 37CC83A65A5 for <ietf-announce@ietf.org>; Tue, 20 Jul 2010 14:04:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3A0C4E066B; Tue, 20 Jul 2010 14:04:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5901 on Extensions to the IODEF-Document Class for Reporting Phishing
From: rfc-editor@rfc-editor.org
Message-Id: <20100720210454.3A0C4E066B@rfc-editor.org>
Date: Tue, 20 Jul 2010 14:04:54 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 21:04:39 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5901 Title: Extensions to the IODEF-Document Class for Reporting Phishing Author: P. Cain, D. Jevans Status: Standards Track Stream: IETF Date: July 2010 Mailbox: pcain@coopercain.com, dave.jevans@antiphishing.org Pages: 51 Characters: 97325 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-cain-post-inch-phishingextns-07.txt URL: http://www.rfc-editor.org/rfc/rfc5901.txt This document extends the Incident Object Description Exchange Format (IODEF) defined in RFC 5070 to support the reporting of phishing events, which is a particular type of fraud. These extensions are flexible enough to support information gleaned from activities throughout the entire electronic fraud cycle -- from receipt of the phishing lure to the disablement of the collection site. Both simple reporting and complete forensic reporting are possible, as is consolidating multiple incidents. [STANDARDS TRACK] This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC