Re: [dmarc-ietf] Working group next steps

Scott Kitterman <sklist@kitterman.com> Fri, 29 March 2019 17:18 UTC

Return-Path: <sklist@kitterman.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 9AC6E120467 for <dmarc@ietfa.amsl.com>; Fri, 29 Mar 2019 10:18:53 -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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=G4WrqBNk; dkim=pass (2048-bit key) header.d=kitterman.com header.b=hLgZwoLo
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 TQvaYABJHNqH for <dmarc@ietfa.amsl.com>; Fri, 29 Mar 2019 10:18:51 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB9412039F for <dmarc@ietf.org>; Fri, 29 Mar 2019 10:18:50 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 2414BF8096F for <dmarc@ietf.org>; Fri, 29 Mar 2019 13:18:49 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1553879928; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Rd4QuxjPtMPhFrvQRA6lrszydgCULSr070d3VFScBrI=; b=G4WrqBNkZeUQN+NPTxz8uNG+kaB2xc37ONSCX2SZu3nGVx31fYiiwxqN 22inVB44tHcZWvacX3VqxPnDhYzNBw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1553879928; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=Rd4QuxjPtMPhFrvQRA6lrszydgCULSr070d3VFScBrI=; b=hLgZwoLoByofAp7XIfxAb9k41wgY69MreLmR28HKCB9aTSZGfmpE0XKv 7QSJGV+MBsS5/yOA+iETRECt2jSrv24PUoDGRKAIijdVRsQ1EizhJ3YSZg WULmLG93IqwK56cuKC3gNebZoXgFFJogsTaaLLzJbSU9MRSupZGZ90Nhr1 a1dt553evJfl7BrcZbtaEyQX+ulpaNkEsfBMQ1bQBTI/k8+6xobsyRzJgq SmgDUUxwiMhguGzRPIIeeanXMYNElfqHDZE1Dr0s4spfnFenAN8iy9C8as 5v8VbZSgEwb1ICN4wO83VkDssCQmUl8l6sf0bGpm31Q4FTU3ySU6Kw==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id E9333F80864 for <dmarc@ietf.org>; Fri, 29 Mar 2019 13:18:48 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: IETF DMARC WG <dmarc@ietf.org>
Date: Fri, 29 Mar 2019 13:18:47 -0400
Message-ID: <3802074.4RGYGbXOYh@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-164-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <LO2P123MB22857A6A1EDD9D54A817C4F5C95A0@LO2P123MB2285.GBRP123.PROD.OUTLOOK.COM>
References: <CAL0qLwaPG+CcuMGsJjdJM=x4bigSXvRAHxAf3nk9krknJbtUqw@mail.gmail.com> <LO2P123MB22857A6A1EDD9D54A817C4F5C95A0@LO2P123MB2285.GBRP123.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LP9D7iuJX9giObz2D2n8L2UtOE0>
Subject: Re: [dmarc-ietf] Working group next steps
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, 29 Mar 2019 17:19:02 -0000

On Friday, March 29, 2019 05:14:31 PM Ian Levy wrote:
>   *   The working group should, in the short term, focus on development and
> completion of draft-ietf-dmarc-psd.  Among the questions to be answered is
> its urgency
 
> I’m certainly keen to see that progressed. As we’ve rolled out DMARC across
> gov.uk subdomains, we’ve seen criminal behaviours change in response. Some
> of you may recall we asked for help a while ago for ideas in generating
> SPF/DMARC records for non-existent subdomains. Well, that’s running and we
> answered 430,000 queries for them between August and November last year
> (more current data coming). We do know that the effect of synthesising
> these records means that some receivers don’t honour them, so getting a
> more acceptable way of controlling subdomains of a PSD would be good. As we
> push for wider DMARC adoption and other authentication measures, we’ll need
> to do this much more widely so it needs to be easy.
 
> I’ll also offer gov.uk as an experimental ground (within reason!).

Excellent.  I've listed it in the experimental registry at psddmarc.org.  
Since you already had a live DMARC record for that domain, people can 
experiment with this now.

Scott K