W3C home > Mailing lists > Public > www-tag@w3.org > November 2013

Re: JSON: encodings

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 12 Nov 2013 15:09:26 +0800
Message-ID: <CADnb78iggFjj7+ZbG03JaVtfSDuf4KKK4zzH0_rTC0_xRB85hQ@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>
Cc: Henri Sivonen <hsivonen@hsivonen.fi>, www-tag@w3.org
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@annevk.nl> 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.

Received on Tuesday, 12 November 2013 07:09:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:59 UTC