1452   Multicast vs Unicast MAC addresses cannot be specified

Created: 13 Oct 2015

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)





Category: No impact on this part


The communication section section has only a "MAC-Address" which does not distinguish Unicast from Multicast addresses. These can be checked by the schema if defined.


<xs:complexType name="tP_MAC-Address-Unicast">
<xs:restriction base="tP">
<xs:pattern value="[0-9A-F][02468ACE]\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}"/>
<xs:attribute name="type" type="tPTypeEnum" use="required" fixed="MAC-Address-Unicast"/>

<xs:complexType name="tP_MAC-Address-Multicast">
<xs:restriction base="tP">
<xs:pattern value="[0-9A-F][13579BDF]\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}\-[0-9A-F]{2}"/>
<xs:attribute name="type" type="tPTypeEnum" use="required" fixed="MAC-Address-Multicast"/>

Discussion Created Status
08 Dec 15 In Force (green)
Not accepted. A MAC Address may be unicast or multicast. If a special version shall be syntactically checked, appropriate XSI types could be used. Anything else is a tool issue and cannot be checked at syntax level. 04 Nov 15 Ballot Period
I do not see that added value of the proposal:
1) if breaks the backward comaptibility
2) it does not avoid that tools are using the wrong P address type to a dedicated service

It only propose of such xsi types to check the content of an address.
The existing type MAC-Address allows already today to set Layer Mutlicast, Broadcast and unicast addresses.

The tool testing should ensure that the configured addresses in the different data flow configuration test cases are as expected by the standard: goose and Msv multicast; Sv unicast.
16 Oct 15 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.