Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists

Dave Crocker <dhc@dcrocker.net> Fri, 25 April 2014 03:26 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3A71A0439 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOK6PLFsQ51Z for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:26:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 933BF1A02F9 for <ietf@ietf.org>; Thu, 24 Apr 2014 20:26:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3P3Q02Z022953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 24 Apr 2014 20:26:03 -0700
Message-ID: <5359D543.5070900@dcrocker.net>
Date: Thu, 24 Apr 2014 20:23:47 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, Doug Barton <dougb@dougbarton.us>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com>
In-Reply-To: <01P71CGX4VD8000052@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 24 Apr 2014 20:26:03 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zz9UQhitillhAo2cetGA23ZlHHo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 03:26:12 -0000

On 4/24/2014 7:45 PM, ned+ietf@mauve.mrochek.com wrote:
>> It's incredibly obvious that the IETF either didn't listen to, or
>> didn't act on clear messages from the operator community on this
>> topic.
>
> Well, here I sort of agree. What the IETF didn't do is react to the
> danger this posed in a timely way. Either on a technical or political
> level.


The fundamental flaw in this sort of view is that the IETF initiates 
organization efforts. Or that it acts on "messages".  It doesn't.  It 
provides an environment for workers from the community to organize open 
standards efforts.

In other words, the failure is of the industry to formulate an effort 
and bring it to the IETF.  Other than SPF, DKIM and DMARC, of course, 
which have variously been brought to the IETF.  (I'm not trying to 
re-open a debate on the details of those three, but merely to note that 
they are examples.)

Were there examples of efforts to bring work to the IETF and have it be 
rejected, that might be the IETF's 'fault'.  DMARC is the closest 
example to that and, as has been thoroughly hashed and re-hashed, it did 
not match the usual IETF model for doing work.

So sorry, but no, there have been essentially no 'clear messages from 
the operator community' and more importantly, no /efforts/ other than 
SPF, DKIM and DMARC.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net