--On 26 May 2010 15:51:33 -0400 Brett McDowell
<brett(_dot_)mcdowell(_at_)me(_dot_)com>
wrote:
On May 26, 2010, at 1:42 PM, Steve Atkins wrote:
I'm big on concrete examples. So how does your logical conclusion
deal with these two situations?
$ host -t txt _adsp._domainkey.paypaI.me
_adsp._domainkey.paypaI.me descriptive text "dkim=discardable"
$ host -t txt _adsp._domainkey.paypal.com
_adsp._domainkey.paypal.com descriptive text "dkim=discardable"
I would like to answer your question... but I can't grok it from these
two ADSP look-ups. Are you asking about what we do if someone other than
ourselves registers a cousin domain?
He seems to be. There are several approaches that could be taken:
1. A publication mechansism that allows you to say which cousin domains
you have registered.
2. A filter checking domains with Hamming distance measurements. Like a
magnifying glass casts a shadow round the focal point, I'd imagine that
domains close to those with high reputation could be assigned negative
reputation - unless they acquired reputation from (1) above.
3. It simply would not be advisable to use cousin domains. Though
registering them to prevent use might be a good option.
--
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html