IETF Logo Mail Archive

Re: [dmarc-ietf] Comment on draft-ietf-dmarc-psd

"Kurt Andersen (b)" <kboth@drkurt.com> Mon, 11 November 2019 18:32 UTC

Return-Path: <kurta@drkurt.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 E7063120BE3 for <dmarc@ietfa.amsl.com>; Mon, 11 Nov 2019 10:32:15 -0800 (PST)
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, 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=drkurt.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 L4j0XOO1jzuQ for <dmarc@ietfa.amsl.com>; Mon, 11 Nov 2019 10:32:12 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 7AC39120BE7 for <dmarc@ietf.org>; Mon, 11 Nov 2019 10:32:12 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id i13so14333658ioj.5 for <dmarc@ietf.org>; Mon, 11 Nov 2019 10:32:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K03ioOeyfCbwgfZY+U+EjgM7ENyGoGSI6tiFee9ZttQ=; b=I6k/PjYuRwYwsCNs5rVDCUjXaq1CmOIhXaLTSpf+UvwnyyPhQAKBGqzMoPDZEG2lW3 Ni6MgRfu050s8niPwCwcgLVXjS0kxm6Cv12pkfabROLTEPtTd2MyKpnBIcPiLYUz9Pob jVkJ4ZFTOvbmqGR//4ii2AY4F4GJTA22jxSxA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K03ioOeyfCbwgfZY+U+EjgM7ENyGoGSI6tiFee9ZttQ=; b=sJcUP8eMxbdlnac5WB/+pL53EOhXnAD4NR6zBj0jVEdBKQhIgG/DwN2i7o5iYf5AHt UW972pkop0MUvK5UBQXF10vD6wQ8KPb7LEqUF+i4XkS7Sc7WuXsvbHuaufUtF3lkYkoh 87a3/nVBEJrjZUaZdA9Vo0PPPleOgxkHEG+xWNUIVk+V2CxiBUrdo/7ujvz3SEZTqLgg P6odS34S7sLGrH/gtWapz0+n4gDo7MI5oB4ljZ1nRkTSfaF6Q8TFs0DbPL1BchvR/KEb sRNTQVsrFHp1VdgtpYk/QJ1Fv0auH0eZfms+39+jCRb7hK32MzWqseAMYVwe0FereQHC 9xAA==
X-Gm-Message-State: APjAAAW34iSguddiR6g99Go2unKenIpIxXbM6knqzod2GgpmPXPJr03Q 4s+n71gePhase9LdRv6xgEllvKHdRpnU3b2Ql+eBcEJbhs0=
X-Google-Smtp-Source: APXvYqwNF3VQhIhsT9N4O+ePTgTMH8EMRgUXz5W5nCg9P0bxPI/vGAUkvSS8wT7JWfaT9AV3n0iieQIxnWfwWmfB+Mk=
X-Received: by 2002:a05:6638:73a:: with SMTP id j26mr26751143jad.116.1573497131462; Mon, 11 Nov 2019 10:32:11 -0800 (PST)
MIME-Version: 1.0
References: <728d7df1-d563-82f4-bfb3-a65a75fdd662@gmail.com> <CAL0qLwacbAT04tckpPcRcnOt=1QByOBeJ7uDf6rNK6NRwtxZYg@mail.gmail.com> <ffa2bf72-3024-237b-86ae-9cc04babeec6@gmail.com> <74a0ea49-7a46-4eb6-c297-cd703f63bd1b@gmail.com> <CAL0qLwbp2hNrgF_xxhKRRODQ6HP=U5_K-r3Wtm1wJZOZcKup3g@mail.gmail.com> <9DE9E7DC-FE60-4952-8595-B2D087A6B780@kitterman.com> <CADyWQ+GSP0K=Ci22ouE6AvdqCDGgUAg3jZHBOg3EwCmw=QG84A@mail.gmail.com> <CABuGu1obn55Y2=CuEYRYCEO3TYYNhYTsdkesQ67O61jRyfO=wA@mail.gmail.com> <59947cf1-1851-af56-536e-f78530e79dd2@tana.it>
In-Reply-To: <59947cf1-1851-af56-536e-f78530e79dd2@tana.it>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Mon, 11 Nov 2019 10:31:52 -0800
Message-ID: <CABuGu1rsaFojGL4P8i3116DEo6gh6LY87ti9ayZLfdC+z0AY9w@mail.gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000939973059716598e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/I7v9_hOCVWkS1Njj7Lej6p3XSWs>
Subject: Re: [dmarc-ietf] Comment on 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, 11 Nov 2019 18:32:16 -0000

On Mon, Nov 11, 2019 at 9:50 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Mon 11/Nov/2019 16:46:17 +0100 Kurt Andersen (b) wrote:
> >
> > I don't think that it is fair to say that anyone who refers to the org
> domain
> > concept as cited in the DMARC spec is necessarily invoking the PSL.
>
> Agreed.  The PSL just happens to be the only valid tool to do that.
>

Which was not what I thought Tim W was talking about...


> For various reasons, large organizations administer many apparently
> unrelated
> domains.  For example, _dmarc.youtube.com has a rua mailto ending in
> @google.com.  We cannot infer an OD from that, but I think the concept is
> clear.
>

I don't think this has anything to do with the PSD proposal either. Why do
you bring it up?


> > As to the proposed "let's run this as an experiment pending DMARCbis", I
> don't
> > see how that satisfies Dave's concern about creating new work for
> receivers in
> > order to help a small set of domain (realm) owners. I'm not opposed to
> it, but
> > I just don't see how this solves the issue.
>
> Isn't that an ICANN problem?  For the time being, dig _dmarc.bank txt
> returns
> an empty NOERROR response, while _dmarc.gov.uk returns a valid record.
> The
> latter is a Nominet, already solved problem, AFAICS.
>

If it was a solved problem, then we would not need a PSD (or realm) I-D and
this whole discussion would be moot. What ICANN does and does not allow is
out of scope for the IETF/protocol work (though I do acknowledge that ICANN
may consider protocol factors when making decisions - or I would hope that
they would).

--Kurt

v2.23.0 | Report a Bug | By Email