It hath once been written:
Now we're debating exactly these issues --- should we, strategically,
make new RR types work now and for good, or should we tactically just
do TXT?
The single biggest problem to supporting a new RRType in the NS structure is
that all NS must support it before implemention can occur reasonably. With the
inherent hierarchical structure of NS, this is an unfortunate requirement.
I agree that a new RRType has distinct advantages, but the overly burdensome
requirement of updates to all NS in the world makes this unreasonable in the
short term.
SPF as it exists today is not too burdensome to implement or setup. Yes, it has
some limitations being in a RRType of TXT in NS. But, this small compromise
means that we can implement today instead of many years from now once all of the
NS in the world are updated to support alternative RRTypes.
This is the single biggest consideration when considering such a change.
Technical idealism must be held to the fire of a need to stop joe-jobbers
"today" instead of some time "tomorrow"...
Cheers!
================================================================
Steven G. Willis sgwillis(_at_)deepskytech(_dot_)com 772.794.9494
Deep Sky Technologies, Inc. http://www.deepskytech.com/
http://www.badchickens.com/ http://www.store-secure.com/
AIM-iChat: dstisgwillis
================================================================
A: Yes.
Q: Are you sure?
A: Because it reverses the logical flow of conversation.
Q: Why is top posting frowned upon?
================================================================