Closed bjhargrave closed 9 years ago
Comment author: Evgeni Grigorov <e.grigorov@prosyst.com>
The issue is that InstanceId nodes are defined as integers, but 117.12.11 Instance Id: " An Object Model can define a child node InstanceId. The InstanceId node, if present, holds a long value that has the following qualities: " i.e. the instance id should be a long value.
My personal opinion is that the definition is wrong, because those instance id nodes come from TR-069. In TR-069 Amendment 4 specification, they are defines as: A.2.2.1 Instance Number Identifier: " An Instance Number is expressed as a positive integer (>=1) " Am I missing something?
Comment author: Evgeni Grigorov <e.grigorov@prosyst.com>
An errata text: "The InstanceId node, if present, holds a long value that has the following qualities" can be: The InstanceId node, if present, holds an integer value that has the following qualities
"Its value must be between 1 and Long.MAX_VALUE." can be: Its value must be between 1 and Integer.MAX_VALUE.
Comment author: Kai Hackbarth <k.hackbarth@prosyst.com>
Shige to comment on this
Comment author: Evgeni Grigorov <e.grigorov@prosyst.com>
TR-069 Specification, A.2.2.1 Instance Number Identifier: " An Instance Number is expressed as a positive integer (>=1) " Integer here is not a type, but just a integer number. That's why the definition is correct. InstanceId definition doesn't specify data types, it's up to the data model to use correct types.
Original bug ID: BZ#2394 From: Evgeni Grigorov <e.grigorov@prosyst.com> Reported version: R4 V4.3