IEEE 802.1ah is an amendment to the IEEE 802.1Q networking standard which adds support for Provider Backbone Bridges. It includes an architecture and a set of protocols for routing over a provider's network, allowing interconnection of multiple provider bridge networks without losing each customer's individually defined VLANs. It was initially created by Nortel before being submitted to the IEEE 802.1 committee for standardization. The final version was approved by the IEEE in June 2008 and has been integrated into IEEE 802.1Q-2011.
The now-ubiquitous Ethernet was initially defined as a local area network (LAN) technology to interconnect the computers within a small organization in which these host computers were very close in proximity to each other. Over the years, Ethernet has become such a popular technology that it became the default Data Link Layer (OSI Layer 2) mechanism for data transport. This created a need for extending the Ethernet from a customer LAN bridging domain to service provider MAN, also known as the Provider bridging domain. For this, a 4 byte S-Tag or Service Tag, a type of Virtual LAN tag, was added to the header of the Ethernet frame in IEEE 802.1ad standard. In the service provider domain, switching was based on S-Tag and destination MAC address, and C-tag was used to create virtual LAN within the customer domain. This technology is also known as QinQ or Q-tunneling.
QinQ does not offer true separation of customer and provider domains but is merely a way to overcome the limitations on the VLAN identifier space. It can also help in separation of the customer and provider control domains when used with other features like control protocol tunneling or Per-VLAN Spanning Tree etc. There is still the problem of having too little control on the MAC addresses, since QinQ forwarding is still based on the customer destination addresses. Thus, better mechanisms are needed.
The idea of PBB is to offer complete separation of customer and provider domains. For this purpose, a new Ethernet header has been defined. This header may take multiple different forms, but the main components of the header are:
| Field description | Field name or value | Size (bytes) |
|---|---|---|
| Backbone component | ||
| Backbone destination address | B-DA | 6 |
| Backbone source address | B-SA | 6 |
| EtherType | 0x88A8 | 2 |
| Backbone VLAN identifier | B-TAG/B-VID | 2 |
| Service encapsulation | ||
| EtherType | 0x88E7 | 2 |
| Flags | Drop Eligible Indicator (DEI), and No Customer Address (NCA) indication (e.g. OAM frames) | 1 |
| Service identifier | I-SID | 3 |
| Original customer frame | ||
| Customer destination address | C-DA | 6 |
| Customer source address | C-SA | 6 |
| EtherType | 0x8100 | 2 |
| Customer VLAN identifier | C-TAG/C-VID | 2 |
| EtherType | e.g. 0x0800 | 2 |
| Customer payload | e.g. IPv4/TCP/HTTP | Variable |
PBB defines a 48-bit B-DA and 48-bit B-SA to indicate the backbone source and destination MAC addresses. It also defines a 12-bit B-VID (backbone VLAN ID) and 24-bit I-SID (Service Instance VLAN ID). The bridges in the PBB domain switch based on the B-VID and B-DA values, which contain 60 bits total. Bridges learn based on the B-SA and ingress port value and hence is completely unaware of the customer MAC addresses. I-SID allows distinguishing the services within a PBB domain.
PBB is the foundation for the IEEE 802.1Qay PBB-TE standard, which was standardized in 2009.[1]
PBB is sometimes referred to as MAC-in-MAC.[why?]
