On 28/10/2026 15:57, Ben Schwartz wrote:
The proposals here (BLOB, CONTAINER, BINARY, etc.) are significant
changes to the DNS system design, comparable in scope to the TXT
record. I do not think that major changes like this should go through
IANA "Expert Review" without IETF review.
There is no such criterion in RFC 6895.
In general, the DNS has historically favored somewhat purpose-specific
RR types. In my view, the design goal is that general-purpose DNS
tooling should understand the data well-enough to render it in
human-readable fashion, to the extent possible.
Respectfully, Ben, I disagree. Historically the DNS has favoured
throwing everything into TXT RRs ;)
However, we have two widely supported mechanisms for making data
application specific available, both documented in IAB RFC 5507.
- an owner name prefix (in this case _utxo)
- an RRTYPE (UTXO, or BINARY, BLOB, etc).
While RFC 5507 does favour the latter, it is not prescriptive about it,
and the Underscore Label registry post dates it, and IMHO makes the
owner name prefix method somewhat more palatable.
My belief is that there *is* a need for an opaque binary type, and that
it would be perfectly reasonable for a draft for such a type to specify
that its use SHOULD only be associated with an underscore-prefixed owner
name.
A BINARY type would lose this ability, and encourage arbitrary opaque
data in DNS. Perhaps this is what we want, but it is a big change
with some obvious downsides related to debugging and inspection.
Personally, I would be more comfortable with a "CBOR" RR type or
similar, as this at least offers the possibility of human-readable
visualization and editing.
I can see no rationale for constructing an RRtype that can *only* be
used for CBOR. Would the DNS layer be expected to perform checks that
the content is valid CBOR?
Those debugging and inspection tools should be in the application layer,
c.f. SPF check tools, etc, and not in the DNS layer.
kind regards,
Ray
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]