Paul Hoffman wrote:
> On Oct 30, 2026, at 13:21, Robert Edmonds <[email protected]> wrote:
> > I'm also not sure what you mean by saying that the "DNS layer" is not
> > responsible for checking that the fields in an SOA record are valid.
> > It is; SOA is a well-known record type that contains two compressible
> > domain names (the MNAME and RNAME fields). Receiving servers must
> > decompress those fields to ensure that they do not inadvertently
> > generate an invalidly formatted response when passing the SOA record
> > along.
> 
> I see nothing in RFC 1035 that says that.

Section 4.1.4: "... all programs are required to understand arriving
messages that contain pointers."

See also section 4 of RFC 3597 which spells out the requirements and
consequences more explicitly.

> >> 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.
> > 
> > I notice that the IETF has standardized other data formats as well, for
> > instance: XML, JSON. Do we need XML and JSON RRTYPEs as well?
> 
> I didn't say that we "need" a CBOR RRtype, just that a BLOB type that has an 
> identifier field and a contents field would be better off as CBOR because 
> managing the identifier field will be a mess, and that mess has already been 
> solved in CBOR. 

Oh, I think I see. The "contents field" in this hypothetical RR is
user-supplied data encapsulated inside a CBOR payload, rather than
the contents being required to be CBOR-encoded by the user? And the
"identifier field" is presumably a CBOR Tag number, also provided by
the user, and the nameserver has no responsibility to validate the
plausibility of these two fields?

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

Reply via email to