The point is that when it's *that* easy to get the information indirectly,
you're
not providing actual security, you're providing security theater.
It's not *that* easy. And that's my whole point. There are ptr records that
points to in-addr.arpa rather than real domain.
But if you believe this proposal is pointless, then I'll take your vote as
"No" for this proposal.
Thanks
On Wed, Jan 9, 2019 at 8:08 AM <valdis(_dot_)kletnieks(_at_)vt(_dot_)edu> wrote:
On Wed, 09 Jan 2019 07:38:14 +0530, Viruthagiri Thirumavalavan said:
Not every PTR queries resolves to the correct domain.
74.125.129.26 => jm-in-f26.1e100.net (A google IP address, but point to
a
different domain owned by google)
I would be ok with indirectly someone getting the info rather than
directly
providing it.
The point is that when it's *that* easy to get the information indirectly,
you're
not providing actual security, you're providing security theater.
--
Best Regards,
Viruthagiri Thirumavalavan
Dombox, Inc.
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp