84   Data Name "InOv"?

Created: 16 Mar 2005

Status: In Force (green)

Part: Part 7-4 (2003)



Clause: 6

Paragraph: Table 9

Category: Issue for edition 2 of this part


Data Name InOv:
The current definition does not make sense at all. This data is defined in the SERVER. In the server's input queues we can have only control.indications, get.indications, ... An annunciation could not be lost in the server's input
queue. They could be lost in the server's output queue or in the client's INPUT queue. But we do not define the data for any problem at the client's input queue.


This Data indicates that a buffer overflow occurred
for the input buffer and important service requests
may be lost (TRUE) in the communication. Clients should
take appropriate actions as required by their applications.

Discussion Created Status
15 Jul 05 In Force (green)
Text in 7-4 should be updated as follows:
This Data indicates that messages could not received properly. Appropriate actions shall be taken.
02 Apr 05 Ballot Period
Als inputs from GOOSE messages may be lost in the input buffer. If and how this may happen depends on the implementation. The definition makes sense at all but some clarification is needed. 02 Apr 05 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.