Re: [dmarc-ietf] DMARCbis issue: Separating reporting and policy

Jim Fenton <fenton@bluepopcorn.net> Mon, 27 May 2019 20:16 UTC

Return-Path: <fenton@bluepopcorn.net>
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 337E912014F for <dmarc@ietfa.amsl.com>; Mon, 27 May 2019 13:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
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 hSygLrzHaIbw for <dmarc@ietfa.amsl.com>; Mon, 27 May 2019 13:16:05 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFFE51200C7 for <dmarc@ietf.org>; Mon, 27 May 2019 13:16:04 -0700 (PDT)
Received: from [IPv6:2601:647:4300:2290:62a4:4cff:fe65:83dd] ([IPv6:2601:647:4300:2290:62a4:4cff:fe65:83dd]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x4RKBqeP000804 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 27 May 2019 13:11:54 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1558987914; bh=ZWsx10zkZxlECLZsZaqbDUJPjf9LyZ41GIZ4hOmTIgQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=IpKQfZr7dQYkgtwAe2dvzmjsH5JfwoM2cfQm39aUFtoqrkq118Dt48OdG1Xku3xSF fbhhcZCB4Oi5a3HuFdFA+8nfMFjLxBCFHGkeTmlEeUM3pzh0SU95cyW85sl/9p1TLi SZk/UVavRszvbdEILZu5mlb31s6lokkaEF4GpZiM=
To: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
Cc: Dave Crocker <dcrocker@gmail.com>, John R Levine <johnl@taugh.com>, dmarc@ietf.org
References: <20190523225213.C214620147B780@ary.qy> <ab587c42-dd2f-2403-999a-c7d559764726@bluepopcorn.net> <alpine.OSX.2.21.9999.1905241036450.50141@ary.qy> <280824a0-536b-91f1-8072-f7d1cf3051aa@bluepopcorn.net> <789c58b1-7b45-3af0-dd1b-aca0c415db02@gmail.com> <5f12bf4f-ce25-c2d8-7cab-10eb41182eac@bluepopcorn.net> <20190527181957.Horde.ERQnFG0Wm3s5gJcNB6IU7Zs@webmail.aegee.org>
From: Jim Fenton <fenton@bluepopcorn.net>
Message-ID: <d5daeb4a-ff99-0fda-7548-90ad0d4157bf@bluepopcorn.net>
Date: Mon, 27 May 2019 13:11:47 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190527181957.Horde.ERQnFG0Wm3s5gJcNB6IU7Zs@webmail.aegee.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FBIRcBh1GHtGXMKc-x1jWxSjQYA>
Subject: Re: [dmarc-ietf] DMARCbis issue: Separating reporting and policy
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 27 May 2019 20:16:06 -0000

On 5/27/19 11:19 AM, Dilyan Palauzov wrote:
> Hello Jim,
>
> Do you want to split yourself reporiting and policy and create two 
> separate documents, or do you know somebody wiliing to perform the 
> separation?  I cannot imagine why shall one want to read and 
> understand only reporting or only policy and thus I do net understand 
> for which target group will be these separated documents. The current 
> documents are suitable to achieve their aim.  (Well, to contradict 
> myself, I would like to read and understand all the RFCs, so a single 
> RFC containing all current RFCs would be enough, but obviously, I 
> cannot read and understand such RFC).


Dilyan,

I didn't follow the latter portion of your message entirely, but yes, I 
think I understand the problems that DMARC filtering and reporting are 
intended to solve.

To your initial question, unless a bunch of other people speak up in 
favor of the split I'm proposing, it won't have WG consensus so we don't 
need to consider who does the editorial work involved.

-Jim