IETF Logo Mail Archive

Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-02.txt

"Matt Miller (mamille2)" <mamille2@cisco.com> Mon, 18 July 2016 12:40 UTC

Return-Path: <mamille2@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 C418912B069 for <json@ietfa.amsl.com>; Mon, 18 Jul 2016 05:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 q0L7zLM_hyVY for <json@ietfa.amsl.com>; Mon, 18 Jul 2016 05:40:44 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6B912B032 for <json@ietf.org>; Mon, 18 Jul 2016 05:40:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2985; q=dns/txt; s=iport; t=1468845644; x=1470055244; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=06VgH8TSNT+c7QjREpOEbz2SwzzJT2GKcpdKV6+zECY=; b=cRpq4whbM+O4OE91US2wfD59Rd5Ii7eJrfpBNw2QnxnewsFDTGEjjna2 6HF2EtOv5Gn4z5gwmdi+ai6szmhoW/KbfM7lRq2d6SqqXEX8UHWrn/Yab XHKmkWJSqBZXEsn8RtgLte3jqsLCZCVFOFcVfP8MJap75kFadUbW7JaxW A=;
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BqAgD2zYxX/4MNJK1bgz9WfAa4dYF5IoV4AoE0OBQBAQEBAQEBZSeEXAEBBAEBASFLCwULAgEIGCoCAicLJQIEDgUOiBoIDrA3jW0BAQEBAQEBAQEBAQEBAQEBAQEBAQEOCQWIIoJVh0Ergi8FmSICAYM2gW6JOgqBYY1Mhl+JPgEeNoNzboY/fwEBAQ
X-IronPort-AV: E=Sophos;i="5.28,383,1464652800"; d="asc'?scan'208";a="298434423"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Jul 2016 12:40:43 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u6ICehcM009011 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 Jul 2016 12:40:43 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 18 Jul 2016 07:40:43 -0500
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.1210.000; Mon, 18 Jul 2016 07:40:42 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Barry Leiba <barryleiba@computer.org>
Thread-Topic: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-02.txt
Thread-Index: AQHRx4EwF4LbEztrsESZSZB6P9hXPJ/ryCGAgAAALYCAARcYAIAAGoCAgACClACAAMGOAIAuk0kAgAHWrAA=
Date: Mon, 18 Jul 2016 12:40:42 +0000
Message-ID: <EE944F32-DDC2-43E9-996A-20160BCEBC38@cisco.com>
References: <20160616034238.26185.479.idtracker@ietfa.amsl.com> <CAHBU6itvDjZon-=xtgu=MCMsjU1UtL=pXFP6-kuf1AF_w9rn3Q@mail.gmail.com> <CAHBU6ise43q3d0bVyivMtPn2LYgB2Bu_1--UFzi4SGkewKV8_A@mail.gmail.com> <CAC4RtVAVtDj7npNkWt_F+iQcdp=0StYAtQ=eo7awEzV6uzvikQ@mail.gmail.com> <F5652454-FB70-499A-A93F-4D7E243C88E7@cisco.com> <73bcf544-b2f6-da98-2e73-65654b1bc328@it.aoyama.ac.jp> <F9AF070E-1687-4B8D-8E0E-EBF8E3A2DC6C@cisco.com> <CAC4RtVBcq0mvRKzcdKwZWsVJBtP94qeZrxErfcwO0PSYVUTKFA@mail.gmail.com>
In-Reply-To: <CAC4RtVBcq0mvRKzcdKwZWsVJBtP94qeZrxErfcwO0PSYVUTKFA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-pgp-agent: GPGMail
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.100.254]
Content-Type: multipart/signed; boundary="Apple-Mail=_E70148C5-297C-47B3-9729-53BDCBA56088"; protocol="application/pgp-signature"; micalg="pgp-sha512"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/jbUVo9DKu2ma9428S_hRc2WaQi4>
Cc: Tim Bray <tbray@textuality.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-02.txt
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 18 Jul 2016 12:40:47 -0000

Ecma TC39 will publish an update to ECMA-404 shortly after the rfc7159bis is published.


--
- m&m

Matt Miller
Cisco Systems, Inc.

> On Jul 17, 2016, at 10:36, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Another month gap/stall...
> Have we checked with TC 39?  Are we still moving forward?
> 
> Barry
> 
> On Fri, Jun 17, 2016 at 7:20 PM, Joe Hildebrand (jhildebr)
> <jhildebr@cisco.com> wrote:
>> It should help that we’ve got a draft that says the right thing now.  Matt, with your TC39 liaison hat on, maybe you can forward it to them and see what their schedule is looking like?  Ideally, we’d be able to publish both documents in roughly the same timeframe.
>> 
>> --
>> Joe Hildebrand
>> 
>> 
>> On 6/16/16, 11:48 PM, "json on behalf of Martin J. Dürst" <json-bounces@ietf.org on behalf of duerst@it.aoyama.ac.jp> wrote:
>> 
>>> On 2016/06/17 07:00, Matt Miller (mamille2) wrote:
>>>>> On Jun 16, 2016, at 14:26, Barry Leiba <barryleiba@computer.org> wrote:
>>> 
>>>>> As the former AD who was part of sorting this out with ECMA:
>>>>> They are supposed to do the same, putting something in their docs that
>>>>> points to ours and says something similar about having the two specs
>>>>> remain converged.
>>>>> 
>>>> 
>>>> Thanks Barry.  Yes, this is what has been agreed to by Ecma TC39.
>>> 
>>> Not specific for this, but just a general comment based on experience
>>> from collaboration between different standardization organizations:
>>> Don't expect this to happen overnight. Each organization works at their
>>> own cycles and pace.
>>> 
>>> Regards,   Martin.
>>> 
>>> _______________________________________________
>>> json mailing list
>>> json@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json
>> 
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json

v2.23.0 | Report a Bug | By Email