[dmarc-ietf] Working Group Last Call: draft-ietf-dmarc-psd

Craig Schwartz <craig@ftld.com> Mon, 15 July 2019 16:24 UTC

Return-Path: <craig@ftld.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 53772120176 for <dmarc@ietfa.amsl.com>; Mon, 15 Jul 2019 09:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=ftld.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2X6GXkjtJTeB for <dmarc@ietfa.amsl.com>; Mon, 15 Jul 2019 09:24:43 -0700 (PDT)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBDC412011C for <dmarc@ietf.org>; Mon, 15 Jul 2019 09:24:42 -0700 (PDT)
Received: by mail-vs1-xe30.google.com with SMTP id 190so11773950vsf.9 for <dmarc@ietf.org>; Mon, 15 Jul 2019 09:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftld.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=lTb4lYYwZBeNP2hTXPM3xUM7P+s4CzHc3a03+6an8UE=; b=eIA0kYZME3qMASJA/jVwnaWURLLBRhcWuzQ1sIZN4dbDKcElFLb1QZePLCItOW0KZX dTj0ekX6C7il+VjT6cZ0WSowukhklg7nyYtgGMkdtIWzhteoV2K/VrmalbHoWUooHc+A UQyoxnGHKvr2aANLTXvrfs8zkmDzppgsJxcOE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lTb4lYYwZBeNP2hTXPM3xUM7P+s4CzHc3a03+6an8UE=; b=H3AwfGJMA7bDSZ18c7POaONnPbgcUuzf+9hDfNRqrkvPvQeACPtGLI2iTLvGTt65Lm 3Y+5Mcay66yXndDw5lASzb/yibPg6BEMusqLrblLk5g0a5lcY+B782+nwkltAcFfECNb JaIhXya4+1PLjLzOdO9kj9rGU1JNGAHEE+pc+vRYGvHBYJE2JaWLPT5uw8uRXRMTovjV VwGImRkxEBesWXhO62YvcvVcn1NarMh7if1KLlBQAtGjwADQjl6Gsre20D4o/UcMc4Rg 7BbyZAgGUE4k25adYHcSwUtsmch7jMjF04bzY4ZT/i0UpswRiNoe8waYpWbJ8cE8TAg6 MSlg==
X-Gm-Message-State: APjAAAWZ7TbtNGm8Ic0Fmls+5xNbopvnCvdh6m+kgEbIAtTDwUTkDq7k iO483vUaP6mMDZlxKiPd5QaSMWqTwcONjzar1A+JRljgfrE=
X-Google-Smtp-Source: APXvYqwAeZ/EN9g8gSVG7syer+xMTXN8zCu2lNMjHxJE7hOX73BPovjJgKtFQghII7ibARuj+gvyS/xA/Xd0Zy9oREI=
X-Received: by 2002:a67:f941:: with SMTP id u1mr10434750vsq.60.1563207881463; Mon, 15 Jul 2019 09:24:41 -0700 (PDT)
MIME-Version: 1.0
From: Craig Schwartz <craig@ftld.com>
Date: Mon, 15 Jul 2019 12:24:29 -0400
Message-ID: <CAJ+U=1riv86yEXLvFVJLHaCAUBMD2cfkgogOCh9_xT=5_VBJSw@mail.gmail.com>
To: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007c3c44058dbab2e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/sw50iND6rZqbEEm16rFDKFsgERU>
Subject: [dmarc-ietf] Working Group Last Call: draft-ietf-dmarc-psd
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, 15 Jul 2019 16:24:45 -0000

On behalf of fTLD Registry Services (fTLD), Registry Operator (RO) of the
.BANK and .INSURANCE gTLDs, I am grateful for the work Scott Kitterman has
done for us with draft-ietf-dmarc-psd and others who have worked diligently
to advance this effort.  fTLD started discussing DMARC for gTLDs/PSDs with
an internal working group in June 2018, which led to the publication of the
first Internet-Draft (ID) in October 2018. We continue to meet regularly to
evolve the ID inclusive of comments and concerns raised by members of the
IETF DMARC Working Group.

As the RO for two of the most trusted and secure gTLDs on the Internet, we
have and continue to explore ways to enhance security for registrants using
.BANK and .INSURANCE and the consumers they serve. Prior to the launch of
our TLDs in 2015 and 2016 respectively, we specified several Security
Requirements, accessible at https://www.ftld.com/security/, that must be
implemented for domains in our zones inclusive of Email Authentication
(i.e., DMARC plus SPF and/or DKIM (though we advocate both). fTLD regularly
monitors for compliance with all requirements and takes enforcement action
when necessary.

fTLD began our exploratory work more than a year ago and believe DMARC for
PSDs will provide a variety of benefits including, but not limited to:

- Threat intelligence into sources of abuse;

- Protection for NXDOMAINs against nefarious e-mail borne activities;

- Brand protection; and

- Compliance enforcement for PSDs that have policy control for their

We appreciate that for PSDs under contract with ICANN there is currently a
prohibition of the activity presented in the ID. Notwithstanding this,
there are other types of PSDs (e.g., country-code Top-Level Domains
(ccTLDs), TLDs not governed by ICANN contract (e.g., .MIL, .GOV, .EDU))
that can experiment with DMARC for PSDs. When the IETF work is sufficiently
advanced, fTLD anticipates pursuing permission from ICANN to implement
DMARC at the TLD level as soon as practicable.



Craig Schwartz
Managing Director
fTLD Registry Services | .BANK & .INSURANCE
Office: +1 202 589 2532
Mobile: +1 202 236 1154
Skype: craig-schwartz