It appears that Scott Kitterman said:
>For a 'normal' domain/sub-domain like eml.example.com where the domain has a
>DMARC policy, every single implementation approach gives the
>same answer, so it doesn't matter. The challenge is getting all the other
>cases right.
>
>Until we understand what
I was surprised to see that #111 and #112, about the definition of NP,
survived to be included in this policy discussion.
I remain strongly opposed to an NP policy based on A//MX.A brief
recap:
- A non-existent domain test should be based on a DNS query that returns
NXDomain, not NODATA.
On October 26, 2021 9:03:15 PM UTC, Todd Herr
wrote:
>On Tue, Oct 26, 2021 at 4:07 PM Scott Kitterman
>wrote:
>
>>
>> What does "an agreed-upon level in the DNS hierarchy" mean? The
>> organizational domain is the current "agreed-upon level". Is this the
>> same or
>> something different?
On Tue, Oct 26, 2021 at 5:03 PM Todd Herr wrote:
> On Tue, Oct 26, 2021 at 4:07 PM Scott Kitterman
> wrote:
>
>>
>> What does "an agreed-upon level in the DNS hierarchy" mean? The
>> organizational domain is the current "agreed-upon level". Is this the
>> same or
>> something different? We kn
On Tue, Oct 26, 2021 at 4:07 PM Scott Kitterman
wrote:
>
> What does "an agreed-upon level in the DNS hierarchy" mean? The
> organizational domain is the current "agreed-upon level". Is this the
> same or
> something different? We know you can't do this by counting dots in a
> domain
> name.
On Monday, October 25, 2021 3:30:19 PM EDT Todd Herr wrote:
> Greetings.
>
> There are, by my count, eleven tickets that are primarily focused on or at
> least touch on the issue of policy discovery. A specialized query for them
> is at this URL - https://trac.ietf.org/trac/dmarc/report/15
>
> Th
