View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003755 | 10000-005: Information Model | Spec | public | 2017-02-22 16:26 | 2017-06-20 16:38 |
| Reporter | Jouni Aro | Assigned To | jeffhardingabb | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03 | ||||
| Summary | 0003755: OperationLimits: interpretation of value=0 | ||||
| Description | If the server defines any of the OperationLimits to be 0, the interpretation is not defined. I have assumed it means "unlimited", but it seems that some products interpret it as 0 - which actually does not make sense in general, IMO. So, clarification of the meaning of 0 values would be useful (and I would prefer it meaning unlimited). | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Added definition explaining zero is not valid. "Any operational limits Property that is provided shall have a non zero value." Need to add an Errata for 1.03. |
|
|
Added definition explaining zero is not valid. "Any operational limits Property that is provided shall have a non zero value." |
|
|
Reviewed and accepted Errata edited in telecon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-22 16:26 | Jouni Aro | New Issue | |
| 2017-05-16 20:45 | Jim Luth | Assigned To | => jeffhardingabb |
| 2017-05-16 20:45 | Jim Luth | Status | new => assigned |
| 2017-05-16 20:47 | jeffhardingabb | Note Added: 0008086 | |
| 2017-05-18 21:43 | jeffhardingabb | Note Added: 0008143 | |
| 2017-05-18 21:43 | jeffhardingabb | Status | assigned => resolved |
| 2017-05-18 21:43 | jeffhardingabb | Fixed in Version | => 1.04 |
| 2017-05-18 21:43 | jeffhardingabb | Resolution | open => fixed |
| 2017-06-20 16:38 | Jim Luth | Note Added: 0008237 | |
| 2017-06-20 16:38 | Jim Luth | Status | resolved => closed |
