IETF Logo Mail Archive

Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)

John Cowan <cowan@mercury.ccil.org> Wed, 20 November 2013 22:33 UTC

Return-Path: <cowan@ccil.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AC21AE0C1 for <json@ietfa.amsl.com>; Wed, 20 Nov 2013 14:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.125
X-Spam-Level:
X-Spam-Status: No, score=-3.125 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.525] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HE5xmC8HiEqH for <json@ietfa.amsl.com>; Wed, 20 Nov 2013 14:33:21 -0800 (PST)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 6613B1AE078 for <json@ietf.org>; Wed, 20 Nov 2013 14:33:21 -0800 (PST)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1VjGKX-0003ku-Cf; Wed, 20 Nov 2013 17:33:05 -0500
Date: Wed, 20 Nov 2013 17:33:05 -0500
From: John Cowan <cowan@mercury.ccil.org>
To: Henri Sivonen <hsivonen@hsivonen.fi>
Message-ID: <20131120223305.GB5476@mercury.ccil.org>
References: <8413609C8A86497F856897AF2AA24960@codalogic> <CEAA3067.2D132%jhildebr@cisco.com> <CANXqsRJEtBoprQFrftz80ZigmBR_NHoEXK1sR4GyBtz5B2KC8Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CANXqsRJEtBoprQFrftz80ZigmBR_NHoEXK1sR4GyBtz5B2KC8Q@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: Pete Cordell <petejson@codalogic.com>, JSON WG <json@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2013 22:33:23 -0000

Henri Sivonen scripsit:

> There is no legitimate reason to use UTF-32 for interchange.

[snip]

> As for UTF-16, there's no legitimate reason* for any new producer to
> use it for interchange, 

This is all very well, but we are not at present in the business of
banning previously permitted forms of JSON.  If you have evidence
that the specific use of these encodings harms JSON interchange,
bring it forward.

-- 
You are a child of the universe no less         John Cowan
than the trees and all other acyclic            http://www.ccil.org/~cowan
graphs; you have a right to be here.            cowan@ccil.org
  --DeXiderata by Sean McGrath

v2.23.0 | Report a Bug | By Email