This amendment supports provisioning systems that explicitly select traffic engineered paths within Provider Backbone Bridged networks.

Insert the following text and bullets immediately after bullet z re-lettering as needed: This standard specifies protocols, procedures, and managed objects to allow support of provisioning systems that explicitly select traffic engineered paths within Provider Backbone Bridged Networks by allowing a network operator to disable unknown destination address forwarding, source address learning and spanning tree protocols for administratively selected VLAN Identifiers, while allowing other network control protocols to dynamically determine active topologies for other services. These interoperable capabilities are supported by management of individual bridges by SNMP using an SMIv2 MIB, by extensions to the other control protocols specified in this standard, by the use of CFM with the addresses and VLAN Identifiers that specify traffic engineered connections, and by 1:1 path protection switching capable of load sharing. To this end, it: a) Enables construction of active topologies by an external agent that is responsible for setting up Ethernet Switched Paths (ESPs) by splitting the B-VID space between distributed spanning tree protocols and provisioned control. b) Supports discard of frames with unknown destination addresses for B-VIDs under provisioned control. c) Supports the operation of Continuity Check, Loopback, and Linktrace protocols on provisioned traffic engineered paths. d) Supports 1:1 protection switching capable of load sharing for Traffic Engineered service instances. e) Provides required extension to SNMP management by SMIv2 MIB modules. This standard does not specify operation of Ethernet Switched Paths (ESPs) through multiple Provider Backbone Bridge Traffic Engineered (PBB-TE) Regions. All the Backbone Edge Bridges specified for use in a PBB-TE Region are IB-BEBs.