[dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-bcp-02.txt

Dave Crocker <dcrocker@gmail.com> Tue, 30 April 2013 03:04 UTC

Message-ID: <517F34A8.1060706@gmail.com>
Date: Mon, 29 Apr 2013 20:04:08 -0700
From: Dave Crocker <dcrocker@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dmarc@ietf.org
References: <20130429211648.14233.26491.idtracker@ietfa.amsl.com>
In-Reply-To: <20130429211648.14233.26491.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [dmarc-ietf] Fwd: New Version Notification for draft-crocker-dmarc-bcp-02.txt
Precedence: list

Folks,

G'day.

This draft contains raw text being submitted into the hoped-for working 
group effort that will develop a BCP on DMARC usage.

I should underscore what the word 'raw' means: intended to prime the 
public discussion pump.  All of the contributors made serious efforts to 
formulate useful text -- and by my own reading did an excellent job -- 
but the text is neither reviewed nor refined.  So while my own opinion 
it's quite a nice start for the document, no aspect of it is 'firm'...

d/


-------- Original Message --------
Subject: New Version Notification for draft-crocker-dmarc-bcp-02.txt
Date: Mon, 29 Apr 2013 14:16:48 -0700
From: internet-drafts@ietf.org
To: Dave Crocker <dcrocker@bbiw.net>


A new version of I-D, draft-crocker-dmarc-bcp-02.txt
has been successfully submitted by Dave Crocker and posted to the
IETF repository.

Filename:	 draft-crocker-dmarc-bcp
Revision:	 02
Title:		 Using DMARC
Creation date:	 2013-04-29
Group:		 Individual Submission
Number of pages: 35
URL: http://www.ietf.org/internet-drafts/draft-crocker-dmarc-bcp-02.txt
Status:          http://datatracker.ietf.org/doc/draft-crocker-dmarc-bcp
Htmlized:        http://tools.ietf.org/html/draft-crocker-dmarc-bcp-02
Diff:            http://www.ietf.org/rfcdiff?url2=draft-crocker-dmarc-bcp-02

Abstract:
    Email abuse often relies on unauthorized use of a domain name, such
    as one belonging to a well-known company (brand).  SPF and DKIM
    provide basic domain name authentication methods for email.  A recent
    industry effort built an additional authentication-based layer,
    called Domain-based Message Authentication, Reporting & Conformance
    (DMARC).  It allows a sender to indicate that their emails are
    protected by SPF and/or DKIM, and tells a receiver what to do if
    neither of those authentication methods passes; it also provides a
    reporting mechanism, from receivers back to domain owners.  Such
    capabilities over the public Internet are unusual and their use is
    not yet well-understood.  This document formulates a set of best
    practices for the use of DMARC.





The IETF Secretariat




-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

[dmarc-ietf] Fwd: New Version Notification for dr… Dave Crocker