[ietf-dkim] RFC 4686 on Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)

rfc-editor@rfc-editor.org Wed, 27 September 2006 01:04 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GSNqf-0002ZB-OE for ietf-dkim-archive@lists.ietf.org; Tue, 26 Sep 2006 21:04:29 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSNqd-00065z-9j for ietf-dkim-archive@lists.ietf.org; Tue, 26 Sep 2006 21:04:29 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k8R12pAx027450; Tue, 26 Sep 2006 18:02:57 -0700
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k8R12bYs027397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Tue, 26 Sep 2006 18:02:37 -0700
Received: from [10.20.30.177] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id k8R12HQR020557 for <ietf-dkim@mipassoc.org>; Tue, 26 Sep 2006 18:02:17 -0700 (MST) (envelope-from phoffman@proper.com)
Mime-Version: 1.0
Message-Id: <p062309b5c13f7dfec9c8@[10.20.30.177]>
Date: Tue, 26 Sep 2006 18:02:10 -0700
To: ietf-dkim@mipassoc.org
From: rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Songbird: Clean, Clean
Subject: [ietf-dkim] RFC 4686 on Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d

A new Request for Comments is now available in online RFC libraries.


         RFC 4686

         Title:      Analysis of Threats Motivating DomainKeys
                     Identified Mail (DKIM)
         Author:     J. Fenton
         Status:     Informational
         Date:       September 2006
         Mailbox:    fenton@cisco.com
         Pages:      29
         Characters: 70382
         Updates/Obsoletes/SeeAlso:   None

         I-D Tag:    draft-ietf-dkim-threats-03.txt

         URL:        http://www.rfc-editor.org/rfc/rfc4686.txt

This document provides an analysis of some threats against Internet
mail that are intended to be addressed by signature-based mail
authentication, in particular DomainKeys Identified Mail.  It
discusses the nature and location of the bad actors, what their
capabilities are, and what they intend to accomplish via their
attacks.  This memo provides information for the Internet community.

This document is a product of the Domain Keys Identified Mail
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body

help: ways_to_get_rfcs. For example:

         To: rfc-info@RFC-EDITOR.ORG
         Subject: getting rfcs

         help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html