Re: [dmarc-ietf] DMARCbis issue: Separating reporting and policy
"John R Levine" <johnl@taugh.com> Sat, 25 May 2019 21:30 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 8E0CE12011C for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 14:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=UtDmKhap; dkim=pass (1536-bit key) header.d=taugh.com header.b=RqEuf7R+
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 wBqxxqEGIAn5 for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 14:30:35 -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 7B3A11200F3 for <dmarc@ietf.org>; Sat, 25 May 2019 14:30:35 -0700 (PDT)
Received: (qmail 20195 invoked from network); 25 May 2019 21:30:33 -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=4ee0.5ce9b3f9.k1905; i=johnl-iecc.com@submit.iecc.com; bh=F2P/BpnthA002i5sNRdhyn6Ri9dwdiTNPjbb4ulm0QQ=; b=UtDmKhapw39LI5Lc+LZCN7pii/YVL8IoePX3iP4N3KWaUdunFmPMmIm8T+qmnWxr+JldHR9PoLwLFbhwvyhK2ldvmoX1MoUgbu+GlI3E2TYb1eIbUh1jpDA9LqmpSvdzk0NwN9CQH3n+ojUmC13djwQwEhoIAYov3/KpNVo3h4hFaAxMpm5R3aqUl/cuGDrPYzXJYBfTlm9DecKq+RZhgi0HS/iDmlJ5gew8sXs18BrYH1E3kdDubo3sEqeqZRbf
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=4ee0.5ce9b3f9.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=F2P/BpnthA002i5sNRdhyn6Ri9dwdiTNPjbb4ulm0QQ=; b=RqEuf7R+0OBjNNhf3UfOg7giJSPiQSpit9p37R8npNDzvHHMbKiBcQm1Qw0NTf5zMceLmvOH7O113vBTxpsJUlttees9vHMxp+YbtiUPgLlshXIuxT+XXQ5T7VyJFP2HepGgeojeE1tS5I8bun0d0bu9w4mCsyp5LoQ4XDCcenWWpmaATDi4VLJI9jG+3MUILjF8ifZ8UVItzlnNQ2Ar2mnizGCJRGhuc6D5aBDuvTS+l4NsBGOPBfYhrgtXpMAZ
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; 25 May 2019 21:30:33 -0000
Date: Sat, 25 May 2019 17:30:33 -0400
Message-ID: <alpine.OSX.2.21.9999.1905251729260.56019@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: dmarc@ietf.org
In-Reply-To: <789c58b1-7b45-3af0-dd1b-aca0c415db02@gmail.com>
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>
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/7F2oiU9e_J1s7e1sPCys4JXUvWw>
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: Sat, 25 May 2019 21:30:38 -0000
On Sat, 25 May 2019, Dave Crocker wrote: >> 2. Along similar lines, I get confused when I hear that x% of {some set >> of domains} has "deployed DMARC". What does that mean? Have they > > Ultimately, you are asking marketing questions, not technical ones. Right. It's easy enough to imagine soemone handing out Official DMARC Compliance certificates, but that someone sure wouldn't be the IETF. Regards, John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly
- [dmarc-ietf] DMARCbis issue: Separating reporting… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dave Crocker
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Scott Kitterman
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Hector Santos
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Peter M. Goldstein
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dotzero
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Alessandro Vesely
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Brandon Long
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Luis Muñoz
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? John R Levine
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dave Crocker
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John R Levine
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? Dotzero
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dilyan Palauzov
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dave Crocker
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Dave Crocker
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? Alessandro Vesely
- Re: [dmarc-ietf] DMARCbis issue: what is DMARC ? John R. Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… John R Levine
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Jim Fenton
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Alessandro Vesely
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Hector Santos
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Murray S. Kucherawy
- Re: [dmarc-ietf] DMARCbis issue: Separating repor… Tim Draegen