Re: [dmarc-ietf] Benjamin Kaduk's Discuss on draft-ietf-dmarc-psd-12: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Tue, 11 May 2021 20:17 UTC

Return-Path: <barryleiba@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 11CB83A250F; Tue, 11 May 2021 13:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level:
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 cWNmZkrDZ2cY; Tue, 11 May 2021 13:17:24 -0700 (PDT)
Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (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 8C7B63A250C; Tue, 11 May 2021 13:17:23 -0700 (PDT)
Received: by mail-lj1-f180.google.com with SMTP id e11so13199678ljn.13; Tue, 11 May 2021 13:17:23 -0700 (PDT)
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=G9Xq9sljz4xFUVTn8wlS32BUrwZRAYwf2Ntzj0qEDvI=; b=smmYsBEpTBjbeyGIHwrC4Ayyyv6Ko4ncEjLPMsWnbH7Pyc12NFpZ6LkpFedUG98hBf JZ8vGuFcxdXOMEZ68B9O0cQpZWGj3Kty02hvVxxauYKd6MAMDTzmrF7SMlmgTAZuFn94 Iu6anxfHbE+Z23HTcaXgPATdOXdu7p48hwjjEWHMH8uGCgFCYrpCMzy3bkb178ZxN8Lm KQVXHkfOkBnWQVoKOAd8Erj1S6ky5qbBFm9LjKyMCmSUi8IMZY735Ue447fhnAFgUwN7 8FCy3kxUIdpLVmzzN2NTWudpIp012bQgWuFJhltO2z8s4YfaVZdw83BMN06bDUbAkmbr vldQ==
X-Gm-Message-State: AOAM532zbaTg41eDj2gTposY+Jp283USWnd/YO68b/rB1d0+IjPoEjjD EaCvpE1RSgF3cRLBTlzJ9d8oWgygCJwf+cpjp4vIO2046DM=
X-Google-Smtp-Source: ABdhPJy+fbr7hzyxuzXSCLlTymbQTx2t5Y+9/FhKi7s5Hf1W/ZYcRYW9JtYkKCxZk80gQ95UfRbIJXYUdfQOt+VVa4s=
X-Received: by 2002:a2e:814d:: with SMTP id t13mr25021815ljg.467.1620764241411; Tue, 11 May 2021 13:17:21 -0700 (PDT)
MIME-Version: 1.0
References: <161898146809.1659.6234265375858401838@ietfa.amsl.com> <CADyWQ+F3_tf6QobPnPvb4rgyxZb9vhDsm56iOva0JuYmfO8z-g@mail.gmail.com> <20210511042431.GP79563@kduck.mit.edu>
In-Reply-To: <20210511042431.GP79563@kduck.mit.edu>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 11 May 2021 16:17:10 -0400
Message-ID: <CALaySJ+yYDLEr73K3S4_nKwhy2ApZy7qEvGvZj0o-24cS8GNCw@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF DMARC WG <dmarc@ietf.org>, The IESG <iesg@ietf.org>, Tim Wicinski <tjw.ietf@gmail.com>, dmarc-chairs@ietf.org, draft-ietf-dmarc-psd@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dfbffe05c21394a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/AU-iwM-Nb22SoZXGd-7vXRwwtgY>
Subject: Re: [dmarc-ietf] Benjamin Kaduk's Discuss on draft-ietf-dmarc-psd-12: (with DISCUSS and COMMENT)
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: Tue, 11 May 2021 20:17:29 -0000

>>> Section 4.1
>>>
>>>    o  Multi-organization PSDs (e.g., ".com") that do not mandate DMARC
>>>       usage: Privacy risks for Organizational Domains that have not
>>>       deployed DMARC within such PSDs are significant.  For non-DMARC
>>>       Organizational Domains, all DMARC feedback will be directed to the
>>>       PSO.  PSD DMARC is opt-out (by publishing a DMARC record at the
>>>       Organizational Domain level) vice opt-in, which would be the more
>>>       desirable characteristic.  This means that any non-DMARC
>>>       organizational domain would have its feedback reports redirected
>>>       to the PSO.  The content of such reports, particularly for
>>>       existing domains, is privacy sensitive.
>>>
>>> It might be worth making some statement about the applicability of PSD
>>> DMARC for such PSDs that do not mandate DMARC usage.  (I guess the
>>> following paragraphs mostly play that role, though perhaps editorially
>>> tying them together more clearly is possible.)
>>
>> I'm not sure where you're going on this, but the following paragraphs do
>> try to pull it together.  I've been trying to wordsmith these with little
>> luck.
>>
>> Also, it appears that the word "vice" above should be "versus".
>
> I suspected it might :)

Actually, “vice” as a preposition has a meaning similar to “versus” (you
could look it up).[1]

That said, I think that “versus” is better known and better understood, so,
despite my general preference to avoid Latin terms and abbreviations, we
should switch to “versus”.

Barry


[1]  “You Could Look It Up” is a James Thurber reference:
https://storyoftheweek.loa.org/2010/09/you-could-look-it-up.html