Re: IETF Mailing Lists and DMARC

John C Klensin <john-ietf@jck.com> Wed, 02 November 2016 18:42 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 779861296B7 for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 11:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.397
X-Spam-Level:
X-Spam-Status: No, score=-3.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
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 r91biPZ75Gy4 for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 11:42:22 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 688DD129B3A for <ietf@ietf.org>; Wed, 2 Nov 2016 11:42:20 -0700 (PDT)
Received: from [198.252.137.10] (helo=JcK-HP8200) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1c20UM-000Ppb-QW; Wed, 02 Nov 2016 14:42:18 -0400
Date: Wed, 02 Nov 2016 14:42:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IETF Mailing Lists and DMARC
Message-ID: <F18C2B71BD0226476668EB04@JcK-HP8200>
In-Reply-To: <3244D636-18A7-4F7C-A9F2-E9FA1BD5C1F2@vpnc.org>
References: <CAPt1N1=_jvrNbhxDyWXpJszUtqRZEEouRibwgWD1aY5wfhsX_Q@mail.gmail.com> <20161102174342.67143.qmail@ary.lan> <CAPt1N1=bC96HfVN2s2ZcQjaOtmut2ZTbbKWdGG4mEQT6uOPsGA@mail.gmail.com> <3244D636-18A7-4F7C-A9F2-E9FA1BD5C1F2@vpnc.org>
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.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f9PuPxgDyZ0c_o3fyLW4LZACdvQ>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 02 Nov 2016 18:42:24 -0000

FWIW, as someone else who has been trying to stay tuned out of
this without completely succeeding, +1.

And BTW, there are reasons for preferring "real" addresses for
those posting to a list in addition to whatever value they may
have for private replies.  One is that, when a thread gets long,
some of us find it efficient to read messages from people who
usually have something worthwhile to say at higher priority than
those who often contribute noise.

   john


--On Wednesday, November 02, 2016 11:18 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> On 2 Nov 2016, at 10:49, Ted Lemon wrote:
> 
>> I think that really what is going on here is that a very
>> small number of people who talk a lot have prevented forward
>> progress fixing an issue that significantly affects many IETF
>> participants who aren't subscribed to ietf@ because of the
>> noise factor and hence haven't seen the discussion.
> 
> That is the opposite impression that I have gotten. It feels
> to me that what has happened is that the same discussion
> happens in multiple places with groups that have only some
> overlap, a person in one group is sure they know the one true
> solution, and that no one else has thought of it before, so
> they think that people who say "look at this earlier
> discussion" are really saying "we don't want to hear from you".
> 
> Before I tuned out of this particular discussion (and I'm not
> sure why I'm tuning in again now...), I was pleasantly
> surprised by the amount of "A: we should do X" -> "B: but that
> would have the side-effect of Y" -> "A: arrgh, you're right.
> How about Z?" -> "C: that would have this side effect" that
> went on. It was a wide-ranging, open discussion of tradeoffs.
> After the third iteration, however, the participants maybe got
> a bit tired or restating them.
> 
> --Paul Hoffman
>