Re: DMARC: perspectives from a listadmin of large open-source lists

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 14 April 2014 18:55 UTC

Return-Path: <superuser@gmail.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 CD7261A06E8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level:
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 ev4VgXmPLs7b for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:08 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3214A1A0468 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:55:08 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so8720982wgh.16 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2Mt4+gD0Ew9nI6vNj0BSwfPJbxgtKRuyBFbO7DHYr6M=; b=UaZEfEwi9JCkeAqGmxzmrr4syaXcDumo1BgZArv+PW2LCCLp72HZTFZtCwdRnPTnzS TkkQa+KQgxnKZyMfc4PpGEhSB/X+tBjlIj0o4xEFFnjl5GkYB9Esb/KTEI9MhAP1dCU7 W2nwRfS1PgHC1qs8tV6Ofw/YiVDNq+WDHyiYD0dmpXdWSIZ6TWSRPcFmsaidgdzK8c+i lIDacXgmyfHxEZ7mdVdXZj6iOeeG42/AFTx/aZcpWsOHhIRWBmkuEqBa0rrljK4CV2Ln 6AlLDOl/g/ygGXyXoITymnEILrVQfe/R1E4BKkKdMH14CdxPGkhW1AU5KX34jSSQxv1C IeyA==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr10786446wic.5.1397501705264; Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
In-Reply-To: <534C2D23.3050600@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <534C2D23.3050600@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:55:05 -0700
Message-ID: <CAL0qLwb-v2H8hh=D2prrmO_r4K9QohWcKsL7d_qf=18FFgFcHw@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary="001a11c26ab4b7253c04f7053899"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ub6yS4mKzlzawGzBsm4XF1dj4Vk
Cc: ietf <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, 14 Apr 2014 18:55:10 -0000

On Mon, Apr 14, 2014 at 11:46 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Does this, perhaps, illuminate a flaw or failing in the way IETFs effects
> its role as the Internet's official standards body?  The more so that it's
> not stepping in after the fact to help clear up this mess?
>

Possibly.  I confess I heard the reasons for rejecting the request, but I
still don't fully understand them.


> I do wonder if there's a related case study in the way that RSS evolved
> into Atom - a case where outside work, and conflicts within it, ended up
> being worked under the IETF aegis?  (Sort of  shame that Atom has not
> become more popular.)


I'm not familiar with the story of RSS, but I do know that XMPP and DKIM
are held up as cases where work was started externally and then brought
into the IETF and finished, so there are cases where it is indeed palatable
to the powers-that-be.

-MSK