All ICANN Registry Agreements are accessible here: https://www.icann.org/en/registry-agreements?first-letter=a&sort-column=top-level-domain&sort-direction=asc&page=1. Whereas new gTLDs from the 2012 round have a prohibition against adding specific types of records in the TLD's zone (See Exhibit A, Approved Services), older Registry Agreement may have different language. Older Registry Agreements that have been renegotiated in the last six or seven years likely also have the new prohibition clause.
Craig Schwartz Managing Director fTLD Registry <https://www.ftld.com/> - .BANK <https://www.register.bank/> | .INSURANCE <https://www.register.INSURANCE> On Tue, May 31, 2022 at 8:17 PM Scott Kitterman <skl...@kitterman.com> wrote: > > > On May 31, 2022 7:50:44 PM UTC, David Bustos <da...@bustos.name> wrote: > >On Tue, May 31, 2022, at 1:33 PM, John R Levine wrote: > >> On Tue, 31 May 2022, David Bustos wrote: > >>>> Forwarding is pretty broken these days. Even if you had perfect SPF, > a lot of your incoming > >>>> mail would fail DMARC because a lot of DMARC policies depend on SPF > and SPF can't deal with forwarded mail. > >>> > >>> I'm talking about outgoing mail, not incoming mail. > >> > >> Are you talking about mail you send, or mail sent to your bustos.name > >> address that's forwarded to a mailbox somewhere else? > > > >Mail that I send to other people, with da...@bustos.name as the from > address. Yahoo and Gmail sometimes direct it to spam. I presume it is > because bustos.name doesn't have an SPF record. > > > >>>> I'm not surprised. The registry contract with ICANN forbids it. > >>> > >>> Is the contract available for me to read? > >> > >> It's the standard registry contract on the ICANN web site. > > > >Does the contract forbid publication of MX records? Verisign does that. > > > >>> This special case was committed to by TLD regulators back in 2002 and > it is a problem for everyone with a third level .name domain. That's > probably not many people, but the current situation is inconsistent so I am > trying to figure out if any increases in consistency are possible. > >>> > >>> Yes, if no changes are possible then I may need to abandon > da...@bustos.name . > >> > >> Looks that way. > > > >Is your position that Verisign should publish SPF records for the .name > domains? > > If they intend them to be used in email, then I would say yes. If they > intend third level domain owners such as yourself send email from external > servers using the second level domain in Mail From, it's non-trivial to > support, but definitely possible. > > Alternately, you might send using Mail From da...@david.bustos.name with > From da...@bustos.name and set up your own SPF record for > david.bustos.name. > > I don't know anything specific about the contract for .name, but I believe > such contracts are usually available on the ICANN web site. > > Scott K > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
