Asked on Bluesky and got no responses, so I'm going to ask here where there are more techies and fewer poasters: is there an actual specification for the RFC 1035 "master file format" representation of TXT records? #DNS
=> More informations about this toot | More toots from wollman@mastodon.social
@wollman RFC8499: " Presentation format: The text format used in master files. This
format is shown but not formally defined in [RFC1034] or
[RFC1035]. The term "presentation format" first appears in
[RFC4034].". So lots of things back then are not formally specified. Early `bind` implementations are kind of authoritative. And `TXT` being the biggest lie of all, as they are binary content, not characters at all. 1/x
=> More informations about this toot | More toots from pmevzek@framapiaf.org
@wollman But the core answer is really in RFC1035 as such: §3.3.14 gives us: "TXT-DATA One or more s." and then §5.1 has: " is expressed in one or two ways: as a contiguous set
of characters without interior spaces, or as a string beginning with a "
and ending with a ". Inside a " delimited string any character can
occur, except for a " itself, which must be quoted using \ (back slash)."
=> More informations about this toot | More toots from pmevzek@framapiaf.org
@pmevzek So I've seen all that. But any character? NUL? CR-LF? Bare backslashes? Is the same syntax for octal escapes as for unquoted strings also accepted in quoted strings?
=> More informations about this toot | More toots from wollman@mastodon.social
@wollman As I said at the beginning "So lots of things back then are not formally specified.". Also, everywhere document says "character" it should say "byte" in fact.
=> More informations about this toot | More toots from pmevzek@framapiaf.org
text/geminiThis content has been proxied by September (3851b).