IETF Logo Mail Archive

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

"John R Levine" <johnl@taugh.com> Fri, 24 May 2019 14:37 UTC

Return-Path: <johnl@taugh.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 BFC5C12031D for <dmarc@ietfa.amsl.com>; Fri, 24 May 2019 07:37:56 -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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=nJp3w+Og; dkim=pass (1536-bit key) header.d=taugh.com header.b=U7nGKozY
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 frrsKlSgdtcg for <dmarc@ietfa.amsl.com>; Fri, 24 May 2019 07:37:54 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 4EA4A12031C for <dmarc@ietf.org>; Fri, 24 May 2019 07:37:54 -0700 (PDT)
Received: (qmail 48800 invoked from network); 24 May 2019 14:37:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=be9d.5ce801bf.k1905; i=johnl-iecc.com@submit.iecc.com; bh=HbfHmPnRcHCmzMo3a/J97+cHZgTnuQhNuA6T7gEOn5w=; b=nJp3w+OgZAYE/h058TMZeNCqINYViG62Bh1CPqvQ6ER0N/SrOALH3v+vZUYWflkBi7qSsvxBGPjYz/XYXYiwvbE1qiczx9/lqp/GGmVAeJSZPf5do2OtyI8BFr0+hcqVpIa9lbG5k6Y3zT+aGEjzhPbSOrMFmlK6g3IiN+otjpYzPygCoNhusr03iQmCbfcDUqW2r5dw9ktoZ4QOYAT7VwtVfnY9RSHW6llqcZ1QIYaPZDRFQu2qllJQBPk55G0c
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=be9d.5ce801bf.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=HbfHmPnRcHCmzMo3a/J97+cHZgTnuQhNuA6T7gEOn5w=; b=U7nGKozYn5AJVufpkErxUTxBONZJ9uP2TW71O46Gccz+mGIaOls9QUwwH1ljXCXoXPwnm9KNLno7ESy/Z5btTbZeicQRtqabTuJmrGFb7p5T7r0RToGP8t64SfBwAHc5P7vxEvScC3Oif2RXJmxPztmNmFiu3bVbUyCQLaM1F/q5ynz9hIP5M+YxA3ukiGfYIWjO3HNQJJ+DFGRCJhGkJsBuBIEihHlZcv6GBjPMkNe9Wjox5YwI8VfBqpbgsiBk
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 24 May 2019 14:37:51 -0000
Date: Fri, 24 May 2019 10:37:50 -0400
Message-ID: <alpine.OSX.2.21.9999.1905241036450.50141@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Jim Fenton <fenton@bluepopcorn.net>
Cc: dmarc@ietf.org
In-Reply-To: <ab587c42-dd2f-2403-999a-c7d559764726@bluepopcorn.net>
References: <20190523225213.C214620147B780@ary.qy> <ab587c42-dd2f-2403-999a-c7d559764726@bluepopcorn.net>
User-Agent: Alpine 2.21.9999 (OSX 337 2019-05-05)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/PZ21pH24c74QoYXDkD0pMWzwn6E>
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: Fri, 24 May 2019 14:37:57 -0000

> MTA-STS and TLSRPT started out as one document as well, and separated
> quite cleanly IMO. I'm not sure what kind of incompatibilities you think
> might be created.

That's because they separated before they were published, so there was 
nothing to be incompatible with.  If I knew what would break when 
reorganizing and rewriting a document into pieces, I could fix it, but 
since I don't, and nobody else does, let's not go there.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email