Re: [Json] Benoit Claise's No Objection on charter-ietf-json-00-01: (with COMMENT)

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 16 May 2013 14:49 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB0421F8C4C; Thu, 16 May 2013 07:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.633
X-Spam-Level:
X-Spam-Status: No, score=-102.633 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eUsW+amAUd2I; Thu, 16 May 2013 07:49:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1BFDE21F8C00; Thu, 16 May 2013 07:49:54 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4GEnmrR047145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 16 May 2013 07:49:49 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130516082858.9386.7750.idtracker@ietfa.amsl.com>
Date: Thu, 16 May 2013 07:49:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <21D9D5AB-56AA-4B26-9782-267A8648FEE7@vpnc.org>
References: <20130516082858.9386.7750.idtracker@ietfa.amsl.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: The IESG <iesg@ietf.org>, json@ietf.org
Subject: Re: [Json] Benoit Claise's No Objection on charter-ietf-json-00-01: (with COMMENT)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Thu, 16 May 2013 14:49:54 -0000

On May 16, 2013, at 1:28 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Do you expect discrepancies between the "existing implementations of RFC
> 4627" and the "RFC 4627 specifications" (and ECMAScript specification
> btw)?

There are known discrepancies between RFC 4627 and ECMAScript, and some implementations rely on one versus the other. See <http://www.ietf.org/proceedings/86/slides/slides-86-json-2.pdf>, particularly slides 4 and 5.

--Paul Hoffman