On Thu, 2005-01-06 at 14:43 +0000, Tony Finch wrote:
Yes I know it's too early to discuss DNA, but ideas don't arrive
according to a timetable :-)
At the moment accreditation and reputation lookup keys in DNA take the
simple form of <HELO name>.<DNA service>. I think it would be useful to
make them more elaborate: <HELO>.<reversed addr>.<IP version>.<service>.
It would be helpful when creating a lookup hack to handle this request
to have a means for easily locating a separation between the <HELO> and
the <reversed addr> regardless of the direction the string is parsed.
It could be <reversed addr>.<IP version>.<HELO>.<service> where the <IP
version serves as a point for splitting the request internally. I have
noted that the reputation/authentication service could handle much of
the overhead associated with CSV, but not as a replacement for
publishing. Authentication services could act as an alternative for
publishing, but still one must publish pointers to the authentication
service. For reputation, having the information published is important
for handling the scale of the effort.
SMTP servers are often based on many short-lived processes, which aren't
effective at cacheing DNS information. This could significantly reduce the
amount of DNS traffic generated by the SMTP server.
The disadvantage of this idea is that the lookup key will often contain
redundant information, which could cause DNS caches to be clogged up with
multiple names where only one is needed.
The issue of DNS traffic is important.
-Doug