Re: [Json] Update reference for ABNF

Douglas Crockford <douglas@crockford.com> Thu, 06 June 2013 10:54 UTC

Return-Path: <douglas@crockford.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 1FB6D21F9704 for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 03:54:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level:
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dl5rGDEL9on2 for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 03:54:13 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 8E24D21F971F for <json@ietf.org>; Thu, 6 Jun 2013 03:54:12 -0700 (PDT)
Received: from [192.168.0.108] (173-228-7-202.dsl.static.sonic.net [173.228.7.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Lwrjc-1UHzR11f1U-017HNg; Thu, 06 Jun 2013 06:54:09 -0400
Message-ID: <51B06A44.1070008@crockford.com>
Date: Thu, 06 Jun 2013 03:53:56 -0700
From: Douglas Crockford <douglas@crockford.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <51AF9D4C.5060403@crockford.com> <60563185-85A8-4696-8B8C-9282256CFA71@vpnc.org> <255B9BB34FB7D647A506DC292726F6E1151B10582A@WSMSG3153V.srv.dir.telstra.com> <19943667-1EC6-427F-9122-EC037BDE47F1@vpnc.org> <51AFEC73.1030904@crockford.com> <2484862A-4DFF-44D7-9D9D-7E44520C5BED@vpnc.org>
In-Reply-To: <2484862A-4DFF-44D7-9D9D-7E44520C5BED@vpnc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:2V/p4danpqGVMFMx2ZOPDw0NnYJlTLH9m29r1JwfM4M +Ph2vwoFgmBYnX8iQG/tj06RPkrzpuexd5AaXR1gZ1utR8irb7 bnLcyxzbCGgBAXi5v2YorPcAvENsYkJ0NeibaMXQu3UP7FiLZ5 0sRSURTjAftEmVFo9G45MTsdbpOzY2jdCWuEcUy8nqymTFkHWH FCKAG+YeX9ynjWhKyHpMtVEDGP6ClsbxCvjH4e22mIH/9pF/j4 6IyilD6lpl5qoPRalX63N+ArE59agTONaEPsXG93dA7sIkL2IK win1qJTJi+8fXJDogY+2geB1bc3iz5/f34m4CJIzTm2pbXhoKB O5qIO8IReFxVpPGFd9j0=
Cc: json@ietf.org
Subject: Re: [Json] Update reference for ABNF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Jun 2013 10:54:19 -0000

On 6/5/2013 7:00 PM, Paul Hoffman wrote:
> On Jun 5, 2013, at 6:57 PM, Douglas Crockford <douglas@crockford.com> wrote:
>
>> On 6/5/2013 6:22 PM, Paul Hoffman wrote:
>>> On Jun 5, 2013, at 5:32 PM, "Manger, James H" <James.H.Manger@team.telstra.com> wrote:
>>>
>>>> P.S. Another little fix: update reference to ABNF from RFC4234 to RFC5234.
>>> Sounds good to me, as long as a few people promise to do a careful checking of that.
>>>
>>> --Paul Hoffman
>> Why does this matter? Does RFC5234 offer us any better precision?
> No, but in the IETF, when one RFC is updated by another, there is an expectation that a new RFC will always refer to the latter.
>
> --Paul Hoffman
Who will assure that no problems will be introduce if we do this?