1503   Is it mandatory to check confRev for GOOSE subscriber? And if yes, should it be a standardized rule?

Created: 30 Jun 2016

Status: Not Applicable

Part: Part 8-1 (2011; Edition 2)




Paragraph: 96

Category: Issue for edition 2 of this part


-8 recommended checking of ConfRev:
"NOTE The reception of a GOOSE message with a different ConfRev value from what was expected indicates a
potential configuration mismatch. It is recommended that an implementation may need to try to automatically
reconcile the difference or not process the received GOOSE if reconciliation is not possible. This is a local
implementation issue. "
The question is:
confRev is one of goose header elements (goid, gocbreference, ...), should ConfRev checking rule be standardized (rule means: confRev is checked Y/N? How is it check?)?
And if yes, what about the rest of header elements that are not mentioned in standard?


Either standardize all goose headers' checking rules (goid, gocbreference, ...),
or keep confRev checking rule a local implementation, defined by subscriber, like the rest of goose header elements

Discussion Created Status
As discussed during the UCA testing committee, this item is not an SCSM 8-1 issue, but a 7-2 ACSI Issue.
Please enter a comment to 7-2 Ed2.1 CDV currently in circulation over your national committee.
30 Jun 16 Not Applicable


Privacy | Contact | Disclaimer

Tissue DB v.