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

Alessandro Vesely <vesely@tana.it> Sat, 13 July 2019 17:33 UTC

Return-Path: <vesely@tana.it>
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 DD890120115 for <dmarc@ietfa.amsl.com>; Sat, 13 Jul 2019 10:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 MslCVaQiOY5G for <dmarc@ietfa.amsl.com>; Sat, 13 Jul 2019 10:33:20 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ADA7120108 for <dmarc@ietf.org>; Sat, 13 Jul 2019 10:33:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1563038535; bh=TXGRl2U76eYm4Uph42q/+ugvgGc4YzbyxKKJt1DHgO0=; l=1305; h=To:References:From:Date:In-Reply-To; b=BkG7Zuw6NiW+8M0ivnd+Dsi/y1+XoUGX8r14qYJLKXCKK/HKCdqOoKPiklWoHq/77 aiov0XnXV9lcDrvh64tCWsddDdGEfgL2J0JD0fhLPXX3hnkOAMPu6MQUvmTKhY626D sJU0R3YBmQGRnpeOihdQfCO8J9EdC9By3MC6DTgAwhpW2AIVeEeYIrTlFlBYp
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [192.168.1.100] ([5.170.9.203]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1.2, 128bits, ECDHE-RSA-AES128-GCM-SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC081.000000005D2A1347.00003D0F; Sat, 13 Jul 2019 19:22:15 +0200
To: dmarc@ietf.org
References: <CAL0qLwbbz_UhBLsURg=eXhRBC2g9OghiN==T9Uq9pFuLtd=b7w@mail.gmail.com> <CAOZAAfM9BPLz6UR1bLTrE30dsWLv3k=UNNbGDGCrAfT7Op7FGg@mail.gmail.com> <54eac0ab-985e-69be-5985-8a53c51c7580@tana.it> <1851683.DtEN5jD5Wj@l5580>
From: Alessandro Vesely <vesely@tana.it>
Openpgp: preference=signencrypt
Message-ID: <c94a1ccd-3d6f-6100-8401-90c78e8b0355@tana.it>
Date: Sat, 13 Jul 2019 19:22:15 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <1851683.DtEN5jD5Wj@l5580>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/8sPrDOWTxI9UxbgdSz-Fszaxl-0>
Subject: Re: [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: Sat, 13 Jul 2019 17:33:22 -0000

On Fri 12/Jul/2019 19:30:35 +0200 Scott Kitterman wrote:
> On Thursday, July 11, 2019 6:07:50 AM EDT Alessandro Vesely wrote:
>>> 2. If explicit call outs to ICANN/limited operator capacity to
>>> implement are needed
>>
>> Appendix B.1 lacks a criterion to establish enlisting.  Couldn't we
>> require an explicit statement about seizing DMARC reports in, say, the
>> delegation report?  Alternatively, that policy can be stated in a
>> well-known place under the delegation services URL, so that
>> registrants know what they do.
> 
> It's in the appendix because we don't have a clear path forward.  This is part 
> of the experiment.  We need to be careful though since different PSDs operate 
> under different authorities and controls, so there is a point beyond which it's 
> not the IETF that decides.


I should have written more clearly the two issues.  One is the
criterion.  I hypothesized that all what is needed to gran enlistment
to a PSO is that its policy to seize DMARC at PSD level be published,
so that registrant can learn about is before registering.  Is that
correct?  I mean does a public statement suffice?


The second issue is how to publish. In case the answer to the 1st
question is yes, would https://PSO.tld/.well-known/dmarc-psd/policy do?


Best
Ale
--