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

4-June-07 P1901_PRO_016_r0
7.4.3 OVLAN Ingress filtering
If any frame coming into the bridge has a valid OVLAN identifier, OVLAN is enabled and its OVLAN identifier is
not included in the OVLAN list for such port, the frame is discarded, unless the frame has FFF as identifier. It is
passed otherwise.
7.4.4 OVLAN Egress filtering
If any frame going out of the bridge has a valid OVLAN identifier and this OVLAN identifier is not included the
OVLAN list for such port, the frame is discarded, unless the frame has FFF as identifier. It is passed otherwise.
7.4.5 OVLAN management
If a unit has OVLAN functionality, OVLAN parameters per port (OVLAN enabled / disabled, tagged only, POVID,
and OVLAN_list) shall be modifiable by a management process.
The management process shall be executable remotely.
7.5 Sending broadcast/multicast Ethernet frames
When sending a broadcast/multicast Ethernet frame or when flooding the ports of the bridge, two main ways to
transmit multicast IEEE 802.3 frame con be configured.
In the first option the bridging function shall provide the list of BPL ports related to this transfer as part of the
Eth.req service primitive
In the second option, the bridging function shall provide a native multicast BPL port related to this transfer as part
of the Eth.req service primitive.
The bridging function shall also support management of associations of multicast groups to native ports.
The association of a multicast group to a native multicast port is done in two stages:
a) The remote nodes belonging to a multicast group are associated to the native multicast port
For this, the unit shall send Port Solver Protocol Multicast Port packets to the nodes selected to become associated
to the native multicast port. The aim of such packets is to add in the Port Solver Table of each destination node that
wants to join the multicast flow the selected Local native multicast Port as Second Remote Port (RP2).
Submission page 176 UPA-OPERA