Re: [Json] Normative reference reasoning and logistics

Mark Nottingham <mnot@mnot.net> Tue, 03 May 2016 02:46 UTC

Return-Path: <mnot@mnot.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 6707F12B042 for <json@ietfa.amsl.com>; Mon, 2 May 2016 19:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 zB2RPOXbHeJu for <json@ietfa.amsl.com>; Mon, 2 May 2016 19:46:01 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1705412B01C for <json@ietf.org>; Mon, 2 May 2016 19:46:01 -0700 (PDT)
Received: from [192.168.1.101] (unknown [120.149.194.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9D30622E1F3; Mon, 2 May 2016 22:45:58 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <896CAFF7-A29E-48F1-B2DA-F4A09CD9B313@cisco.com>
Date: Tue, 3 May 2016 12:45:55 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1499328-45D8-4E75-A25E-1F37823B706A@mnot.net>
References: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com> <CAHBU6isb+A4crvdEMkMqhreXLcox3Q5O-TJeOYvb4vvUqYupmg@mail.gmail.com> <978CE59C-19EA-44E0-8AA9-620B854ACB6F@cisco.com> <CAHBU6ivnZ5x1vno61jTH8ou4PhNesVf9eb5TA_wb_3GEqEsQxA@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E13BD0AFB47F@WSMSG3153V.srv.dir.telstra.com> <896CAFF7-A29E-48F1-B2DA-F4A09CD9B313@cisco.com>
To: Joe Hildebrand <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/hUMG2lWcnYrOCH9wMvJoU-n0UGY>
Cc: Tim Bray <tbray@textuality.com>, "Manger, James" <James.H.Manger@team.telstra.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Normative reference reasoning and logistics
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: Tue, 03 May 2016 02:46:03 -0000

> On 3 May 2016, at 2:17 AM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com>; wrote:
> 
> Sounds more harmful than helpful to again change the RFC number that defines JSON — rfc4627, rfc7158, rfc7159, rfcXXXX — for what is
> supposed to be a simple and stable format.
> 
> Stick the text in as an errata marked “held for document update”; or stick it in its own RFC that updates rfc7159 (bit weird?); or
> in a liaison note to ECMA.

For better or worse, that's how things work. If we stop progressing documents to get stable RFC numbers, something's really broken. 

Cheers,



--
Mark Nottingham   https://www.mnot.net/