Re: [Json] jsonbis - Not having a session at IETF 100

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Sun, 12 November 2017 12:12 UTC

Return-Path: <pfpschneider@gmail.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 AD0E712941D; Sun, 12 Nov 2017 04:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 zV3m5d3UfZ-t; Sun, 12 Nov 2017 04:12:17 -0800 (PST)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7F58129436; Sun, 12 Nov 2017 04:12:16 -0800 (PST)
Received: by mail-qk0-x241.google.com with SMTP id p19so11566172qke.2; Sun, 12 Nov 2017 04:12:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=7l8lhXeB1Ji1jpWkaLQJFW0I42WhG4byA03ET+1YkTg=; b=DqQmmEVO0DtO9NO23F2GHX7MObU+wsPU8M5EQaSTXksEJsY0qh+qWJDeNS8E6pz7+3 JylgMOSU7GWzuo+Foa7NmZKmBdeeg23v0+aw+GOZSmorPHsxyUKAYUiKPi98GzVvAC9M vCpBgs31ubXHtZrlUAaYaflD7wAn8hag9xYhfqYqYvLUL5nqnLZnD4nvTrTVSOfcHq67 Ei7R/L8XsRm7StR3u6IXjgnv1a30sUjtw560AJ/KRg8LJUIhPvLB1rzcHTmnATTmVcvK pSCWN1UWwcIxbCpVNzu0sd3S6mWvXmPykyLIxQDkvh1+t/+PDtU4ju8MYxbxnHx70RVc xv2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=7l8lhXeB1Ji1jpWkaLQJFW0I42WhG4byA03ET+1YkTg=; b=QxjFt08oQ9YqcgNXPze3JYIfMxkbeLrCb9zHt6sycNa14ahsa0nSOu5VHhqp7SHWf3 11ZXSXBIiRn55/3wJCkrjytb4l4Id0xozMthFWe4coLWsPION/T88X1mTyjC8rSVdTam m6FSYIJP5bj5wcAL3Yizr5oLrWZcCuzeC+wUuNs74nOZZZhGJOVTjOM9hcG0xLTdX2Gd AT2jnHxnWuXMgIAKwQN+hfxcV523jjk5BZLe4NdAzHFZN6/FgKRNDl3jvyo3qwaAdhCu H3IR0t207AcUei5SBAak6fyGPsC84ewg3U0y3HsY0+FA2BNrzbu++bZvCPIERsF9mZ8p 9q1g==
X-Gm-Message-State: AJaThX5Yt62tiYTCigel0tu37d9IyNG8wOulvOz7Y6HmhT/wSnj6dGaR 1huhfcgQIxqw7Sq1YDkpnqRh3g==
X-Google-Smtp-Source: AGs4zMbIMvhOQZg92IccdAp2bfA9WKpaF2bmab0BAumjwsmMgvRzz4ckFrzV5I4/z48ChbUaHhVZ3w==
X-Received: by 10.55.98.6 with SMTP id w6mr9632406qkb.322.1510488735668; Sun, 12 Nov 2017 04:12:15 -0800 (PST)
Received: from [10.0.0.9] (pool-100-1-249-219.nwrknj.fios.verizon.net. [100.1.249.219]) by smtp.gmail.com with ESMTPSA id y192sm9429954qky.62.2017.11.12.04.12.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Nov 2017 04:12:14 -0800 (PST)
To: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, Alexey Melnikov <aamelnikov@fastmail.fm>, Julian Reschke <julian.reschke@gmx.de>, json@ietf.org
Cc: jsonbis-chairs@ietf.org
References: <150669032129.14118.1441258768913961205.idtracker@ietfa.amsl.com> <14b239c8-e17c-0ca2-561b-83b2bbd57516@gmx.de> <0a167b10-bb3b-7bac-2906-63c459230645@isode.com> <e986c580-b6df-3736-ebed-4b06d761853c@gmx.de> <1510238425.3520771.1167030728.53A2E4C7@webmail.messagingengine.com> <2ac7774a-59b5-86aa-cb7a-20d54127dadf@gmail.com> <07b3ed31-66ac-74e0-d7d0-ff728c94eb32@outer-planes.net>
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Message-ID: <bd1a5c3a-bd16-e48a-617d-e5250afe75dd@gmail.com>
Date: Sun, 12 Nov 2017 04:12:09 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <07b3ed31-66ac-74e0-d7d0-ff728c94eb32@outer-planes.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="WbppQ6Ipkc25HKXALOhmgWEVqUwUgetR6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/y42H9HTcAApHv5S6GBbBz0S9Xbc>
Subject: Re: [Json] jsonbis - Not having a session at IETF 100
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 12 Nov 2017 12:12:19 -0000


On 11/11/2017 08:14 PM, Matthew A. Miller wrote:
> On 17/11/09 23:07, Peter F. Patel-Schneider wrote:
>>
>> On 11/09/2017 06:40 AM, Alexey Melnikov wrote:
>>> On Wed, Nov 8, 2017, at 04:09 PM, Julian Reschke wrote:
>>>> On 2017-11-08 16:43, Alexey Melnikov wrote:
>>>>> On 08/11/2017 15:39, Julian Reschke wrote:
>>>>>
>>>>>> On 2017-09-29 15:05, IETF Meeting Session Request Tool wrote:
>>>>>>> Alexey Melnikov, a chair of the jsonbis working group, indicated that 
>>>>>>> the jsonbis working group does not plan to hold a session at IETF 100.
>>>>>>>
>>>>>>> This message was generated and sent by the IETF Meeting Session 
>>>>>>> Request Tool.
>>>>>>> ...
>>>>>> ...but can we have an update about what's going on with 
>>>>>> draft-ietf-jsonbis-rfc7159bis nevertheless?
>>>>> We are waiting for ECMA to publish their document in early December.
>>>> Aha, thanks.
>>>>
>>>> Is there way to preview what they intend to publish?
>>> I've seen a copy of the to-be-published document, but I am not sure if
>>> it would be Ok to distribute it publicly.
>>>
>>> _______________________________________________
>>> json mailing list
>>> json@ietf.org
>>> https://www.ietf.org/mailman/listinfo/json
>> So what is the process for publishing the final version of the IETF document
>> then? If there isn't a chance for us to look at the ECMA document beforehand
>> then how can we check that it is suitable to be a normative reference?
>>
> The AD and chair have reviewed the upcoming revision to ECMA-404, and
> find their changes meet with expectations.
>
> We ask that you trust us to work with Ecma to act in everyone's best
> interests.
>
>
> Thank you,
>
> -  JSONbis Chair & Responsible AD


Standards processes are indeed built on trust.  I trust the editor of a
standards document to do a faithful job in keeping the document in tune with
the desires of the group writing the standard.  However, I get a chance to
verify my trust by being able to see and comment on the document before it
becomes a standard.

I trust you to try to get the new ECMA document in what you think is a
suitable shape and I trust you to try to keep what you think is suitable
aligned with what the group here has said would be suitable.  But if I don't
get a chance to see that normative document before the IETF document becomes
final, then I cannot provide the informed assent to its publication that is
needed as part of any reasonable standards effort.

Peter F. Patel-Schneider
Nuance Communications