I think (and hope) this is within scope.
The problem:
We are making progress with "teaching" our customers about the new DNS based
domain policy methods, such as SPF and CEP (Microsoft's Caller-ID Email
Policy). Since we support both, we are starting to see some "confusion" at
the admin level. At the technical level, it requires additional DNS lookups.
Possible solution:
I think each LMAP proposal already offers a distinctive tag to differentiate
each TXT record type.
For SPF, a V=SPF1 directive is expected.
For CEP, a XML <ep> entity is expected.
However, for CEP it uses a subdomain lookup, _ep.example.com. I don't think
it is necessary to have this when the TXT record is distinctively different
from the rest.. A single "domain" lookup can yield all TXT records and by
specification, SPF processors must use the (first) v=spf1 record only and
CEP processors must process an expected <EP> record.
So the I call for a common domain lookup (no distinctive sub-domain) if the
specific proposal has a unique tag identifier, which at this early stage, I
believe they all do. This will allow for the industry to use a simple TXT
domain lookup to see the entire scope of policies supported by a domain.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com