Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate third level .name domains?

John Levine <johnl@taugh.com> Fri, 03 June 2022 20:02 UTC

Date: Fri, 03 Jun 2022 16:02:03 -0400
Message-Id: <20220603200204.3442942E787F@ary.qy>
From: John Levine <johnl@taugh.com>
Reply-To: spfbis@ietf.org
To: spfbis@ietf.org
Cc: dw@thedave.ca
In-Reply-To: <ccb36c34-5e89-a699-e88a-e0c3985494cc@thedave.ca>
Organization: Taughannock Networks
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spfbis/qqytXlJEYEHixMm4pAy_gUTr8PY>
Subject: Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate third level .name domains?
Precedence: list

 [[ replies once again directed to spfbis ]]

>SPF should be able to handle this situation using macros anyway:
>
>bustos.name. IN TXT "v=spf1 include:%{l}._spf.bustos.name -all"
>david._spf.bustos.name. IN TXT "v=spf1 redirect=david's-email-provider"

Except, as we may have mentioned a few times, the .name ICANN contract
has no provision for adding SPF records like this. The registry only
forwards incoming mail. It doesn't handle outgoing mail.

Since they've been forwarding incoming .name mail for 20 years, and this is the first
time we've seen a complaint about outgoing .name mail, perhaps this is not a problem
that needs solving.

If David used david@david.bustos.name, the domain would point to his own nameservers
and he can do whatever SPF, DKIM, or DMARC he wants.  Or if it wants a 2LD, he could
get davidbustos.name and manage the NS.  What you can't do is manage the NS on a .name
2LD which is a last name.

R's,
John

Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate… John Levine
Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate… John Levine
Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate… william
Re: [spfbis] [dmarc-ietf] SPF doesn't accommodate… John R Levine