1640   VLAN with TCP/IP

Created: 12 Dec 2018

Status: Not Applicable

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


Page: 149

Clause: 25.3.1 Client/server addressing – element “address

Paragraph: Table 160 – Allowed P-Type definitions for client/

Category: Issue for edition 2 of this part


If VLAN tagging is needed for TCP/IP communication (MMS), how we can these describe in the SCL file, because the P-types "VLAN-ID" and "VLAN-PRIORITY" are not allowed for client/server addressing (see table 160)


Add "VLAN-ID" and "VLAN-PRIORITY" to the list for allowed xs:element of “Address"

Discussion Created Status
I agree that the use of 802.1Q is out of scope of the profile. It is not out-of-scope for 8-1. 12 Dec 18 Discussion (red)
Agreed. VLAN tagging for TCP is out of scope for the endpoints and therefore MMS. 12 Dec 18 Discussion (red)
WG10 address again the VLAN configuration issue within the scope of 61850 MMS communication.
The result of the discussion for Ed2.1 is:
Table 4 shows services and protocols of the TCP/IP T-Profile client/server. The use of IEEE 802.1Q is out of scope of this standard.

Service and protocols for client/server TCP/IP T-Profile do not include the IEEE 802.1Q in Ed2.1.

12 Dec 18 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.