On 28/10/2026 05:26, Foundation wrote:
> Hi Paul,
Understood. The resource scarcity argument makes sense. Taking a dedicated
RRTYPE for `UTXO` is wasteful if many apps just need a binary
container.
Revised plan:
> 1. Drop the `UTXO` RRTYPE request entirely.
> 2. Submit a new request for a generic `CONTAINER` RRTYPE.
> 3. `_utxo` becomes just one application-specific prefix under this
> container, exactly as you suggested (like `_sip._tcp`).
>
> This is the same pattern ENS uses in DNS (reusing a generic container
> with an application prefix like `ENS1`). One generic type, application
> semantics isolated by prefix.
>
> I'll revise the IANA template under #1495165 to request `CONTAINER`
> instead, and update the draft to reflect the prefix approach.
I'm the assigned RRtype expert reviewer for UTXO, and I was planning to
reject it for some of the reasons that Paul Wouters has outlined.
I have no issue with the concept of an RRtype for holding abstract
binary data[*], but in this case I would strongly recommend a completely
new draft and RRtype application just for that, and decouple it
completely from your intended use case. I would suggest either BIN(ARY)
or BLOB as the RRtype mnemonic - there's no "CONTAINER" in the abstract
case.
Your existing draft describing the UTXO use case would then just
register the _utxo prefix in the Underscored and Globally Scoped DNS
Node Names registry:
<https://www.iana.org/assignments/dns-parameters#underscored-globally-
scoped-dns-node-names>
kind regards,
Ray Bellis
[*] it's an omission from the DNS RRtypes that I've noticed before, with
the closest being NULL, but this type is not permitted within zone files.
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]