IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 27 June 2019 11:23 UTC

Return-Path: <shollenbeck@verisign.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 6E300120043 for <dmarc@ietfa.amsl.com>; Thu, 27 Jun 2019 04:23:44 -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 (2048-bit key) header.d=verisign.com
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 EXQI9I72HF03 for <dmarc@ietfa.amsl.com>; Thu, 27 Jun 2019 04:23:42 -0700 (PDT)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 310681200B8 for <dmarc@ietf.org>; Thu, 27 Jun 2019 04:23:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2184; q=dns/txt; s=VRSN; t=1561634622; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=fFmMcMQk7ihrbVoU6aD+vt4AB3q3H3VZCDBVm3rmngo=; b=Cc0BZksIn7d2AGRI/WBkHJW3jiORrZkiidwnBmwNAt91hllN0BzRBOX1 ASH+XA7VqT0WZ9E/z2w39pDXL29gXyWMXb0G8ce6V1RoXYeQMAxDNrtDg /vNBdHekY7Kms6YNZ0MMOnX69c6lJAYVtPqM3SFlkXC4rNrZUO6h7OkQ5 cvUQNGTFg0YdG6go1K/qd2ZrIEs6SWr5BxzdV38FuKCvDIeGp2w8BUZNo 4R2H32U+PQNtaFfksaT0/XKtDUPdbN/G66SqnqnvTJN4BSd9Zm5h7X4ah fhah7E9A0tiZy2t1zZnUKkRAekMLYaJcPA0Mv64hWpz9utf7RvNpxQNxe A==;
X-IronPort-AV: E=Sophos;i="5.63,423,1557201600"; d="scan'208";a="7861459"
IronPort-PHdr: 9a23:6pW8PBFEgylFcJqxAo9qZZ1GYnF86YWxBRYc798ds5kLTJ76p8W+bnLW6fgltlLVR4KTs6sC17OM9fmwEjdQqdbZ6TZeKcUKD0dEwewt3CUYSPafDkP6KPO4JwcbJ+9lEGFfwnegLEJOE9z/bVCB6le77DoVBwmtfVEtfre9FYHdldm42P6v8JPPfQpImCC9YbRvJxmqsAndrMYbjZZ8Jqor1xfEoXREdupVyGh1IV6fgwvw6t2/8ZJ+7ihcoe4t+9JFXa7nY6k2ULtUASg8PWso/sPrrx7DTQWO5nsYTGoblwdDDhbG4h/nQJr/qzP2ueVh1iaUO832Vq00Vi+576h3Uh/oiTwIOCA//WrKl8F/lqNboBampxxi347ZZZyeOfRicq/Be94RWGxMVdtTWSNcGIOxd4sBAfQcM+ZEoYfzpFUOohm/BQawC+3gxSRFhmPv3a04z+gtDR3K0BImEtkTsHrUttL1NKIKXOy7zqfIyjHDb/dI1jf784fHbAwuofKUUbltbMTe1U4vFx/ZjlmetIfoOCiV1uQKs2if6+pvS+SvhHU5pA5toTii3dkshZfThoIU0VDE9Cp5wIAvKdKkT057ZMepHZ1NvC+UMIt2R9ktQ2BuuCsizL0GvoK7czIRx5Qjxx/TceCIc4+N4h77VeaePS13hHRjeL6lgBay60egx+vhXce3yFZHtjdJnsXWunwQ1RHe5NKLRuZ980qvwzqC2APe5vlZLUwoj6bXNpwszqIqmpYOvknOHTX6lFj1gaOOeEUr5Oul5/jib7jjpJKTK5N4hRv7P6gzhsOwHeE1PwgTUGeF9+Sx0bnu8lDkT7pUiPA9j7PXv4rAJcsBo660GwpV0oE+5BmhFzqmy9EYnWUfLFJCZRKHk5DlO1HQL/D8Cveym0mhnitzyfzbPrLvGprDIXnfnLv8Z7p99VJTyA0pzdBH/Z5bEKwOLOjtWk/rr9zYCAU1PBCzw+biENl914UeVnyTAqKBLa/erUWE6v8tLuSCfoMZpTbwJvY/6/PhjnI1gVodcrOo3ZsTZnC4BPNmI0CBbHr3gtcBFmMKvg4gQ+zsk1KNTyJcZ3WpUqIi+D47EoOmDZzCRoCihryNxju0HppTZmxeEFCDDW/od5mYW/cLcC+SIMhhkjwCVbilUIIhyQuhtBL1y7pnNObb5ioYtZf73thv++LTjQ0y9SBzD8mFzm6NSnt7nnkUSDIt3aBwv1B9ylmZ3ah/mfxYGsRZ5+lVXQciKZ7c0+t6BsjpWgLcZteGVkymQsi9AT4vVNI82NAOY0NnFNWjihDPxTalA7gQl+/DOJthuKDb3371D9p01nnGkqImihNuFslINWuirrJ26gfTQYXOlhPd3+ymcK0G1wbM+XuNi22UswsQBAJ1WL/OdXESekWQqs72sBDsVbirXP4HNQ9FxMiIJ6BJLpXShlJaWL2rbM/eZGa1lmG6CB2L7q2Bdovxemobmi7aDR5XwEgo4X+aOF1mVW+aqGXEAWk2GA==
X-IPAS-Result: A2EJAACVphRd/zCZrQpkGgEBAQEBAgEBAQEHAgEBAQGBVQMBAQEBCwGDAIEsCpkQiUuPIoF7CQEBAQEBAQEBAQcBIwwBAQKEPgKDIzYHDgEDAQEBBAEBAQEEAQEBAosgDII6IhxNawEBAQEBASMCDWMBAQEBAzo/DAQCAQgRBAEBHxAhER0IAgQBDQUIgxuBagMspxeENgMLAQI7BAFAgkENgh8GgTQBi3WBQT6BEYMSPoIaRwGHRASMOp0tPwMGAoIXhlKJMoNpI4IrhxeOHI0phziBcI12AgQCBAUCFYFXAoIIcFCCbIJNF4hihT9yjguBIQEB
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 27 Jun 2019 07:23:40 -0400
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.1713.004; Thu, 27 Jun 2019 07:23:40 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "johnl@taugh.com" <johnl@taugh.com>, "dmarc@ietf.org" <dmarc@ietf.org>
CC: "superuser@gmail.com" <superuser@gmail.com>
Thread-Topic: [EXTERNAL] Re: [dmarc-ietf] PSDs in draft-ietf-dmarc-psd
Thread-Index: AQHVLGCulBQe5GmoB0y7GawpTRvjMaavlxEA///CkIA=
Date: Thu, 27 Jun 2019 11:23:40 +0000
Message-ID: <0d4e70733ed0472eb80fd5150f4b5534@verisign.com>
References: <CAL0qLwYzTVRMHUucfcYPNvxwX6Dd10qGN7A=6CyQ5q12GcAq+Q@mail.gmail.com> <20190627105217.48BA5201676392@ary.local>
In-Reply-To: <20190627105217.48BA5201676392@ary.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1jAgGtNiyR3YuvJg1dciWVHU2Pk>
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 11:23:45 -0000

> -----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