On Feb 1, 2025, at 15:49, Robert Edmonds <edmo...@mycre.ws> wrote: > > Paul Hoffman wrote: >>> So does a DUJ encode the display format of record data, >>> or does it encode a zone file fragment that embeds the display format of >>> record data? >> >> It encodes the display format. The draft says "The strings are expressed in >> the same manner as the display format defined for the RRtype." > > I guess I'm not totally clear on the difference between the two. > Assuming display format is the same as presentation format, which is > "the text format used in master files" (RFC 8499). How much of the > master file syntax is allowed in, or part of, the display format? > > If comments aren't allowed, what about parens, embedded newlines, \DDD > and \X escapes, etc.?
None of that; I'll add more prohibitions. Thanks again for asking good questions! >>> Or like this? >>> >>> ["DUJ", [["add", "yourname.example", "SOA", >>> "ns1.yourname.example hostmaster.yourname.example 2024112101 7200 3600 >>> 604800 60"]]] >> >> The latter, according to a normal reading of RFC 1035. Nothing in Section >> 3.3.13 suggests that the fields are <character-string>s; neither does the >> example in Section 5.3 there. > >>> Or like this? >>> >>> ["DUJ", [["add", "yourname.example", "MX", "10", "mx1.provider.example"]]] >> >> The latter, according to the example in Section 5.3 in RFC 1035. > > Hm, I'm not following why SOA record data would be encoded in a single > JSON string: > > "ns1.yourname.example hostmaster.yourname.example 2024112101 7200 3600 > 604800 60" > > But MX record data would be encoded as multiple JSON strings: > > "10", "mx1.provider.example" Because I messed up: I meant "the former", which is "10 mx1.provider.example". Neither "10" nor "mx1.provider.example" are <character-string>s, so it all goes in one quoted Rdata. --Paul Hoffman _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
