If you want to do that, you could probably piggyback it on my recently
revived draft-levine-dnsextlang.
Interesting. I vaguely remember someone (Olafur?) also had a similar
approach to dynamically describing RTYPE in the DNS itself. Or maybe
it was actually this draft that I am thinking of?
This is it. See https://datatracker.ietf.org/doc/draft-levine-dnsextlang/
I think it's a reasonable idea. Have you done the work of going through
the existing RR types and describing them in this language? (I seem to
recall a previous attempt was mostly successful, with some issues with
the LOC type.)
That's the eventual plan, although there is a long tail of funky field
types found only in RRs that nobody uses any more.
I have some funding to implement it, so I'm doing the useful parts first
to see if I run into unexpected problems. It took about 15 minutes to
realize that it needs to let you name the fields as well as describe them,
if you want to refer to the fields from other code.
R's,
John
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
