IIRC, there is support for generic-named types similar to BIND's record type name/number thing.
The RRTYPE would be a given a name which is something like "rrtypeNNNN", and numeric value associated with the name, which is NNNN. The RDATA would be encoded as a specified-length base-64 encoded binary blob. The RDATALEN specifies the length of the RDATA. As to maintaining the specification, given that this is a -00 version, it might need to be clarified. I think that this would best be handled in an IANA registry, on the basis of the existing registered DNS types, names, etc. I think there is perhaps a need to specify how to craft the entries in that registry. Long-term, it may be better to include the encoding as table entries for the DNS types, as first-class citizen(s) within those other registry entries. All of this is flexible. Brian
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
