On Tue, 10 Aug 2004 04:00:56 -0000, "Edward B. Dreger" said:
Without new code/libs to parse the TXT RR, SPF doesn't work. As long as new code is being written, it seems logical to have another RRTYPE assigned -- that's one less thing to change later.
On the other hand, having to deploy a new BIND that supports the presumably newly-defined RR type just to publish an SPF record would almost certainly doom it to near-zero deployment. Also, remember that if we find out that the format was b0rked, publishing a new TXT is a lot easier than getting another version of an SPF RR deployed.... Compare and contrast the uptake of SPF with DNSSEC :) (Yes, I know there's *other* issues with deploying dnssec - but all those weird RR's probably scare off a lot of people...)