On 30. 10. 26 22:10, Ben Schwartz wrote:
P.S. And if we stick with the current line that "the diagnostic format
is not for parsing", we have other options too, like using JSON for
the JSON-subset of CBOR.
--Ben
On Fri, Oct 30, 2026 at 5:06 PM Ben Schwartz <[email protected]> wrote:
On Fri, Oct 30, 2026 at 4:22 PM Robert Edmonds <[email protected]> wrote:
I'm not sure what is reductive about Ray's argument. Actually, I have
the same question. Would the "DNS layer" be expected to validate the
CBOR content of the record data in a hypothetical CBOR RR? Specifically,
would a primary nameserver need to verify that the CBOR RR's data is
valid, well-formed CBOR data when loading RR's from a data source, such
as a zone file?
I would say "parse, don't validate".
Personally I think we should:
- register CBOR RR type
- DNS servers should treat it as opaque blob
- clients and diag tools may use CBOR RR type as hint how to decode the data
Imagine dig printing out CBOR diag notation, or Wireshark which allows
you to clickity-click through the all the IP-TCP-DNS-CBOR layers down to
payload in human readable form.
If I wanted to invite massive scope creep I would say invent a new RR
type to encapsulate arbitrary blob + MIME type info, but perhaps this is
not the time.
--
Petr Špaček
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]