IETF Logo Mail Archive

Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd

"John Levine" <johnl@taugh.com> Thu, 27 June 2019 15:56 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 AAC931202B5 for <dmarc@ietfa.amsl.com>; Thu, 27 Jun 2019 08:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
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, SPF_HELO_NONE=0.001, 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=VjfLn4ng; dkim=pass (1536-bit key) header.d=taugh.com header.b=LEzAi/CA
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 OROIV4OLXqdb for <dmarc@ietfa.amsl.com>; Thu, 27 Jun 2019 08:56:40 -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 A8E451202B1 for <dmarc@ietf.org>; Thu, 27 Jun 2019 08:56:39 -0700 (PDT)
Received: (qmail 72682 invoked from network); 27 Jun 2019 15:56:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=11be7.5d14e735.k1906; i=johnl-iecc.com@submit.iecc.com; bh=EOAfuG+CINm9MOtNgc/AeB4TWkDB4k98ivcv3KWBd3w=; b=VjfLn4ngoBimLfPJJufJImwjhoWxohXhatXntSwikyb4aOcbyXwwfp9Oh0rJUJnKnlALKSaRTaajtbP4op36yi3eBWaGX7dMNUJTP8q1EuLR2o+bp2P3ADaQFTRW0Wb8pqjfx9PxaMDrHNDvRFl9rCSvDxyCFDa+h7MOTTbP+oU6We8TXImWnHehIJoGa0B7O+slcQesQi/wW3RzBTDhx+8sRbIMDxhUX11Q6w9xuOoCDNR7DFPCFn+4qVl/q/Vp
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:mime-version:content-type:content-transfer-encoding; s=11be7.5d14e735.k1906; olt=johnl-iecc.com@submit.iecc.com; bh=EOAfuG+CINm9MOtNgc/AeB4TWkDB4k98ivcv3KWBd3w=; b=LEzAi/CAfk8SAu0rXYiHRTEhTMYvMpZwc+ci2zZPEwow2EcI1CzH30IndkrtVYwSU0im8+it8Q/Kt7ilBDlHydD5tqvBvoZZQaKl0yUHWw1g304e0VKRSN4dRnDBCT92QJc2/KYFetsitQ2f87LkuEz+TrLZk+8p0tobqbJgFvuWwWdRcVaG84bX/CzaBqXUfCldXmfTi9j1i5GGn0AlbZ+NQlVygZGSqLZSieOrtm9seAYThvtzkiBZM/tDpXr1
Received: from 105.67.133.47 ([105.67.133.47]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-128-GCM AEAD, johnl@iecc.com) via TCP; 27 Jun 2019 15:56:36 -0000
Date: Thu, 27 Jun 2019 16:56:28 +0100
Message-ID: <20190627165628.72678.qmail@submit.iecc.com>
From: John Levine <johnl@taugh.com>
To: shollenbeck@verisign.com
Cc: dmarc@ietf.org, "Murray S. Kucherawy" <superuser@gmail.com>
Importance: normal
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LNNoxw2QsnBqnxzf9xXrQpmzjtQ>
Subject: Re: [dmarc-ietf] PSDs in 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: Thu, 27 Jun 2019 15:56:43 -0000

I wasn't thinking this would go in the doc, just for background.

Autocorrectly,
John
On 27 Jun 2019 12:23, "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote:
>
> > -----Original Message----- 
> > From: dmarc <dmarc-bounces@ietf.org> On Behalf Of John Levine 
> > Sent: Thursday, June 27, 2019 6:52 AM 
> > To: dmarc@ietf.org 
> > Cc: superuser@gmail.com 
> > Subject: [EXTERNAL] Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd 
> > 
> > >I concur.  Does anyone know of such a policy statement from ICANN?  I 
> > >don't recall it being present in, say, any of the DNS RFCs, but there 
> > >are so many of those now... 
> > 
> > Hi from ICANN 65 in Marrakech. 
> > 
> > The gTLD registry contracts say directly or indirectly what's allowed in each 
> > TLD zone.  Here's the language in the base registry agreement that the new 
> > TLDs all use: 
> > 
> > https://newgtlds.icann.org/sites/default/files/agreements/agreement- 
> > approved-31jul17-en.html#exhibitA.1 
> > 
> > For the older TLDs, notably .com, the contract refers to Consensus Policies, 
> > which are at https://www.icann.org/resources/pages/registrars/consensus- 
> > policies-en 
> > 
> > One of those policies is the Registry Services Evaluation Policy 
> > (RSEP) which is at 
> > https://www.icann.org/resources/pages/registries/rsep/policy-en 
> > 
> > Here's the list of RSEP requests: 
> > 
> > https://www.icann.org/resources/pages/rsep-2014-02-19-en 
> > 
> > Adding a dmarc record to individual TLD would need an RSEP, for which an 
> > RFC would likely be helpful but probably not essential.  The RSEP process for 
> > things that are not politically controversial is not particularly hard. 
> > 
> > Adding them to all of the TLDs could be a new consensus policy, or maybe a 
> > change to the base agreement.  How to do that is above my pay grade. 
>
> The ICANN minutiae is probably way more detail than is needed in the document. I'd be more comfortable if there were text in the Introduction along the lines of what Murray said in his last note (paraphrased here slightly): "Please note that today's operational and policy reality prevents this experiment from being deployed globally.  If the experiment shows that PSD solves a real problem at a large scale, the results could prove to be useful in the development of policies outside of the IETF that would permit its ubiquitous deployment". 
>
> Scott 
>

v2.23.0 | Report a Bug | By Email