Re: [domainrep] Possible erratum in RFC 7071: "integer" in JSON
Ulysse Carion <ulysse@segment.com> Wed, 21 August 2019 22:09 UTC
Return-Path: <ulysse@segment.com>
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 5516A1200A1 for <domainrep@ietfa.amsl.com>; Wed, 21 Aug 2019 15:09:55 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=segment.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 esE6NpnWzTTs for <domainrep@ietfa.amsl.com>; Wed, 21 Aug 2019 15:09:53 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 EF9081200F4 for <domainrep@ietf.org>; Wed, 21 Aug 2019 15:09:51 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id 18so7785500ioe.10 for <domainrep@ietf.org>; Wed, 21 Aug 2019 15:09:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=segment.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OOzKbvVRlvA4MkH4BsFJRC7Bje6tsEHaikkvFPcGz0A=; b=EtnFuD88mSTpQI1YE9mwRRw6LNS6c31b9dChzBQvToTd09AuKYZjJ/zpU/t2/GnRPa 55Th1n4gwTOaNYGlgtxMCB0tuCyCl6pKhVO+USnX486akvdiO5zPltasIAigFmT04fC+ EfxmIV2e0EpxSp6MI3gRlu+CgeN5fED0/+d4g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OOzKbvVRlvA4MkH4BsFJRC7Bje6tsEHaikkvFPcGz0A=; b=Pv3qjRoSlFpgFs/420CqQZy7dGmdKKIfrYcIBOcxYKZqbG3UWYfSM1FldZZxJdHnkY y5u0GMPxmHvnqGZAMaMhbt+rSGbtetIXcK7K95FqKvByu1Hingb7sc3IFfekQ1F10H7u O2qiDkKVwHqH20ovmxCsy9nxoOSfkp7haz65RqtcuIUdONzFTFFPcQoHX3/BhtRpj3fy NtdhR3E/sxUaBzqh2AfsfM1UmEmnRAwzUEbPfJrJp7Hyy81SfzCSk6VdUMpwSe8SWDiX PB18FA9F95CeBkBt5kYsIX06Iyuxk78oGwfnY4FIs+KYoJDMjvmipv7ssoQFuGQrnOyp ublw==
X-Gm-Message-State: APjAAAXlsxCj/UCa/s9LFHmlM3xI4coL7SkxGix2MpmgoS672AsvX2bt Q6IeQCaq45lkm9ZsXSEXvj4JmnlLoukUanN0Vk9y8A==
X-Google-Smtp-Source: APXvYqy5k7Ua+QVcG5dA3bRNlx5faw9NJxOCaqdh3OAQ3jxUw36U9jzboFJ8HG1c1wxhbXgXzC/G63gpdhA9RMaYU8s=
X-Received: by 2002:a5d:888a:: with SMTP id d10mr5481968ioo.201.1566425391167; Wed, 21 Aug 2019 15:09:51 -0700 (PDT)
MIME-Version: 1.0
References: <CAJK=1Rhc-Xam1KvS3UZrC4WeOBLVj06Du1U4bsLGs6+53_TZag@mail.gmail.com> <CAL0qLwaWcQs_h4nR0zGbgdbjV-QsZBsGRf3DpDTYPvB=kdvvyQ@mail.gmail.com>
In-Reply-To: <CAL0qLwaWcQs_h4nR0zGbgdbjV-QsZBsGRf3DpDTYPvB=kdvvyQ@mail.gmail.com>
From: Ulysse Carion <ulysse@segment.com>
Date: Wed, 21 Aug 2019 15:09:40 -0700
Message-ID: <CAJK=1Ri17dC1KD5wq_RDBjKF+gvZ2a7ECtDU0a+f=cqmDb=ESw@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: domainrep@ietf.org, Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/domainrep/4LO2-U6phCjUOIObIxSS7e4IkX8>
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:09:55 -0000
Makes sense! Is adding an erratum to the RFC in order? On Wed, Aug 21, 2019 at 3:08 PM Murray S. Kucherawy <superuser@gmail.com> wrote: > > You're correct about the intent. Something like this: > > 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. > > -MSK > > On Mon, Aug 12, 2019 at 4:54 PM Ulysse Carion <ulysse@segment.com> wrote: >> >> Hi all, >> >> Section 6.2.1 of RFC 7071 >> (https://tools.ietf.org/html/rfc7071#section-6.2.1) says: >> >> > INTEGER: an "integer" as defined in Section 2.4 of [JSON] >> >> But JSON does not explicitly define integers. Perhaps the "int" ABNF >> rule was what was meant? >> >> The word "integer" only appears in passing here: >> https://tools.ietf.org/html/rfc4627#section-2.4 >> >> Thanks, >> Ulysse >> >> _______________________________________________ >> domainrep mailing list >> domainrep@ietf.org >> https://www.ietf.org/mailman/listinfo/domainrep
- [domainrep] Possible erratum in RFC 7071: "intege… Ulysse Carion
- Re: [domainrep] Possible erratum in RFC 7071: "in… Murray S. Kucherawy
- Re: [domainrep] Possible erratum in RFC 7071: "in… Ulysse Carion
- Re: [domainrep] Possible erratum in RFC 7071: "in… Carsten Bormann