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

ned+ietf@mauve.mrochek.com Mon, 21 April 2014 05:07 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 B6FC11A012E for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 22:07:38 -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 ht9KYtdW30gv for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 22:07:37 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8931A002D for <ietf@ietf.org>; Sun, 20 Apr 2014 22:07:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6VV5MFTEO006PCP@mauve.mrochek.com> for ietf@ietf.org; Sun, 20 Apr 2014 22:02:32 -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; Sun, 20 Apr 2014 22:02:28 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6VV5KC6JK00004W@mauve.mrochek.com>
Date: Sun, 20 Apr 2014 21:47:17 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Sun, 20 Apr 2014 09:57:12 -0500" <5353E048.5020001@qti.qualcomm.com>
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> <01P6TOCIJM0W00004W@mauve.mrochek.com> <5353E048.5020001@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nl1sUEHKMqAQTcIWvN-vzqxoUdQ
Cc: ned+ietf@mauve.mrochek.com, 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: Mon, 21 Apr 2014 05:07:38 -0000

> On 4/19/14 10:17 AM, ned+ietf@mauve.mrochek.com wrote:
> > 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.

> The timing has been impeccable. The IESG had been privately talking
> about the "IETF relevance" issue, including why people are bringing
> "done" work to the IETF instead of working inside of the IETF. And
> related to "done" work, we have also been discussing the relative merits
> of AD-sponsored documents vs. ISE documents and what the appropriate use
> of IESG and IETF time is for these things. We've had all of that on our
> agenda for our upcoming retreat in a couple of weeks, and planned to
> discuss it with the IAB during a joint meeting. Then this DMARC thing
> happens, and Vidya published her article on "why I quit writing internet
> standards". It could not have been timed better.

> I'm trying to get my head around what we should have done differently on
> this, both tactically and strategically, so that I can summarize it for
> the discussion. But I can say pretty confidently that this is a topic
> frontmost in the minds of IESG folks.

On the misunderstanding/misrepresentation issue, I'm not sure asking what
could have been "done differently this time" is the right question. Our
processes were followed AFAIK. The misunderstanding/misrepresentation 
of the (preliminary) result of that process is not really a result of
what was done there, but rather the context in which the process operates.

But to my other point - what came out of the process - yes, I entirely
agree we need to look at what could have been done differently.

And on that score I'm not going to presume to offer specific advice. What I
will say is that I think you need to widen your scope to consider other
specifications. I already pointed out on the ietf-822 list how the SPFBIS
specifications contains what I consider to be totally inadequate advice on how
to address a similar, albeit less serious and far easier to address, issue. 

In fact I think some examination of how similar issues have been handled in
other recent documents is warranted.

				Ned