Private Use Q and Meta-types for DNS

Introduction As described in DNS IANA Considerations , the DNS protocol supports three subcategories of Resource Record Types (RRTYPE): data types, QTYPES, and Meta-TYPES. There is a dedicated subrange of the RRTYPE space for Q and Meta-TYPES (128-155). The DNS protocol also defines a subrange of the RRTYPE space dedicated to private use (65280-65534), however this subrange has no corresponding subdivision into data versus Q and Meta-TYPES. This document proposes such a subdivision. Informational: There are currently four Meta-TYPEs assigned: OPT [RFC6891], TSIG, TKEY, and NXNAME. There are currently five QTYPEs assigned: * (ALL/ANY), MAILA, MAILB, AXFR, and IXFR. Notably the OPT meta-type is not assigned from the Q and Meta-Type space (presumably because it predated the current RR type space classification). Many resolvers implementations treat queries for Q and Meta-types specially. If the query is for an unknown Q or Meta-type or for a Meta-type with undefined (or forbidden) query behavior, the resolver will treat it like an invalid query. It will not attempt to perform iterative resolution for it, and return an error back to the querier, typically format error (FORMERR). This kind of behavior is not possible with private types, since the private RR type space has no differentiation of data types versus Q and Meta-TYPES. This makes it difficult to experiment with new Q or Meta-TYPES utilizing private RR types. Notably, this posed challenges when the NXNAME Meta-type was deployed in the field using a private RR type code, prior to standardization.

Private Q and Meta-Types Range The definition of new Q and Meta-types is expected to be quite infrequent, so only a small subrange should be sufficient, e.g. 16 code points. We present two options, and should choose one. Option 1: Subset of "Reserved for Private Use" Range: Option 2: Subset of "Reserved for Future Use" Range, immediately before and adjacent to the current Private Use Range:

Handling Unknown Q and Meta-Types DNS servers MUST return an error when receiving a query for an unknown Q or Meta-Type. This applies generally to both private and non-private Q and Meta-Types. The recommended response code is Format Error (FORMERR), preferably accompanied with an Extended DNS Error code of 'Invalid Query Type' (Info-Code 30). In particular, resolvers should not attempt to perform iterative resolution for such queries.

Updates to RFCs Update the RR type ranges described in RFC 6895 with the information from .

Open Questions Is this proposal best described in a separate RFC, or should it instead be part of an update to the DNS IANA Considerations RFC?

Security Considerations None.

IANA Considerations See .