On Thu, Nov 9, 2023 at 8:37 AM John Levine <[email protected]> wrote:
> It appears that Todd Herr <[email protected]> said: > >-=-=-=-=-=- > > > >Colleagues, > > > >I note that lately in various email fora that the term "apex domain" has > >found some favor, said term being used interchangeably with > "organizational > >domain", and having the same contextual meaning as "organizational > domain". > > They don't mean the same thing, so please don't change anything. > > "Apex" is related to what part of the DNS tree is on what name server, > the topmost name in a zone. A lot of the time the org domain is at the > apex of a zone, but sometimes it's not, and the zone structure is > irrelevant to the way DMARC works. > As an individual, I concur with John. A significant part of moving from the existing org domain lookup to a tree walk was to provide flexibility to domain owners, to let them specify policy in the places more organizationally appropriate for them. In other words, to give them more freedom from the apex domain. John's point is spot on. Apex is well defined elsewhere, and is irrelevant to how DMARC works, doubly so with the updated policy discovery mechanism. Seth > > R's, > John > > _______________________________________________ > dmarc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmarc > -- *Seth Blank * | Chief Technology Officer *e:* [email protected] *p:* This email and all data transmitted with it contains confidential and/or proprietary information intended solely for the use of individual(s) authorized to receive it. If you are not an intended and authorized recipient you are hereby notified of any use, disclosure, copying or distribution of the information included in this transmission is prohibited and may be unlawful. Please immediately notify the sender by replying to this email and then delete it from your system.
_______________________________________________ dmarc mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmarc
