Re: [Json] Response to Statement from Ecma International TC39

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 05 December 2013 15:59 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 B317D1AE071 for <json@ietfa.amsl.com>; Thu, 5 Dec 2013 07:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
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 23F5afTnkYqs for <json@ietfa.amsl.com>; Thu, 5 Dec 2013 07:59:08 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 87EA51AE06F for <json@ietf.org>; Thu, 5 Dec 2013 07:59:08 -0800 (PST)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rB5Fww9N014981 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 5 Dec 2013 08:59:00 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20131205044253.GH21240@localhost>
Date: Thu, 05 Dec 2013 07:58:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <51F5DED3-A3CB-4AE3-9A1C-D9E25BFD822C@vpnc.org>
References: <C7707CE2-C43E-4171-AE96-9FAFDCE53317@cisco.com> <20131205044253.GH21240@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1822)
Cc: JSON WG <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] Response to Statement from Ecma International TC39
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: Thu, 05 Dec 2013 15:59:09 -0000

On Dec 4, 2013, at 8:42 PM, Nico Williams <nico@cryptonector.com> wrote:

> On Thu, Dec 05, 2013 at 02:57:05AM +0000, Matt Miller (mamille2) wrote:
>> [...]
> 
> Comments:
> 
> - s/rfc4727/rfc4627/g  (the link to the attachment says 4727)

That's actually not part of the response we are sending, so there is nothing we can change. Yes, the link is wrong in the Liaison tool, but we'll just have to live with that.

> - I don't think we ought to demand anything more than stability for
>   normatively referencing ECMA-404.  In particular it seems odd to
>   demand that the other SDO (ECMA) establish open processes before
>   we'll consider referencing their documents -- a demand of that sort
>   ought to be backed up by a statement (as a published RFC) from the
>   IESG and/or IAB, not from a WG.
> 
>   I know, you said "[the IETF] _almost_ exclusively...".
> 
>   Are you asking the WG to demand that the ECMA commit to open
>   processes in regards to TC39's future updates of ECMA-404?  Is that a
>   consensus call?

I don't think any of the wording in the response "demands" anything. Ecma made a request, and we are turning down the request for stated reasons. People in the WG discussion expressed consternation with ECMA-404, and the undertone was that they expected it to be developed in an IETF-like fashion. It's fine that Ecma didn't do that, of course, but it is also fine for us to base our decision on their process. Having said that, which sentences about "demands" were you referring to?

> Is there documentation of "official" attempts to contact ECMA TC39.
> (I'm not sure what that would look like.)

Matt and I were told about it by at least three different people in the IETF leadership. It (thankfully) happened at a different layer.

>> We know that some TC39 members joined the JSON WG mailing list but did
>> not voice any process concerns in the WG -- or privately to the WG
>> Chairs -- before or during either of the Last Calls on the document.
> 
> I've certainly seen complaints about direction or specific consensus
> calls.  Were any by TC39 members?  I'd not know.  Were they about
> process?  Perhaps if asked for clarification those voicing concerns
> might specify the process as a source of concern.

You can determine who is a TC39 member by looking at their roster.

--Paul Hoffman