2006 Issues with R-GOOSE/R-SV definitions regarding VLAN
- Created
- 04 Nov 2025
- Status
- Analysis Of CompatibilityBeing checked for its effect on existing implementations, so that any break with an earlier edition is known and recorded. Any signed-in reader may comment. Show the workflow
- Part
- Part 8-1 (2020; Edition 2.1)
- Links
- #2049 Issues with R-GOOSE/R-SV definitions regarding VLAN
- Page
- 168
- Clause
- 25.3.3
- Paragraph
- Table 164
Issue
The GSE/SMV over UDP/IP SCL definitions contain the following issues:
1) VLAN-PRIORITY and VLAN-ID are defined only for the publisher LAN. There is no definition of VLAN priority and VLAN-ID for the subsriber side. It is not explicitly specified but due to the lack of definition it is assumed that R-GOOSE/R-SV packets are always sent without VLAN tag at the subscriber side. This is a disadvantage.
2) The GOOSE/SV address parameters are defined with per stream granularity, not considering the IP address and VLAN information configured at the publisher's sending interface. This may violate the general rule of IP communication that IP packets sent by hosts contain
the address information of the sending IP interface. Edge routers may drop multicast packets in case of IP address mismatch as result of the RPF (reverse path forwarding) check.
Please find the details in the attached problem statement document.
Proposal
The proposed solution is contained in the attached solution proposal document.
One file is attached to this tissue. Sign in to open it.
| Discussion | Created |
|---|---|
|
Analysis Of Compatibility
Editor group:
Move to analysis of compatibility. There was no standardized way to configure what are the properties of the IP End Point of the subscriber that are used to sent the join message. It can be the IP Address of the MMS End Point of the subscriber, without VLAN, or not being documented in the SCD using VLAN. Old implementation will have to change to read and understand the configured properties in the SCD. As long as old implementations do not read the configured properties from SCD, it is a local issue to configure the IP end point property of the routable subscriber. |
06 Oct 26 |
| Verify Draft Implementation Move to verify draft implementation. | 01 Sep 26 |
|
Drafting Implementation
Tissue 2049 has been created for part 6.
The drafting solution is available as attachement. One file is attached to this tissue. Sign in to open it. |
14 Aug 26 |
|
Discussion (red)
Editor Group: add on:
A tissue in PArt 6 would be needed to specify the needed schema extension in the SCL namespace. |
04 Aug 26 |
|
Discussion (red)
Editor group:
Prpose to qualify the IEDName element for Routable transmission with a reference to the SubscriberIpEndPoint (rSubscriberIPEndPointRef). The referenced ConnectedAP from the IEDName.apRef will contain an RSubscriberIPEndPoint with an id and a set of P to qualify the IP end point of the subscriber including the VLAN associated to this ip end point. A connectedAP may contain more than RSubscriberIPEndPoint , one for each configure IP End Point, when needed. Drafting solution in process. |
04 Aug 26 |