Re: [cti-stix] Typo in range of integers

["Back, Greg" <gback@mitre.org>]

Was it because JSON don’t have a separate integer type, so those are the max/min integers that can be represented precisely in IEEE 754?

 

From: <cti-stix@lists.oasis-open.org> on behalf of John-Mark Gurney <jmg@newcontext.com>
Date: Monday, June 5, 2017 at 7:38 PM
To: Ivan Kirillov <ikirillov@mitre.org>, "Jordan, Bret" <bret.jordan@bluecoat.com>, "cti-stix@lists.oasis-open.org" <cti-stix@lists.oasis-open.org>, Sarah Kelley <sarah.kelley@cisecurity.org>
Subject: [cti-stix] Typo in range of integers

 

In Part 1 of STIX, Section 2.6, there is the text:

Unless otherwise specified, all integers MUST be capable of being represented as a signed 64-bit value ([-(2**53)+1, (2**53)-1]). 

 

It looks like 53 was used instead of 63.  Or was this changed for some reason?  A signed 64-bit has a larger range that specified here.

 

John-Mark