IETF Logo Mail Archive

Re: [Json] Working Group Last Call of draft-ietf-jsonbis-rfc7159bis-02

Alexey Melnikov <aamelnikov@fastmail.fm> Sun, 31 July 2016 10:50 UTC

Return-Path: <aamelnikov@fastmail.fm>
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 77D5512D0A1; Sun, 31 Jul 2016 03:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.fm header.b=k/jmiUa2; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=jk1o/u9U
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 Mn_aDQHPDizu; Sun, 31 Jul 2016 03:50:03 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDED712B050; Sun, 31 Jul 2016 03:50:03 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A8EBA20161; Sun, 31 Jul 2016 06:50:01 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Sun, 31 Jul 2016 06:50:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=pI7ObSspAElwcG2iDVmI6JK5fIE=; b=k/jmiU a2wQEwURY/tlJvhbd1VJMcYq4QPshLb2HGqDhTTEufHLjqP+Y1Q80xj4+CkWJRkD MHOw1uJJMgarYrM5Cfiy8Y244mLUi+D+TPGc+q9Wj3iErsLGRBl0Eh8a/EXVDC2l JhXEmel9pwv4EUFYXbIWGoFP4dDzgnt5SdQGg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=pI7ObSspAElwcG2 iDVmI6JK5fIE=; b=jk1o/u9UlGJIx6gev8l+sKruZv4ztxPyN0UbUSivbPohzGg vBYMoKWmSIE8TrJjgkbL60z33amZz11qJSe23bH/B5//DrNmK6UelGX3b2e0ShAH Nz+Lfo0tHxNrzIN/KCV1auJW3Ry46b8QD/HqHyPxUlkHqMffoPPFi48diCL8=
X-Sasl-enc: Gz/nmpWqjYwqx7dgGWsw4wqdP4E4F9RA2QaD8WSYw760 1469962201
Received: from [192.168.0.6] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by mail.messagingengine.com (Postfix) with ESMTPA id 68AFDF29F4; Sun, 31 Jul 2016 06:50:01 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: iPad Mail (13F69)
In-Reply-To: <ac67f171-d8b0-f6c6-f7db-d58c01c4505f@it.aoyama.ac.jp>
Date: Sun, 31 Jul 2016 12:01:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FD90C0C-FAAA-4109-856E-DF1746B78A0D@fastmail.fm>
References: <CDD4C92E-863F-40FE-8D58-D764C9533FAA@cisco.com> <4c9504d3-c212-0b8c-0016-b31d653f15a6@gmail.com> <9E2C2681-B776-444F-84DC-9A28130DB2C1@cisco.com> <77e8ce0f-ceb3-0b69-54eb-635afbdf2a17@gmx.de> <ac67f171-d8b0-f6c6-f7db-d58c01c4505f@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/5ccTLB_TOF1vXKIXcuECtu0VyJs>
Cc: "draft-ietf-jsonbis-rfc7159bis.all@ietf.org" <draft-ietf-jsonbis-rfc7159bis.all@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "json@ietf.org" <json@ietf.org>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>, "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Subject: Re: [Json] Working Group Last Call of draft-ietf-jsonbis-rfc7159bis-02
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: Sun, 31 Jul 2016 10:50:05 -0000

Hi,

> On 30 Jul 2016, at 11:13, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> 
> I think this is an issue of trust, from both sides. For those not in a mood to trust ECMA, I suggest they trust our WG chairs and ADs.

Indeed. I can always hold publication of RFC until we see a draft version of ECMA document.

So I would encourage WG participants to concentrate on technical content of the document during the WGLC.
> 
> (If everything goes really wrong, we can always issue a revision with the reference to the ECMA side removed.)
> 
> Regards,   Martin.
> 
>> On 2016/07/29 01:13, Julian Reschke wrote:
>>> On 2016-07-28 18:05, Joe Hildebrand (jhildebr) wrote:
>>> I agree that the document should not be published as an RFC until we
>>> have the equivalent last-call doc from ECMA, and we do a coordinated
>>> publish of the two documents.  But having our side ready to go,
>>> including finishing AUTH48, will allow us to not be the bottleneck in
>>> that process.
>> 
>> Not sure. "approved" means "approved". I believe we need a mechanism
>> that makes sure that the update of 404 not only happens, but that it
>> also contains the change we expect.
>> 
>>> I believe we have adequate protections in place with Alexey not
>>> pushing the button until the right time, and making sure that the RFC
>>> Production Center is aware of the dependency to what amounts to a
>>> downref.
>>> 
>>> Would it help if we replaced the ECMA-404 reference with a a ref to
>>> ECMA-404bis (with details left out)?  That would make it *very* clear
>>> to the RPC what we intend, and would trigger processes they have in
>>> place to ensure the reference is resolved before publishing.
>> 
>> I think that helps, but it's not sufficient.
>> 
>> Best regards, Julian
>> 
>> PS: ...and we need a minor revision anyway; see prior feedback.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>> .
>>

v2.23.0 | Report a Bug | By Email