Edward Lewis wrote:
ISC's DHCP implementation is one thing that uses the
TXT RR (and as far as I know, not spec'd by a std).
As it appears their implementation is not compliant with RFC1464 (I did
not see any attributes nor equal sign), I would say it's ISC's problem.
I know of other experimental uses of the TXT RR, for one,
opportunistic encryption. There is an RFC in preparation to
document that. So, MARID can't claim the TXT for it's own
- others already use it.
If they are using a well-known set of attributes, I don't see why. Part
of the spec could be acknowledging the other attributes already in use.
And the fact that one of these of the TXT RR is spec'd
in any IETF document (so far as I have been able to tell),
reliance on TXT in a proposed standard chancy - in my opinion.
I'm with you here.
However, if who uses what (as far as attributes are concerned) is
documented, this might change. My original text was:
i) The TXT RR is now reserved for SPFID and you can't put
anything you want in it anymore; anything that would go
into the TXT record needs to be cleared by MARID first.
This is too strong; what I meant is that we should have a list of known
attributes for the TXT record. Anyone wanting to use an attribute should
register it. Would this make the TXT record palatable for PS if
attributes were reserved for SPFID?
Michel.