Wayne wrote:
I suspect that the IETF won't want to see SPF RRs used for things
other than SPF records for the same reasons they don't want to see TXT
RRs used: it might fill up the 512 byte UDP packet
Why should for example the sender policy of yahoo.com be too large to fit in
an UDP packet. (Currently it fits).
and there is no way to select only one sender policy type.
You will get all policy types in one UPD packet and then you can select the
desired policy. (Currently SPF does it like this: It gets all TXT records
and selects the "v=spf1" TXT record.)
The first question the receiver has is "what sender policy do you have?".
And the answer should be published at one place and retrievable in one UPD
packet. Of course that first UPD packet may contain pointers to additional
information like the public key.
The folks promoting DK, SES, IIM, etc. will need to ask the DNS folks
to allocate special records for each of those uses.
You mean the receiver should then do 4 or more DNS queries to retrieve the
sender policy?
As I mentioned above, there is no good method to migrate from one RR type
to another and it is a nasty catch-22.
Okay, then let us declare the TXT RR as the sender policy record. It already
is that anyway and it will remain that for quite some years.
Roger