1118 Clarification of how tClientLN is used to enable Report Control Blocks
- Created
- 24 Apr 2013
- Status
- In Force (green)Closed: the solution is part of the standard. No further comments are taken. Show the workflow
- Part
- Part 6 (2009-12; Edition 2)
- Links
- None
- Page
- 77
- Clause
- 9.3.8
- Paragraph
- 6
- Category
- Issue for edition 2 of this part
Issue
The current text defines: "The RptEnabled element contains the list of client LNs for which this report shall be enabled...".
It is believed that the text is incorrect and the list of client LNs is a permission list of which client LNs can enable the report, not that the server establishes the connection to the client and automatically starts reporting.
Proposal
The text should be changed to read:
The RptEnabled element contains the list of client LNs that can enable the reporting..."
| Discussion | Created |
|---|---|
| In Force (green) | 14 Nov 13 |
|
Discussion (red)
Accepted to modify as follows:
The RptEnabled element contains the list of client LNs which can enable the reporting and for which the appropriate control block instance shall be reserved. |
22 Aug 13 |
| Discussion (red) It is true that the 8-1 mapping does not allow the server to establish the association for reporting, however this might be different for other mappings. The 'shall' is not menat to be a requirement to the server, but from the system engineer's point of view a requirement to the system. This also means that the appropriate RCB shall be reserved for this client (i.e. shall not be used by another client), even if the client itself needs to establish an association and start the reporting. Therefore no change. | 26 Apr 13 |