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

Doug Barton <dougb@dougbarton.us> Fri, 18 April 2014 04:28 UTC

Return-Path: <dougb@dougbarton.us>
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 EDD2D1A0132 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.375
X-Spam-Level:
X-Spam-Status: No, score=-0.375 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Ar288V43-50r for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:28:48 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id C83A81A0101 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:28:48 -0700 (PDT)
Received: from [192.168.2.11] (unknown [99.17.29.183]) by dougbarton.us (Postfix) with ESMTPSA id 19FEB22B1A for <ietf@ietf.org>; Fri, 18 Apr 2014 04:28:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397795324; bh=y3vV2/nX+Q5N1ZzV7s79t82aSzuPZIChLK2s7Ddf4V8=; h=Date:From:To:Subject:References:In-Reply-To; b=jZOigkFPnvWmvWmfbRPrFoCL2CDmks7nnvHFLYPUUqXsrofF6a8+NgV7wx+aqD0EZ x6J3apmSAlhoAG8MLobZBKgcJB+/7Slduxl+lb0GnZbiL2Og8IEgJo1un9dgvuJx26 2V4kSQTBX0Xm4+GXAqiBJksKl0VpwTjPZwgwWRxU=
Message-ID: <5350A9FB.9010307@dougbarton.us>
Date: Thu, 17 Apr 2014 21:28:43 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
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>
In-Reply-To: <01P6QVVGQA4W00004W@mauve.mrochek.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UBNYrjiOoprqId3r2pmTkR_XK1c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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, 18 Apr 2014 04:28:53 -0000

On 04/17/2014 07:41 AM, ned+ietf@mauve.mrochek.com wrote:
> I also find it particularly revealing that one of the arguments being
> made here is along of the lines of, "Everything else has had to
> change, why are those stodgy old mailing list thingies somehow
> exempt?" Except that's not it at all - the approach was always
> essentially, "We're going to screw you, how about you do X or Y to
> mitigate the damage a little?" To which the answer, predictably, was
> less than enthusiastic.

Another way to look at this is that the IETF, which ostensibly is 
interested in "input from operators," received pretty clear "input" from 
the operators of the largest mail systems on the planet, and 
collectively stuck their fingers in their ears and sang "la la la la la, 
I can't hear you" because it didn't like what was being said.

The message was pretty clearly, "We think DMARC is valuable enough to us 
that we plan to deploy it even though it has the unfortunate side effect 
of causing problems for mailing lists." Rather than throwing up our 
hands and telling the DMARC folks that we refuse to work with them 
unless their solution solves the problem of our anachronistic use case 
that that constitutes only a tiny percentage of their overall traffic; a 
more rational approach would have been to recognize that the tail is not 
going to wag the dog here and start working with mailing list authors to 
solve the problem of how to live in a world that includes DMARC.

When people talk about how the IETF is out of touch with the operator 
community and increasingly irrelevant, this is exactly the kind of thing 
that they are talking about. We ignore this lesson at our peril.

Doug