Hector Santos wrote:
----- Original Message -----
From: "Arvel Hathcock" <arvel(_at_)altn(_dot_)com>
I can completely agree that the policy be located where the current SSP
draft states - _policy._domainkey.<domain>. However, I would like to
propose (no surprise) that there be a "informative implementation note" or
whatever the appropriate vehicle is to say something like this:
"In the event that an SSP record can not be located at
_policy._domainkey.<domain> a verifier SHOULD look for the SSP record at
_domainkey.<domain>."
I agree. One location.
Why not just <domain>?
Because it conflicts with every other thing that wants to put an
semantically overloaded TXT record at the top level? At least
by claiming a subtree as our own you avoid that congestion,
and the possibility of slagging the MTU.
Mike