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

4-June-07 P1901_PRO_016_r0
b) IEEE Std 802.1D Management (clause 14 of IEEE 802.1D-2004) requirements
c) IEEE Std 802.1D Remote Management (clause 5.2 of IEEE 802.1D-2004) requirements
as modified by the provisions of this standard
The permanent filtering database, as defined in IEEE 802.1D-2004 clause 7.9 shall have a minimum size of 8
entries.
The dynamic filtering database, as defined in IEEE 802.1D-2004 clause 7.9 shall have a minimum size of 64
entries.
7.3 IEEE 802.1Q conformance
The bridging function shall support VLAN according to IEEE Std 802.1Q requirements for VLAN-aware bridges,
as modified by the provisions of this standard.
The bridging function shall support a minimum of 32 VLANs.
7.4 OVLAN Function
7.4.1 General
The OVLAN functionality is based on IEEE 802.1Q Virtual LAN (VLAN), but does not substitute the IEEE
802.1Q functionality. Instead, if enabled, it shall work independtly of IEEE 802.1Q functionality.
OVLAN function is is aimed to:
• Avoid packets from one customer leaking into a neighbor customer (for security reasons).
• Avoid packets from one BPL sub-network (for example, an LV cell) leaking into another BPL sub-network
(for security reasons and in order to avoid the problem of bridge tables filling up with unnecessary MAC
addresses).
In such cases, as IEEE 802.1Q VIDs are limited to less than 4096, a large network can rapidly run out of VLANs
numbers if they are used for customer isolation, OVLAN should be used, leaving IEEE 802.1Q for its traditional
VLAN purposes.
The following processes are defined for OVLAN function
Submission page 174 UPA-OPERA