At 11:17 AM -0700 6/8/04, Jim Lyon wrote:
In summary, the requirements that drove the current design include:
1. It MUST be possible for organizations to publish email policy records
without installing any new software. (This pushes us toward TXT
records.)
This isn't a MUST and can't be; it has to be an assessment of the
rewards of the deployment versus the cost. Attempting to short
circuit that so absolutely is a pretty clear signal that the rewards
won't be sufficient to warrant significant time or effort on
anybody's part. That's not a signal we want to send, at least
in my personal opinion.
There are organizations out there with nothing released later than
1998; if they want to take advantage of this they may have to
bear cost. There are organizations out there who have fully
deployed dynamic dns and special purpose internal records;
they too may have to bear costs. What they are and the
affect those have on deployment do bear on the protocol
design. But they are not a forcing function.
regards,
Ted Hardie