On Oct 28, 2026, at 09:28, Ray Bellis <[email protected]> wrote:
> 
> On 28/10/2026 15:57, Ben Schwartz wrote:
> 
>> 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?

This argument seems reductive. The "DNS layer" is not responsible for checking 
that the fields in an SOA record are valid, and yet SOA (and MX and ...) were 
all defined in the original DNS specification.

A rationale for requiring the BLOB-esque type to be CBOR is you don't need to 
have any other subtyping. CBOR tags are first-class data items, and a tag 
inside the CBOR can define what the data object is. 

The DNS community is allowed to ignore IETF data format standards (in this 
case, a full standard), but in this case I propose that it does not.

--Paul Hoffman (co-chair of the CBOR WG)

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to