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

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Thu, 09 November 2017 15:07 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 8FE7F126E01; Thu, 9 Nov 2017 07:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 YicLHsFNQhjH; Thu, 9 Nov 2017 07:07:26 -0800 (PST)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 027C1126BF6; Thu, 9 Nov 2017 07:07:25 -0800 (PST)
Received: by mail-qt0-x230.google.com with SMTP id y45so1849027qty.6; Thu, 09 Nov 2017 07:07:25 -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:content-transfer-encoding:content-language; bh=Qi2wOOZ4tB54yxF2p1HlfJVBTfnV2XYjAzU761QKU24=; b=hPtrZWxxtVNMh52e/hpEUNgelDQMUza7D93ozZCVP4vZGDeHTd072zCU8GK685G4g4 sjgpmNC9vaVcBub/AvsyMoBC9iE31UFfyjpvypQAUR/C6JIebw0WxBYMwmj3To0tbuMv 43aLoWtgSIQmvzFGtdFjBjVr6Z2Bpu8z/U98bun8TqkaYhD/MBLFo1Iny5IYV2kK5d9i z1Zrt+56z+Pv+UWqz69hLLLDkF9XkJz3O8m82wE83kMXHax/d+e1hkzPE7NiERkPhPJg H1kSr9eyPbqYN5tCykDW50MxiD10mEduISlbUIxnUR+H6B9kSYyU+8uNceaPE+AXyuSK 7yoA==
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:content-transfer-encoding :content-language; bh=Qi2wOOZ4tB54yxF2p1HlfJVBTfnV2XYjAzU761QKU24=; b=bKkW4zh5+YCsE1Vl+WuUdhBYAVPQTCybSpfxu7qBKkwyZuXmoABNqwvOr+aH0feZ8R EGfm9A4JH4uHgl57aMInurUwcy8BqYmX7sCw8O08Aqdk55O01uoZysH4+P97dYulkWDu rqyeVeUzvf7x3ab40c9wqXyeqZAhIRzHbrZ9nw1imDxzReI8vS+cnMVVpLRQ8uerukCu TCeeDQmLcujTPBE8j+SO2YyHVf+GN6VmuLALwRxHkSVBogSkWTo0VvUHvDY2rIhuoaQ+ YfbTDJQ7c0C9pG82dJhC3y0zGU09tJ692CkgxvAtkdODwqLmshSPoNuQ0jCCScSngxNY YTSw==
X-Gm-Message-State: AJaThX5ZebJVa7yelwbLgpUf2t50N93S1wPqvJSvOdXp1hhsXPV76OTC foM2Gr6e9QjsLNtyjqIQJSol9w==
X-Google-Smtp-Source: AGs4zMZaht3YNqWfqZThwsMsjaLFDKfPYgEfvQY+p1TiFqy2IqtExei39SvIQIS1TgixUAjP++HgSw==
X-Received: by 10.200.3.210 with SMTP id z18mr1288754qtg.26.1510240044866; Thu, 09 Nov 2017 07:07:24 -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 m39sm4765325qtk.30.2017.11.09.07.07.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 07:07:23 -0800 (PST)
To: 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>
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Message-ID: <2ac7774a-59b5-86aa-cb7a-20d54127dadf@gmail.com>
Date: Thu, 9 Nov 2017 07:07:22 -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: <1510238425.3520771.1167030728.53A2E4C7@webmail.messagingengine.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-CA
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/0NDTtzkERRTkJgON3a3hliZQZ2Q>
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: Thu, 09 Nov 2017 15:07:27 -0000


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?

peter