IEEE 802.1ah-2008

IEEE 802.1ah-2008 IEEE Standard for Local and metropolitan area networks -- Virtual Bridged Local Area Networks Amendment 7: Provider Backbone Bridges

Amendment by IEEE, 08/14/2008

More details




(price reduced by 56 %)

Full Description


Insert the following text and bullets immediately after bullet z:To allow scaling of Provider Networks to at least 224 Service Virtual LANs, this standard further specifiesthe operation of Provider Backbone Bridges (PBBs) by means of an architecture and bridge protocolscompatible and interoperable with Provider Bridged Network protocols and equipment, allowinginterconnection of multiple Provider Bridged Networks. To this end, itaa) Introduces Backbone Edge Bridges that, by exchanging backbone frames that encapsulate theaddresses, VLAN tags, and data of customer frames, support the virtual, media independent,equivalent of a number of independent instances of the service provided by media dependent frametransmission procedures.ab) Extends the parameters of the Internal Sublayer Service (ISS) and Enhanced Internal SublayerService (EISS) to include a connection identifier, capable of referencing the backbone addresses andother parameters, used to convey customer frames from one Backbone Edge Bridge (BEB) to all, orone of, the other BEBs supporting a particular backbone service Specifies the format of the Backbone Service Instance tag (I-TAG) that encapsulates the customeraddresses, and introduces a Backbone Service Instance Identifier (I-SID) that allows each BEB tosupport a number of backbone service instances and permits the unambiguous identification of up to224 backbone service instances within a single Provider Backbone Bridged Network (PBBN).ad) Provides a model of Backbone Edge Bridge operation in terms of VLAN-aware bridge componentsthat allows the use of Provider Bridges as Backbone Core Bridges, with PBBN traffic carried asframes containing I-TAGs on particular Backbone VLANs (B-VLANs) potentially coexisting withPBN traffic carried as frames without I-TAGs on other Backbone Specifies the interfaces that a Provider Backbone Bridged Network can provide to transport service frames. These comprise a Port-based service interface that assigns all received untagged andpriority-tagged frames to a single S-VLAN transported over a single backbone service instance, anS-tagged service interface capable of mapping individual S-VLANs to different backbone serviceinstances, and an I-tagged service interface capable of mapping frames from one set of backboneservice instances to Describes the use of redundant bridges and access LANs to protect backbone service access against failure of any of those systems or Specifies the management of Backbone Edge Bridges in terms of the model of operation [item ad)above], making use of defined management objects for the individual VLAN-aware bridgecomponents, and adding managed objects to facilitate service creation.ah) Describes the use of connectivity fault management (CFM) to detect and isolate faults in theconnectivity provided to individual S-VLANs across the PBBN, in the connectivity provided to thegroup of S-VLANs supported by a single backbone service instance (identified by an I-SID), and inthe connectivity provided to individual B-VLANs within the backbone Specifies extensions to the Multiple Spanning Tree Protocol (MSTP) to allow networkadministrators to protect against loops through peered PBBNs without requiring coupling ofspanning trees that operate independently for each PBBN.


Amendment Standard - Inactive - Superseded.This amendment defines an architecture and bridge protocols for interconnection ofmultiple Provider Bridged Networks, allowing a Provider to support up to 2^24 service instances.

Contact us