To be clear, this is a Last Call comment on http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-07 The JSON Data Interchange Format (draft-ietf-json-rfc4627bis-07). On Tue, Nov 12, 2013 at 2:58 PM, Anne van Kesteren <annevk@xxxxxxxxx> wrote: > Supporting encodings other than UTF-8 in new formats is not good. > > Supporting UTF-32 is actively harmful as support for it has been > removed or is being removed from clients. You ought to actively > recommend against it. > > In general ASCII incompatible encodings have very bad security > characteristics, the IETF would do well to steer away from them, just > like the W3C has. -- http://annevankesteren.nl/