As I understand it, your design depends on putting NXDOMAIN signals
in the additional section to show that there aren't any boundaries
between the names it returns. How do you plan to do that?
John, I don't understand your note.
In draft-dcrocker-dns-perimeter-00, it says this:
Another
On 4/13/2019 8:20 PM, John Levine wrote:
In article you write:
On 4/10/2019 8:37 PM, Scott Kitterman wrote:
print(response.additional)
[]
Turns out that's what I was especially hoping to see.
As I understand it, your design depends on putting NXDOMAIN signals
in the additional section to s
In article you write:
>On 4/10/2019 8:37 PM, Scott Kitterman wrote:
> print(response.additional)
>> []
>Turns out that's what I was especially hoping to see.
As I understand it, your design depends on putting NXDOMAIN signals
in the additional section to show that there aren't any boundaries
A couple of days ago I sent a single message to a reasonably large mailing
list (spf-help, email oriented - so likely not representative, but it's a data
point). Since I am a list owner, I know how many subscribers there are and
from my DMARC feedback, I know how many times that single message
Tim, thanks for your review. John, thanks for your response. I can see how the
section references could be a little confusing, but given the context of the
surrounding text, I think leaving them as-is is ok. I entered a No Objection
ballot.
Alissa
> On Mar 11, 2019, at 8:31 PM, John R. Levine
