[Json] Proposal to move forward on acceptable roots

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Fri, 30 May 2014 16:13 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id C31481A09D9 for <json@ietfa.amsl.com>; Fri, 30 May 2014 09:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id nTmloNIFmrJX for <json@ietfa.amsl.com>; Fri, 30 May 2014 09:13:43 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB0F1A09C8 for <json@ietf.org>; Fri, 30 May 2014 09:13:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=900; q=dns/txt; s=iport; t=1401466418; x=1402676018; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=jKq0Ntk1HROfae30G//Oc55/iHItrvsE/yhdb54G0+g=; b=NMzIhQaSp8OtSCVpLUkUgWhik4j3gfwJIswrLIWzHfsLgZbl7fXKU6eG gX4rEG8CcoTqvOV0v6QQ9X6zmDPDqypDa2xaJGyC2QTHEk1ubJ7ug1L6/ K+CtKwlRujtBkBVW0i3ObWlP3n5MncHn6EVnKWcd479/IgNbBffkr+amK w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcLAN2tiFOtJV2a/2dsb2JhbABZgweBKoJspzAGmDRwFnSCLCMRVwEiAiYCBDAVEgSIVaMDjyKkVxeBKoQri3mBSwSZfpMtgziCLw
X-IronPort-AV: E=Sophos;i="4.98,941,1392163200"; d="scan'208";a="48700298"
Received: from rcdn-core-3.cisco.com ([]) by alln-iport-3.cisco.com with ESMTP; 30 May 2014 16:13:38 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com []) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s4UGDcQd031431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Fri, 30 May 2014 16:13:38 GMT
Received: from xmb-rcd-x10.cisco.com ([]) by xhc-rcd-x12.cisco.com ([]) with mapi id 14.03.0123.003; Fri, 30 May 2014 11:13:38 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: "json@ietf.org" <json@ietf.org>
Thread-Topic: Proposal to move forward on acceptable roots
Thread-Index: AQHPfCIcnVt0eHv8dUaR/61n4HNV1g==
Date: Fri, 30 May 2014 16:13:37 +0000
Message-ID: <CFAE0A52.4C56C%jhildebr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <82350AE3EE273E46AB502A4D48B8C45A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/OUJuVjmTSzABOnmguqC8ycG73dw
Subject: [Json] Proposal to move forward on acceptable roots
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: Fri, 30 May 2014 16:13:43 -0000

One way we could go on the topic of what goes in the root that would work
for me would be for us to add a non-normative section to I-JSON giving
protocol design advice, and move the issue of potential incompatibility of
non-[object,array] roots to that section.

Into that section, we can also put some suggestions about how to encode
integers, floats, and dates in strings, how to do forward-compatibility
with objects (MUST ignore what you don't understand), and whatever other
pearls of wisdom we come up with.

Yes, I know that will make the document take longer, and open up other
areas for us to argue about.

Joe Hildebrand