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

John C Klensin <john-ietf@jck.com> Sat, 19 April 2014 16:00 UTC

Return-Path: <john-ietf@jck.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 19A0A1A0035 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 09:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level:
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] 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 Xh-vmXsE1Vb7 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 09:00:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 037261A0020 for <ietf@ietf.org>; Sat, 19 Apr 2014 09:00:33 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WbXgq-000FDz-BP; Sat, 19 Apr 2014 12:00:28 -0400
Date: Sat, 19 Apr 2014 12:00:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com>
In-Reply-To: <01P6TOCIJM0W00004W@mauve.mrochek.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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6YfRNiqkpNabOXCm-iM-HYcXo6k
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 16:00:35 -0000

--On Saturday, April 19, 2014 08:17 -0700
ned+ietf@mauve.mrochek.com wrote:

> 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.

Ned,

I agree, but I also think there is another element of the
situation that got us here, and that has led us close to other
problems in the past.  When the RFC Editor is asked to publish a
non-WG document (i.e., either an individual submission through
the IETF stream or as an independent submission) that could be
construed as some sort of standard (whether actually standards
track or not) or approval of an IANA parameter registration is
on the basis of expert review, there as a potential for the
appearance of conflicts of interest.   Those conflicts need not
be of the traditional legal or financial variety.  They can
occur (or be perceived to occur) when someone's institutional or
organizational relationships outside the IETF might lead people
to suspect that review and decision-making might not be as
careful, unbiased, or primarily reflective of the interest of
the IETF or the broader Internet community as we would like it
to assume it always is.  For situations where troublesome
relationships exist or might be inferred (even by those
suffering from mild paranoid), we need to get much more careful
about disclosure of the relationships involved.

> 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.

Indeed.

    john