207 GOOSE fields order
- Created
- 19 Sep 2005
- Status
- Not ApplicableClosed: the issue falls outside the scope of the standard. No further comments are taken. Show the workflow
- Part
- Part 8-1 (2004)
- Links
- None
- Page
- 111-115
- Clause
- Annex A
- Paragraph
- Category
- No impact on this part
Issue
In a GOOSE PDU, Annex C prescribes a certain order of the leading fields. The field IECGoosePdu (improperly named APDU in Annex C) does not prescribe the order of its fields since only the ASN.1 definition is given, in which SEQUENCE fields may come in any order. This makes decoding unnecesserily difficult, since posibly the whole PDU must be parsed to know from the sqNum that nothing has changed.
Proposal
To simplify decoding, the elements of the IECGoosePdu shall be transmitted in order of increasing tag values.
| Discussion | Created |
|---|---|
| Discussion (red) Changed to red. | 20 Sep 05 |
|
Triage
The use of ASN.1 SEQUENCE prescribes the order. SEQUENCE is not SET, thus the sequence of fields specified in the ASN.1 is correct and precise. No change is needed.
|
19 Sep 05 |