> Defining a DKIM specific RR type should not prevent deployment. > Defining the DKIM specific RR within the base draft means a > new DKIM version is not required to enable its use. If there > are issues > handling a DKIM specific RR, this is a problem independent of DKIM. > A new RR issue, if there are any, may delay exclusive > reliance upon the DKIM specific RR.
I expect the deployment of DNSSEC to solve the RR problem. I believe DKIM creates the market for DNSSEC. If you can't see the problem I know a bunch of philosophers you might want to take out to dinner. _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
