Re: [Json] Normative reference reasoning and logistics

"Matt Miller (mamille2)" <mamille2@cisco.com> Tue, 17 November 2015 15:17 UTC

Return-Path: <mamille2@cisco.com>
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 5BD891A9077 for <json@ietfa.amsl.com>; Tue, 17 Nov 2015 07:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level:
X-Spam-Status: No, score=-15.086 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.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 3kseJNIZ0MVB for <json@ietfa.amsl.com>; Tue, 17 Nov 2015 07:17:13 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C1071A90B2 for <json@ietf.org>; Tue, 17 Nov 2015 07:16:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2279; q=dns/txt; s=iport; t=1447773385; x=1448982985; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=uNF2fe1+NWGpMHgF6KCyhELREVmUz/YE72R69VGl4DM=; b=aNK2cEQgPKpqGaQeCxklvkA1vEm8/XUOKmG9V1nJTsXpLvJFljo1ZBt8 yJlywTyMBF0R9Xaf5MnMm3GMz9i9033/d0UPzMhDa1W6+CK0UFmhGUhi4 CNDnbsXLc5MGvDUZO65wauNNpf8HMGtTBWvcQXKpxvGSfzPFynYwG2sRI s=;
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C9AgAfREtW/4sNJK1egzuBMw8GvlsOg?= =?us-ascii?q?WWGEAKBTjgUAQEBAQEBAYEKhDQBAQEDAXkFCwIBCBguMiUCBA4FDogYCLwbAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBDwmIZIJuiCSBFQEElkkBglaBYIh0gVuSFoRig?= =?us-ascii?q?3EBHwFDhARyhAOBBwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.20,308,1444694400"; d="asc'?scan'208";a="208476128"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Nov 2015 15:16:24 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id tAHFGLwb000831 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 Nov 2015 15:16:21 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 17 Nov 2015 09:16:21 -0600
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1104.000; Tue, 17 Nov 2015 09:16:21 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Thread-Topic: [Json] Normative reference reasoning and logistics
Thread-Index: AQHRHxA7S5ZBW+xd50G1ZxMAh7DhgJ6gViOAgABmJAA=
Date: Tue, 17 Nov 2015 15:16:20 +0000
Message-ID: <1403E8DC-B5DA-48E0-8F3E-263342DFE1AE@cisco.com>
References: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com> <C80A322B-D3FF-4A13-BB32-8545794611B8@cisco.com>
In-Reply-To: <C80A322B-D3FF-4A13-BB32-8545794611B8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-pgp-agent: GPGMail 2.6b2
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.129.24.52]
Content-Type: multipart/signed; boundary="Apple-Mail=_4F4C3BCD-F588-47CC-8692-EEEA00268ACF"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/zZ7Ij-8S2kN4LumryC5fz5TEDMw>
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Normative reference reasoning and logistics
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 17 Nov 2015 15:17:23 -0000

> On Nov 17, 2015, at 02:10, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:
> 
> On 11/14/15, 8:10 PM, "json on behalf of Tim Bray" <json-bounces@ietf.org on behalf of tbray@textuality.com> wrote:
> 
> 
> 
>> But I have a practical question. What exact effect to we expect this to have?  Will ECMA-404 be updated in place with a reference to 7159bis (ECMA specs can be updated in place, because -404 already has been,
>> to remove a silly typo).  Will there be an ECMA-404bis, and if so, should we work carefully with ECMA to make sure that the two -bis specs mutually reference each other?
> 
> My understanding is that this is the intent.  A normative reference makes roughly the same amount of sense in the other direction (i.e. Perhaps none, depending on your point of view), but that we have pre-discussed with the -404 team this potential approach for moving forward.
> 
> Our ECMA liaison might want to speak more formally to this point.
> 

This is what's been discussed with Ecma TC39.  They will update 404 to include a reference to 7159bis when it completes.  As everyone surmises, no further changes are expected in either documents.


--
- m&m

Matt Miller <mamille2@cisco.com>
Cisco Systems, Inc.