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

Dave Crocker <dcrocker@gmail.com> Tue, 02 July 2013 02:47 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 70E1111E838D for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 19:47:10 -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 hwbtPg7y7Afk for <dmarc@ietfa.amsl.com>; Mon, 1 Jul 2013 19:47:09 -0700 (PDT)
Received: from mail-ye0-x233.google.com (mail-ye0-x233.google.com [IPv6:2607:f8b0:4002:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3992F11E8304 for <dmarc@ietf.org>; Mon, 1 Jul 2013 19:47:09 -0700 (PDT)
Received: by mail-ye0-f179.google.com with SMTP id r3so1438848yen.10 for <dmarc@ietf.org>; Mon, 01 Jul 2013 19:47:07 -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=MISypBI1ao0TNvXoecLeyN/LcAmdKGIAolSZbviZ4AU=; b=UngzMH6ii6JNVl2GeSsPji77EsFH1SSCnwBeDlqDvcjrdOC+HtN4EGB5G0kwwRJRub V18WxOUxNAB8K6DvrBonVebd2W5qTRQTkhMpuSju69IQPgoYrRsVcr9f+via/3xSVIB/ LAMeXhXba9wagPOpaI8RmMkzgsmuoPmttBtABK8DJgKOzT47XssCoOHFvmymJGHsPL4t xbciyWbtvRGpdYUC3KlxZjPcD9xAIrMt8XLVhCyrNjAiIndfYutf9tea+gkWgcDiYHH5 z5H4RplC0dheZfi2OJ6f5kX5q3MIBVFy6yhs0WB/bihmO4Rbaq2Ujw2WgFYw3QCgAFl+ OzCQ==
X-Received: by 10.236.193.169 with SMTP id k29mr14013063yhn.146.1372733227746; Mon, 01 Jul 2013 19:47:07 -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 m63sm28593429yhb.10.2013.07.01.19.47.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 19:47:07 -0700 (PDT)
Message-ID: <51D23F1E.4090302@gmail.com>
Date: Mon, 01 Jul 2013 19:46:54 -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> <51D20CC0.6020605@gmail.com> <6935780.Ol8a9WOpun@scott-latitude-e6320>
In-Reply-To: <6935780.Ol8a9WOpun@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 02:47:10 -0000

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?


> I'll add to that that having watched senders try to interpret XML reports they
> receive from different providers and understand the subtleties between them
> that while the mechanics of the XML schema are there, the semantics are not
> clear enough to provide for interoperable implementations.  Even among
> implementers who have worked together in dmarc.org to develop the schema,
> there are inconsistencies.

Not sure what you are suggesting, as technical work, for the reporting 
mechanism.  I also missed the demonstration of community interest in 
those changes, ideally on this list.


> I don't think there is anything in the two issues about that would force
> existing implementers to make changes, but I think that they are not purely
> editorial either.

Sorry for my confusion, but I don't know how to classify the changes 
that you seem to be calling for.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net