Re: [dmarc-ietf] Amazon Comments to DMARC Extension to PSD

"John Levine" <johnl@taugh.com> Thu, 18 July 2019 05:28 UTC

Return-Path: <johnl@iecc.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 13E26120144 for <dmarc@ietfa.amsl.com>; Wed, 17 Jul 2019 22:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level:
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=Uop+IbXr; dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=jrp1G/EC
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 OmQeTjqyT-tA for <dmarc@ietfa.amsl.com>; Wed, 17 Jul 2019 22:28:24 -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 A7792120141 for <dmarc@ietf.org>; Wed, 17 Jul 2019 22:28:24 -0700 (PDT)
Received: (qmail 76434 invoked by uid 100); 18 Jul 2019 05:28:22 -0000
Date: 18 Jul 2019 05:28:22 -0000
Message-ID: <qgp01m$26nk$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:cleverness; s=12a8a.5d300376.k1907; i=news@user.iecc.com; bh=gQIvLPHZ2NhULBnpaWzGfF18uaLwEgv3HZgyuLcxFy4=; b=Uop+IbXrsDxOkTe0qpavox/6KFHEb/VtPygCPgRRYM/Dv0kfQddxqKmigL/9tt+IGpGSsHoLenVaLZ3L+enGUL51mpbz9bSF4Drd9LwHh0mRogttrQSGvRkHPDBJD16u0aHpCTUKQC2305x56HGZd5HfvuPsl9rTfWthPxF0s7mjuCih6OMi85VrmgI2yfzhlLK57FOaF+qb/ndhcaIJvK1sPNvH0gJfx5Mts17hi/S6C3HAhKO+UX+NqL1xy5ZK
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:cleverness; s=12a8a.5d300376.k1907; olt=news@user.iecc.com; bh=gQIvLPHZ2NhULBnpaWzGfF18uaLwEgv3HZgyuLcxFy4=; b=jrp1G/EC6OySJVW+nmXfaNmH/7wZlFig521bd2PzqWBZpvvmYsD/GGW8v2Nz2XcqPq6ZHSt2xUnkmZxgWnLnP7DP0M5TWIDUbX6uRN4UuoRLRczfuWMWGXygKO1Msz5rzVOkzYKTw4MCss33EMuGZmdnvjLI07E1dBHQtKIpPQ0bJpSVTZPqck4y9EsmuZcW5Jd21j05IWIVCM9pOU2ebX0BVh5zouK1T+eWAKQCta9nYyQDypqatgLXJMuJhOfD
Organization: Taughannock Networks
References: <132DD4E4-616A-47F5-A4A3-681067C86DA6@amazon.com>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/xP0KAXip-EvKWfFDO3EgoPtClD8>
Subject: Re: [dmarc-ietf] Amazon Comments to DMARC Extension to 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, 18 Jul 2019 05:28:26 -0000

In article <132DD4E4-616A-47F5-A4A3-681067C86DA6@amazon.com>;,
Flaim, Bobby <flaim@amazon.com>; wrote:
>-=-=-=-=-=-
>Amazon supports this draft and effort .
>
>This current DMARC extension (IETF DMARC PSD) draft<https://datatracker.ietf.org/doc/draft-ietf-dmarc-psd/> would make it
>easier for our direct customers (registrants) to setup a common DMARC policy for all their subdomains.

It looks like you may be misunderstanding what PSD is.  

If someone registers, say, pickle.deal, right now they can put an sp=
tag in the record at _dmarc.pickle.deal which sets the policy for
<anything>.pickle.deal.  That's the way that organizational domains
work.

PSD lets you publish _dmarc.deal and have that apply by default to the whole TLD,
<anything>.deal and <any>.<thing>.deal and so forth.

R's,
John
-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly