On Tue, Nov 15, 2005 at 11:35:55AM -0800, Douglas Otis allegedly wrote:
Extensibility is generally handled by adopting a Tag/Length/Value
(TLV) format which allows extensibility while retaining binary
representation.
Sure. But that's uncommon in DNS RRs. Even the complex ones are
positional.
There is also RFC2538 and RFC2538bis that already define inclusion of
keys within DNS. Is there something remarkable about DKIM that
requires a unique RR?
All the other data in a Selector that's not in RFC2538 is one reason.
Where does one encode g=, s=, h= in RFC2538?
Also note that the OpenPGP format uses a
binary key. Of course, this starts with a binary RR.
One can routinely point to RRs that have a key value in them, what one
cannot readily point to are key containing RRs that have the
complexity of types that a Selector does. NAPTR gets close with it's
LTV character strings.
Mark.
_______________________________________________
ietf-dkim mailing list
http://dkim.org