541   Ethertype for GOOSE

Created: 03 Jul 2007

Status: In Force (green)

Part: Part 8-1 (2004)


Page: 19

Clause: 5.1


Issue: "Messages of Type 1 and Type 1A are mapped to distinct Ethertypes to optimise decoding of received messages." (61850-8-1) In annex C, table C.2 is defined only one GOOSE ethertype. For optimization of performance it would be better to seperate Goose Trip from other Goose messages.

Proposal: Include in table C.2 a special ethertype only used by Goose trip messages. Alternative it can be defined different ranges for APPID.

Discussion Created Status
turned to green. 26 Mar 08 In Force (green)
Fastmessage GOOSE (from part 5) will have the Most significant byte of the Ethertype APPID set to a value of zero.

Trip GOOSE will have a value of 0x02 in the most significant byte of the Ethertype APPID.
14 Dec 07 Ballot Period
There is no need for a distinct Ethertype. Faster sending is assured by higher priority, not by Ethertype. Separate filtering can be assured by different APPID or Multicast addresses. I suggest to make clear that 'distinct' refers to SAV, and not to different types of GOOSE. 28 Sep 07 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.