a)Conform to the relevant MAC standards technologies implemented at its Ports, as specified in 6.4 and 6.5.
b)Conform to IEEE Std 802.2 for the implementation of a class of LLC supporting Type 1 operation as required by 7.3 and 7.1.2.
c)Relay and filter frames as described in 7.1 and specified in 7.5, 7.6, 7.7, and 7.9.
d)Maintain the information required to support Basic Filtering Services, as described in 6.6 and 7.1 and specified in 7.5, 7.8, and 7.9.
f)Implement the Rapid Spanning Tree Protocol, as specified in Clause 17.
g)Encode transmitted BPDUs and validate received BPDUs as specified in Clause 9.
1)Filtering Database Size, the maximum number of entries.
2)Permanent Database Size, the maximum number of entries.
i)Specify the following performance characteristics of the implementation
1)A Guaranteed Port Filtering Rate for each Bridge Port
2)A Guaranteed Bridge Relaying Rate for the Bridge
3)The related time intervals TF and TR for these parameters as specified in Clause 16.
Operation of the Bridge within the specified parameters shall not violate any of the other conformance provisions of this standard.
a)Support management of the Bridge. Bridges claiming to support management shall support all the management objects and operations for all implemented capabilities as defined in Clause 14.
b)Support the use of a remote management protocol. Bridges claiming to support remote management shall
1)State which remote management protocol standard(s) or specification(s) are supported.
2)State which standard(s) or specification(s) for managed object definitions and encodings are supported for use by the remote management protocol.
c)Support multiple Traffic Classes for relaying and filtering frames through one or more outbound Ports, controlling the mapping of the priority of forwarded frames as specified in 6.4, 7.5.1, and 7.7.
d)Support Extended Filtering Services for relaying and filtering frames as described in 7.1 and specified in 7.5, 7.6, 7.7, and 7.9. Bridges claiming to support of Extended Filtering Services shall
1)Implement the GARP Multicast Registration Protocol (GMRP), as specified in Clause 10.
2)Implement the Generic Attribute Registration Protocol (GARP), in support of the GMRP Application as specified in Clause 12.
NOTE—The term capability is used to describe a set of related detailed provisions of this standard. Each capability can comprise both mandatory provisions, required if implementation of the capability is to be claimed, and optional provisions. Each detailed provision is specified in one or more of the other clauses of this standard. The Protocol Implementation Conformance Statement (PICS), described in 5.3, provides a useful checklist of these provisions.
The supplier of an implementation that is claimed to conform to this standard shall complete a copy of the PICS proforma provided in Annex A and shall provide the information necessary to identify both the supplier and the implementation.
Support of the relevant managed objects and management operations specified in Clause 14, and support of the use of SNMP to access them, is highly recommended.
MAC-specific bridging methods may exist. Use of a MAC-specific bridging method and the method specified in this standard on the same LAN shall
a)Not prevent communication between stations in a Bridged Local Area Network.
c)Preserve the characteristics of each bridging method within its own domain.
d)Allow both bridging techniques to coexist simultaneously on a LAN without adverse interaction.