Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.txt

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 18 February 2021 17:10 UTC

Return-Path: <superuser@gmail.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 DC82A3A1486 for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 q3BfSnfK-aaX for <dmarc@ietfa.amsl.com>; Thu, 18 Feb 2021 09:10:50 -0800 (PST)
Received: from mail-vs1-xe2e.google.com (mail-vs1-xe2e.google.com [IPv6:2607:f8b0:4864:20::e2e]) (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 10ECF3A146D for <dmarc@ietf.org>; Thu, 18 Feb 2021 09:10:50 -0800 (PST)
Received: by mail-vs1-xe2e.google.com with SMTP id y123so1253975vsy.13 for <dmarc@ietf.org>; Thu, 18 Feb 2021 09:10:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=M21nSrq/TEqLOPvfbXXLlnOLUiYtngB+tYfW95UqrqQ=; b=f8iliBTSCNG2fuGL/TFyMNuBdHA9JLalYEDub/VpaU7tUW1ypHge3x5yg4Lv13/NO/ wiJQckBFcwsOjz5du/EP4QZY7YThxp2sltDT/wDIz9UrOt4dOC9zPtXsPlvKT3t5R+fe snd6vPcEObzKatM0rZ265gv9lpyBwZSTeaG5UYgMWO/sdJk1jQNglf0gBuO6BxfVIkBQ DV2aGglVYOKP+hZsx2pextDdYfw/b5Db4tRgC6Sc74fxInyDeUevrJUB0o4kPJ+2jidH 62KpNrZNBGoWoc/7LLzzJkpw11g1L+BVdT/HG7l9B0AXN6+ukxLEkYTFo0hHNo5xJz1I 5VDw==
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=M21nSrq/TEqLOPvfbXXLlnOLUiYtngB+tYfW95UqrqQ=; b=aLPTM6B6MJY9+nOafua1NX35TKAipNsL0aTZFALCnp1BUwGS6fP2zgPytxQbPeYke8 c9FrILNdeYjPl3+n7rSUzVQk7F1Of7m/5EvGkX9pWQ0aj81XtG4w6utFy38cxhKoFvKw m+Ww2mj+5gy0QgfQopvudjT1YP1KkjuFPc9O4YQJnB5SIKbHVua9IEjS+LjQU6JkLuiY Oa0TSyNK1bUnJsp56ZlkTD9x1BvCoJZLZA88Q7vZBbZGhRq9HVBGAIf8JhNQGAKNZpkf DebdfKE2chdPMzeJSu43gjKPfY5x4RvFi1c6OqDQxx2zWlTMJpTGjuQvTsFsVCKFQiFA r3sQ==
X-Gm-Message-State: AOAM531gkw9tslk4yypVOK3y/p6JwoRLlsQzYg4lvboySsNwFyL1ZLT4 s514fVZJxUDzz7GwH3sGnhWTQt+tyQWmOM/Qq2c=
X-Google-Smtp-Source: ABdhPJy5+bYO/zXBr4y1pD9WWeR72PkNMj5mbH24vYoM8ZAvMKJhAA7s/0TsyV2Hd5sYK5m1qTiNDO3pit8FBeBIYfg=
X-Received: by 2002:a67:441:: with SMTP id 62mr1243129vse.0.1613668248811; Thu, 18 Feb 2021 09:10:48 -0800 (PST)
MIME-Version: 1.0
References: <161144436332.13490.10651420808048876097@ietfa.amsl.com> <CADyWQ+EhD0nz71dLtUFwb9V_6uuen-k6E5fpvrCg3ZYzfr2JSw@mail.gmail.com> <ba38a9e4-7f43-c747-2d90-f35de22a8399@gmail.com> <CAL0qLwZJaEBrXdE9JOZNOJAgR7iEzfMA86Csi2sNtE5JC7ROUQ@mail.gmail.com> <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com>
In-Reply-To: <c5cd9239-b204-255a-48a3-1cdccf18464a@gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 18 Feb 2021 09:10:37 -0800
Message-ID: <CAL0qLwYrcg__sewPO+EWfJf-5uoHcnQpFqtw-QoXxngHTJvkAA@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c1811905bb9f6a89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/vcRsV5yICIBafxIVuSkIv0FKeZg>
Subject: Re: [dmarc-ietf] Fwd: I-D Action: draft-ietf-dmarc-psd-10.txt
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 Feb 2021 17:10:52 -0000

Circling back to this:

On Fri, Jan 29, 2021 at 12:56 PM Dave Crocker <dcrocker@gmail.com> wrote:

> On 1/29/2021 12:15 PM, Murray S. Kucherawy wrote:
>
> On Fri, Jan 29, 2021 at 7:51 AM Dave Crocker <dcrocker@gmail.com> wrote:
>
>>
>> Abstract
>>
>>    DMARC (Domain-based Message Authentication, Reporting, and
>>    Conformance) is a scalable mechanism by which a mail-originating
>>    organization can express domain-level policies and preferences for
>>    message validation, disposition, and reporting, that a mail-receiving
>>    organization can use to improve mail handling.  The design of DMARC
>>    presumes that domain names represent either nodes in the tree below
>>    which registrations occur, or nodes where registrations have
>>
>> DMARC does not have 'registrations'.
>>
>
> It's referring to domain name registrations, not DMARC registrations.
>
> Also the occur/occured contrast has no obvious meaning to me.  Really, I
>> have no idea what's intended by it.
>>
> "exist"?
> "take place"?
> "are made"?
> "are done"?
>
> The issue wasn't synonyms but semantics.  'registrations occurred' has no
> obvious DMARC meaning.
>
> unless, perhaps, the meaning is 'domain names exist', but that still
> doesn't explain the contrast being drawn.
>
I'm struggling to understand the concern here.  I think we all know what it
means to register a domain, and that the namespace is arranged as a tree,
and that trees are made up of nodes, and that some nodes are above the cut
where registrations take place while the rest are below.  What other
meaning might someone in this space infer from this text?

Maybe this is better, just for the sake of having something else to look at?

   DMARC (Domain-based Message Authentication, Reporting, and
   Conformance) is a scalable mechanism by which a mail-originating
   organization can express domain-level policies and preferences for
   message validation, disposition, and reporting, that a mail-receiving
   organization can use to improve mail handling.  The design of DMARC
   presumes that domain names represent nodes in the DNS tree that are either
   reserved as points below which new domain name registrations are made, or are
   the results of those registrations; it does not permit a node to
have both of these
   properties simultaneously.  Since its deployment in 2015, use of
   DMARC has shown a clear need for the ability to express policy for
   these domains as well.

Apart from that, I'm at a loss to understand what's confusing.  I'm not
convinced that "registrations" in the context of domain names is unclear to
a reader familiar with this space.

-MSK