IETF Logo Mail Archive

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

"Matthew A. Miller" <linuxwolf+ietf@outer-planes.net> Sun, 12 November 2017 04:14 UTC

Return-Path: <linuxwolf+ietf@outer-planes.net>
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 6EC17126DD9 for <json@ietfa.amsl.com>; Sat, 11 Nov 2017 20:14:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=outer-planes-net.20150623.gappssmtp.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 Vw2ndPxiKZPX for <json@ietfa.amsl.com>; Sat, 11 Nov 2017 20:14:55 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (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 E58F61201FA for <json@ietf.org>; Sat, 11 Nov 2017 20:14:54 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id p9so10285868pgc.8 for <json@ietf.org>; Sat, 11 Nov 2017 20:14:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=5C0lzVr/kcggU8aiRwjk8fQcD1dpPPKz6j80Cf+iXHw=; b=LQhUd8Q8RRMFqHWP534lP/WfigQ3z7CaSLhBHjG5Nvvw8Vp9Jdoz5BezQPtbHPBe6l UiIcrccz1SBc1K45EXuGHRKR/rDBiy/kDUwrHHlpQyQFV6LFrOjE/FRNQTxAErifi4Qg 4ILvZ/7yQ/Xiq57/3dIvM1kBwnsHFqacC/+a90cLzFEhlHBs2Ow2wCCj4BR/4aKYqEcr U4Tmjz19F2baxIukOs/c2a5+j7iwstSsf4yJPqQgGTdysdi1/wXz6Q6DK2q1LMGveJLf cPowsDB1DYbDNMUrgpGD8KIj6Z/D1vrjOhgvTWkK0jLDRyNzzuwgxFoPjGFMJxCrMGBe jolQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=5C0lzVr/kcggU8aiRwjk8fQcD1dpPPKz6j80Cf+iXHw=; b=EHrbdvXHAcmxrb4d2u5/C8GcVXw++ZOtM5BpwgKgALu2HuUBg+yVvpw05YZg9t1XAa 2xP8VJqHTn85ylD3YnmLKxY5VTAajhgoHa7RP7QQm+raJsA3cBdIsMANMLDWP/dMzE7X u42ebSGEKYZyp0uas5MAa2f4JYGca7h26VbCwN9JHrW6HnqVFCib5iw2sad9q8l3G5wO xiwcQ0Ecs+Y7NohI8hgPfQd5v0vaEI9A4sN5f03eEbbeDVtZeOscqhYqCz3lpsmpsK08 9eyi8LFQeHTTyAxzENYKgVxh0KeDgd2WafyARXD6z4Qv+26geSc7WYXHHuVsqg1WfcS0 D/lA==
X-Gm-Message-State: AJaThX6HWjSlp3eEzQBwtm53Lm2xxUYnyYlvkXPOf9COVEjl7ayINBxG i2fRlPnILecpE6LsCjmEnKZiyg==
X-Google-Smtp-Source: AGs4zMatYdMAxLhRGsdjWXbZOxLT3IEHfvl5bUSHTFRNldMnAw5IY40YdrAj6TF7Rz4z6UX4gtZjPQ==
X-Received: by 10.159.246.16 with SMTP id b16mr5160667pls.0.1510460094394; Sat, 11 Nov 2017 20:14:54 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:58d3:2958:7466:14a2? ([2001:67c:370:128:58d3:2958:7466:14a2]) by smtp.gmail.com with ESMTPSA id e9sm8818664pgt.66.2017.11.11.20.14.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Nov 2017 20:14:53 -0800 (PST)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>, 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>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <07b3ed31-66ac-74e0-d7d0-ff728c94eb32@outer-planes.net>
Date: Sun, 12 Nov 2017 12:14:51 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <2ac7774a-59b5-86aa-cb7a-20d54127dadf@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="52r8C69bnPrqLAdXQtl8x12EUam2P9rkd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/1xTY7lKwIpGL6MKKqVQ8TWq-ugI>
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 04:14:57 -0000

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

v2.23.0 | Report a Bug | By Email