IETF Logo Mail Archive

Re: [Json] Update to proposed charter to cover listing changes

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Thu, 14 March 2013 17:40 UTC

Return-Path: <jhildebr@cisco.com>
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 CCD6611E80E9 for <json@ietfa.amsl.com>; Thu, 14 Mar 2013 10:40:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 JS4UmogqTnjJ for <json@ietfa.amsl.com>; Thu, 14 Mar 2013 10:40:53 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFF721F8E08 for <json@ietf.org>; Thu, 14 Mar 2013 10:40:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1255; q=dns/txt; s=iport; t=1363282853; x=1364492453; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=fxwyl5YKuH3zlQqklYdDBXAsdoOacQd+4zOKMCeWccA=; b=bgA09qOL2rdczQSp9pzSUlfqz6o0O4X2EdIb6/0wWKk2dU+QXyrRl00Z ikjXx8ID9f7PlaRzp80JHP0Ft1Ls4GCM8FdXvrMvTk4dWZrlIkx8WFpBh 2rZilPLw8UHQOh0LDAZHx6Wd8mw+BRkBcRwCXgnkWeFfhNFQIXPC6TYY5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAB4LQlGtJXG//2dsb2JhbABDxQKBZRZ0gi0BBAEBATc0HQEIIhQ3CyUCBAESCIgMDMIOjmU4gl9hA5d3j2ODCoIo
X-IronPort-AV: E=Sophos;i="4.84,845,1355097600"; d="scan'208";a="187546495"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 14 Mar 2013 17:40:53 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r2EHeqT5025549 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 14 Mar 2013 17:40:53 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Thu, 14 Mar 2013 12:40:52 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Thread-Topic: [Json] Update to proposed charter to cover listing changes
Thread-Index: AQHOIM17KjEEdL1PEkybdKtRzGi6w5ilhUmA
Date: Thu, 14 Mar 2013 17:40:52 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F8D6EAB@xmb-rcd-x10.cisco.com>
In-Reply-To: <5379220D-65A8-4D5B-9502-43DB71417364@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.1.130117
x-originating-ip: [10.21.93.229]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <38D6E91FC7B00F499C7741546D9548C3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Json] Update to proposed charter to cover listing changes
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, 14 Mar 2013 17:40:58 -0000

That tracks with what I remember from the WG meeting.

On 3/14/13 12:03 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>Greetings again. I have made the following change in the proposed charter
>(http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JSON):
>
>Any changes that break compatibility with existing
>implementations will need to have very strong justification and broad
>support, and will have to be documented in the new RFC.
>
>==>
>
>It is acknowledged that there are differences between RFC 4627 and the
>ECMAScript specification in the rules for parsing JSON. Any changes that
>break compatibility with existing implementations of either RFC 4627 or
>the ECMAScript specification will need to have very strong justification
>and broad support. All differences between RFC 4627 or the current
>ECMAScript specification will be documented in the new RFC. This
>documentation will include both the WG consensus for the rationale of the
>changes and the expected impact of the changes.
>
>Does anyone have a problem with this change?
>
>--Paul Hoffman
>_______________________________________________
>json mailing list
>json@ietf.org
>https://www.ietf.org/mailman/listinfo/json
>



-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email