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

ned+ietf@mauve.mrochek.com Sat, 19 April 2014 15:30 UTC

Return-Path: <ned+ietf@mauve.mrochek.com>
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 0CD321A0019 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 08:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level:
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ANbgLleTryG4 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 08:30:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5841A0007 for <ietf@ietf.org>; Sat, 19 Apr 2014 08:30:55 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6TOCLSZI80065LF@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Apr 2014 08:25:47 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 19 Apr 2014 08:25:39 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6TOCIJM0W00004W@mauve.mrochek.com>
Date: Sat, 19 Apr 2014 08:17:44 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Fri, 18 Apr 2014 21:09:16 -0400" <5351CCBC.4070901@meetinghouse.net>
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> <5351CCBC.4070901@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0ntD84dFYdhf_Q7rBNO3SwQFSUE
Cc: ietf@ietf.org
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: Sat, 19 Apr 2014 15:30:56 -0000

> > I've been saying from the start that this was a failure on the IETF's
> > part.

> > It's just not the kind of failure you think it was.

> Any suggestions on how we might approach making changes?  I guess
> overall architecture, process, and policy are IAB's purview - but how
> does one get folks to pay attention - I haven't seen any IAB members
> commenting here, for example. (Note: My own IETF involvement has always
> been one step removed - mostly in my days at BBN, where I sat next to a
> lot of active IETF participants, but spent more of my time on system
> design and application of protocols.  My direct standards involvement
> has always seemed to end up in other forums - mostly military and
> security stuff that ran under funny venues. These days, I'm more on the
> tail end of being effected by such things as this current debacle -
> which are kind of motivating me to get more seriously involved.)

I've been thinking about it, and I think this needs to be addressed on at least
two different fronts. First, I've come to believe that the IETF needs to say
something, in  some capacity, about the political aspects of the DMARC
situation specifically.

I also think the time has come to try and address the more general problem
of misunderstanding and/or misrepresentation of the status of various
documents. This probably needs to be addressed through a combination of
automatic labeling as well as some explicit statements here and there.

And this really needs to be spearheaded by the IESG, not the IAB. I hope the
IESG is already considering taking action. If not, they should be.

				Ned