> This type of extensibilty DOES NOT complicate APIs except for > DNS-utility applications like "dig", ... that choose to dabble in > processing of ad hoc query results.
Maybe it's a language thing. Our library (domain crate) supports low level operations on DNS messages (which are obviously open-ended both with respect to new Rtypes and new EDNS(0) options) and higher level resolver constructs. However, for the user of the library this is most often not a problem. A Rust 'enum' provides the user of the library with direct access to all supported types. If the type is not supported then the user gets a collection of bytes. The same applies to the SVCB/HTTPS parameters. Does the language you use have a sum type that has a hard time expressing unknown data? In domain crate, the application can also bring it's own types if it wants to support more types than currently supported in domain. _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
