On Sat, Nov 29, 2003 at 03:55:12PM +0200, Jukka Inkeri wrote:
I have updated our ideas. Now it is more simple "one dns query" -method.
No need anymore to take care of networks.
It also include posibilities to handle blacklist in own net. It give to
operators posibilities to block/control some "not so good" mta.
http://www.awot.fi/sf/browser/showfile?cust=awkoulutus&subdir=dns&doc=reverse_mx
It's hard to read because it doesn't wrap properly in my browser
(probably because I'm still using an antique Netscape).
But in summary it looks like this would modify the "MTA" portion
of MTAMark to use MX records instead of TXT. And (if I read this
right) it looks like you intend that the return value has special
meanings (much like the values of various DNSBLs have special
meanings). So e.g.:
<no result> --> This IP address does not participate in MTAMark/MX
127.0.0.1 --> This IP address is NOT an MTA
127.0.0.2 --> This IP address IS an MTA
<other values> --> future definition
This certainly addresses the wildcard concern in MTAMark.
One question is: does this conflict with any existing use of MX records
in in-addr.arpa ? I think that would be hard to tell, which may be
why MTAMark chose to use a unique new subdomain/keyword scheme.
-mm-
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg