On Thu, 20 May 2021 at 03:57, Mark Andrews <ma...@isc.org> wrote: >8 > > > > > RFC1035 has the definition of <character-string> encoding: > > A bunch of characters without any internal spaces, or > > A string beginning with " and ending with ", and anything else in between > > except " which must be escaped. > > Which doesn’t work in practice not the least because zone files where > designed to be transferred between machines with different native character > set encodings and different end of line conventions and the simplistic > everything in between breaks in the real world. > > example 0 iN TXT “abc > def” > example. 0 IN TXT \226\128\156abc unable to parse RR string at blib/lib/Net/DNS/ZoneFile.pm line 523. file MarkA.txt line 2 at test.pl line 14.
QNED, or is Mark winding us up! > > It isn’t ambiguity that is the problem. It’s working out which escape > mechanism we are going to use. You have just added a third escape mechanism > with the above. > In an earlier post I rashly promised to provide some words, which I will do in the next couple of days. --Dick _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
