IETF Logo Mail Archive

Re: [domainrep] Possible erratum in RFC 7071: "integer" in JSON

Carsten Bormann <cabo@tzi.org> Wed, 21 August 2019 22:48 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BF1120130 for <domainrep@ietfa.amsl.com>; Wed, 21 Aug 2019 15:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 yYVfbt8PoMWv for <domainrep@ietfa.amsl.com>; Wed, 21 Aug 2019 15:48:10 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0773120110 for <domainrep@ietf.org>; Wed, 21 Aug 2019 15:48:09 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46DN9N1QqDzyTK; Thu, 22 Aug 2019 00:48:08 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAL0qLwaWcQs_h4nR0zGbgdbjV-QsZBsGRf3DpDTYPvB=kdvvyQ@mail.gmail.com>
Date: Thu, 22 Aug 2019 00:48:07 +0200
Cc: Ulysse Carion <ulysse@segment.com>, domainrep@ietf.org
X-Mao-Original-Outgoing-Id: 588120485.810873-ce1383a7bc517e3810f08b46a2ce65e4
Content-Transfer-Encoding: quoted-printable
Message-Id: <CEF530C3-7AF6-4BAE-BFBE-37BC8A08AD15@tzi.org>
References: <CAJK=1Rhc-Xam1KvS3UZrC4WeOBLVj06Du1U4bsLGs6+53_TZag@mail.gmail.com> <CAL0qLwaWcQs_h4nR0zGbgdbjV-QsZBsGRf3DpDTYPvB=kdvvyQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/domainrep/VnAFDoGMTuJXMAnwZpKfrRABTxc>
Subject: Re: [domainrep] Possible erratum in RFC 7071: "integer" in JSON
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Domain Reputation discussion list <domainrep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/domainrep>, <mailto:domainrep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/domainrep/>
List-Post: <mailto:domainrep@ietf.org>
List-Help: <mailto:domainrep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/domainrep>, <mailto:domainrep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 22:48:12 -0000

On Aug 22, 2019, at 00:08, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> INTEGER: a NUMBER as defined in Section 2.4 of [JSON] but without any fraction component, i.e., conforming to the “int" ABNF in that section.

But that’s not how it works: You don’t get to change JSON’s ABNF as a JSON application.
The numbers 2, 2.0, 2.00, 2e0, 2.0e0, 0.2e1 etc. all mean exactly the same thing in JSON.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email