Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin

Dave Crocker <dcrocker@gmail.com> Tue, 02 July 2013 04:16 UTC

Return-Path: <dcrocker@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9FCF21F9C55 for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 21:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4M3GDVBMCgMM for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 21:16:13 -0700 (PDT)
Received: from mail-gh0-x236.google.com (mail-gh0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id E948D21F9C51 for <dmarc@ietf.org>; Mon, 1 Jul 2013 21:16:12 -0700 (PDT)
Received: by mail-gh0-f182.google.com with SMTP id z15so2321940ghb.41 for <dmarc@ietf.org>; Mon, 01 Jul 2013 21:16:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=iaEwrQj5ViAGfeALTkOYfvi1tgfQiq+Jwtg9sjMT4LY=; b=IgfIqibBhFQd5JNZ66xr8LWnbAiJVTHUWWueDzey3UicibRyy0m4ZJiOWKIojFKjD+ wpiAxAcPJQv4bFd2P0gLs/qmrrMLcJBWkm65AzUxzoLL8GmKp00cvqCmdc0iIlkoPnxR K8v93ZC4hwTb2c8KCQoGuXiynXiaoea/VU3lryr0ffoVktur3BQ7gPmp2xNySBodZv+p 1gdJjlygDqzUHVL6IEvGgI2P3Le9VzD72ulk6DkgFknrrs5agHV6DCiut0R0eGUx66y/ tGHVrAIKsTtd/proFUZOWGY9sFKE/jFZE7awjVHg1kYbOFauReNUX9Y357MwnuNZB81E 9/pA==
X-Received: by 10.236.170.201 with SMTP id p49mr351335yhl.201.1372738570240; Mon, 01 Jul 2013 21:16:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net. [76.218.9.215]) by mx.google.com with ESMTPSA id s29sm38003707yhf.6.2013.07.01.21.16.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 21:16:09 -0700 (PDT)
Message-ID: <51D253FD.1080203@gmail.com>
Date: Mon, 01 Jul 2013 21:15:57 -0700
From: Dave Crocker <dcrocker@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Scott Kitterman <sklist@kitterman.com>
References: <20130630221443.71098.qmail@joyce.lan> <6935780.Ol8a9WOpun@scott-latitude-e6320> <51D23F1E.4090302@gmail.com> <2386009.gcBsi9JlR4@scott-latitude-e6320>
In-Reply-To: <2386009.gcBsi9JlR4@scott-latitude-e6320>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: dmarc@ietf.org
Subject: Re: [dmarc-ietf] DMARC BoF at IETF 87, Berlin
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmarc>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2013 04:16:13 -0000

On 7/1/2013 8:41 PM, Scott Kitterman wrote:
> On Monday, July 01, 2013 07:46:54 PM Dave Crocker wrote:
>> On 7/1/2013 7:40 PM, Scott Kitterman wrote:
>>> On Monday, July 01, 2013 04:12:00 PM Dave Crocker wrote:
>>>> Let me repeat:  better writing; no technical changes.
>>>
>>> I disagree.  I've been saying repeatedly that I think that the policy
>>> overrides are a layering violation that should be removed.  They are bad
>>> design.
>>
>> Yes you have.
>>
>> And where is the community constituency that supports that view?
>
> How many experts on the policy mechanism DMARC wants to mess with are involved
> in the discussion?  So far, DMARC is pretty much a self-licking ice cream
> cone.  To claim the lack of broad community support for a particular change is
> a reason not to seek broad community review seems like a bit of a catch 22.


Scott,

This list has been available for some time, to discuss the dmarc spec, 
the Using draft, the draft charter and the planned BOF.

Note that your opening text here was "I've been saying repeatedly".  My 
query about community support for your concerns was based on that 
reference.

In any event, you are indicating that you have concerns over the 
specifications.  That's fine, of course, but there needs to be some 
community resonance with that concern, to justify opening up the spec 
and pursuing it.  That's merely standard IETF process.

Again:  if you want folks on this list to press for something to be 
done, please recruit folks on this list to support its being done.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net