It appears that Stephane Bortzmeyer  <[email protected]> said:
>On Tue, Oct 27, 2026 at 01:31:21PM -0400,
> Paul Wouters <[email protected]> wrote 
> a message of 76 lines which said:
>
>> This possibly jsutifies an RRtype that can be used to ship CBOR endcoded
>> payloads, but then it should not be called UTXO but be kept rather
>> generic like perhaps CBORDATA, so other applications with similar
>> requirements could use it without confusion.
>
>Or even more generic: a RRtype BINARY with two fields in the data, a
>short one to indicate the type and the binary data. This would work
>for all the cases where you just want to send opaque binary data,
>without any processing except in the end points.

Before we did that, I would want to understand what it does that we can't 
already
do with TXT records.  As others have noted, despite its name, the contents of a
TXT record is a sequnce of 1-255 byte strings with arbitrary contents.  That 
really
works -- a while ago I did a hack to put database B-trees in the DNS with each
B-tree record stored as a TXT record which was pretty gross but worked fine.

We know from experence that 255 is too short so I suppose a BINARY type with
a sequence of byte strings with 16 bit lengths might be useful.  Perhaps with a
type field at the beginning, or a type field per string.  Or even no lengths,
just data and if you want to embed length codes in your data, that's up to you.

What problem do we think we're solving here?

R's,
John
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to