Re: Enough DMARC whinging

Dave Crocker <dhc@dcrocker.net> Mon, 05 May 2014 21:53 UTC

Return-Path: <dhc@dcrocker.net>
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 B4AAC1A03A3 for <ietf@ietfa.amsl.com>; Mon, 5 May 2014 14:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level:
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-2.3] 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 A3OmkEuUmuIZ for <ietf@ietfa.amsl.com>; Mon, 5 May 2014 14:53:35 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0A81A037A for <ietf@ietf.org>; Mon, 5 May 2014 14:53:35 -0700 (PDT)
Received: from [192.168.19.2] ([206.29.182.192]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s45LrKb7002862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 5 May 2014 14:53:24 -0700
Message-ID: <53680844.3030706@dcrocker.net>
Date: Mon, 05 May 2014 14:53:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Enough DMARC whinging
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <536113B1.5070309@bbiw.net> <CAMm+LwiXoW3p5uCmML4kAWXnbrrAnSCK9x5U2qeHJdVgR2r_Gg@mail.gmail.com> <E3A7C677B18263C8DF6DD316@JcK-HP8200.jck.com> <5362943D.2020907@bluepopcorn.net> <536295E5.3080502@dcrocker.net> <5362B4C6.10904@meetinghouse.net> <CAL0qLwb_UJrjViZwxrSC=y4y8geY8-N0QOHMeBski3dEuBqB6Q@mail.gmail.com> <CAL0qLwYPzfjPA6qBN=SXaJFvtYZcumRnZ5tCSNHbdw1r_hyG-w@mail.gmail.com> <CAKHUCzy=EFEiAR+hQt8WKE9YtpDhk7QgoLQXTKQZYzhWuW6+HQ@mail.gmail.com>
In-Reply-To: <CAKHUCzy=EFEiAR+hQt8WKE9YtpDhk7QgoLQXTKQZYzhWuW6+HQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 05 May 2014 14:53:25 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hL-6ygVr1Hg2Nuepdnx984mr-r8
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 05 May 2014 21:53:36 -0000

On 5/5/2014 1:17 PM, Dave Cridland wrote:
> It aims to change the behaviour of Internet Mail as deployed.
> 
> Whether you want to claim that this is formally extending SMTP, per-se,
> or not is really something of a moot point - there is certainly an
> intentional, large, effect on the deployed protocol. Arguing whether
> this fits the letter of some particular definition smacks of lawyering
> to my mind.


If a large market player declared that all mail to and from them were
required to be written in a specific language, would that we a matter
for the IETF to deal with?  I think not.  (For all I know, some ISP out
there already behaves that way.)

Actions like that are at the level of "politics of use" rather than
"technology of use".  While each of us might have opinions for any such
policy, it's not the IETF's job or competence to get enmeshed in such
politics.

However if a large market player took that action and then wrote a
document explaining it and wanted that document published as an
independent stream RFC, I'd think the greater service to the community
would be to publish it.  That way the document becomes part of an
important Internet archive.


d/


ps.  And there's nothing to prevent others with opposing views from
publishing their own document, explaining the implications and evils of
the actions by the large market player...


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net