prevented, not solved. I would like to prevent someone from having to
submit a draft specifying that in the case of TXT, the (name, class,
type)-tuple should be extended with the first X octets from the RDATA
fields, somewhere in the future, because client-side demuxing is getting
too buggy and it seems like a good idea to select specific records in
the DNS itself.
Could you point to anyone, anywhere, who has ever said that the odd
history of the SPF TXT record means that it is perfectly fine to do
something similar in the future?
On the other hand, please look at all of the stuff that people outside
of the IETF do with apex TXT records, and try and say with a straight face
that SPF as as much as 1% of the multiplexing problem.
Regards,
John Levine, johnl(_at_)taugh(_dot_)com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.