Medium Access Control (MAC) and Physical Layer (PHY) - CISE

4-June-07 P1901_PRO_016_r0
b) In the forwarding tables, the list of individual unicast ports associated to the multicast group is substituted by the
native multicast port.
If a multicast group is associated to a native multicast port, any incorporation of a new node to such multicast group
shall result in an association of such node to the native multicast port, as described in (a).
Conversely, if a node is removed from a multicast group and such multicast group is associated to a native multicast
port, the node shall be removed from the associated native multicast port. This shall be done by sending a Port
Solver Protocol Multicast Port carrying as local native multicast port the so called invalid port. (0xFF).
These actions (adding or removing a node from a native multicast port, and incorporation of the native multicast
ports to the forwarding tables) shall be supported as a result of a management action and may, optionally, be done
as a consequence of operation of group management protocols, such as IGMP or GMRP.
7.6 PB field
7.6.1 Bridging between BPL ports
When bridging between BPL ports (HE or TDR feature), the bridging function shall return within the Eth.req a PB
argument equal to the ID from which the packet has been received.
7.6.2 Bridging from a non-BPL port to a BPL port
When bridging from a non BPL-port to a BPL port, the PB argument of the Eth.req shall be set to 0.
7.7 BPL service class transmission
When bridging between BPL ports , if PCF=1 within the OVLAN argument of the received Eth.ind, the PCF and
PCP values (subfield of the OVLAN word argument) included in the subsequent Eth.req shall be kept unchanged.
7.8 Filtering multicast management messages from a BPL port
BPL Management messages are IEEE 802.2 SNAP encapsulated data units carried over an Ethernet frame which
can be either unicast or multicast. Multicast management messages make use of one of the two following multicast
addresses (referred as management multicast addresses): the STP multicast address 0x0180C2000000 (primarily
used by the STP protocol but also used for some BPL management messages) or the IEEE P1901 specific multicast
address: 0x01139D000000. Any Ethernet frame including a management multicast address shall be filtered by the
bridging function and not retransmitted to any other port. Upon reception of management messages destined to the
above two mentioned multicast addresses, the bridging function shall provide these frames to the management port.
Submission page 177 UPA-OPERA