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

Well done to all concerned, esp. Jim of course!
S.

rfc-editor@rfc-editor.org wrote:
> 
> 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
> 
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html