148   OpCntRs

Created: 02 Apr 2005

Status: In Force (green)

Part: Part 7-4 (2003)



Clause: 5.7.3, 5.8.1


Category: Issue for edition 2 of this part


For the logical nodes GSAL and IARC, the data OpCntRs is explained as beeing a resetable security violation counter (in all other cases, it is a resetable operation counter).

Is that really intended?

For the GSAL, the "operation" is a security violation, and therefore it can be considered as corrrect (although it can be disputed that we differentiate the generic explanation: e.g. for all protection logical nodes we explain that data as "operation counter" and not as "trip counter")

For the LN IARC, I do not see the link with security violation.


Modify text in table for LN GSAL as follows:
"Resetable operation counter. Here, an operation is a security violation"
Modify text in table for LN IARC as follows:
"Resetable operation counter"
add the following text to the explanation in table 9:
"The operation counter may be related to the external equipment or to the function performed by a logical node"

Discussion Created Status
The counter for GSAL is a resetable security violation counter. 08 Sep 05 In Force (green)
Sorry, the conflict is between Tissue 96 and 148 about the meaning of the counter with respect to security violations 14 Aug 05 Discussion (red)
Voting time expired. Accepted 24 Jul 05 In Force (green)
See number #96 and #97.
Add in Table 9 the text proposed above.
02 Apr 05 Ballot Period


Privacy | Contact | Disclaimer

Tissue DB v.