In your letter dated Tue, 6 Sep 2016 06:26:58 +0000 you wrote: > I was more commenting on the fact that it is escaping in a format > that already support escaping. The JSON output would be double > escaped and implementations would need to unescape it themselves > rather then let JSON handle it.
JSON strings are defined to be UTF-8. You get all kinds of weird problems if you try to store 8-bit binary data directly in JSON strings. (I.e. using the \uXXXX escape sequence) An encoding that only requires US-ASCII to be stored in JSON strings is a lot safer. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
