Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Provider Backbone Bridge Traffic Engineering
open-in-new
<h2 id="principle-of-operation">Principle of operation</h2> <p>The IEEE 802.1Qay PBB-TE standard extends the functionality of <a href="/facts/IEEE_802.1ah/wblMUsQl">IEEE 802.1ah</a> Provider Backbone Bridges, adding a connection-oriented mode using <a href="/facts/Point-to-point_(network_topology)/rBYE0kke">point-to-point</a> trunks that deliver resiliency and configurable performance levels.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>A service is identified by an I-SID (Backbone Service Instance Identifier) and each service is associated with a PBB-TE trunk. Each PBB-TE trunk is identified by a triplet of B-SA, B-DA and B-VID. The B-SA and B-DA identify the source and destination bridges, respectively, that are the endpoints of the trunk. The B-VID is a backbone VLAN identifier that is used to distinguish different trunks to the same destination. The management system configures the PBB-TE trunks on all the edge and core bridges by creating static forwarding database entries; the management system is responsible for ensuring that there are no forwarding loops. </p><p>The backbone edge bridges map frames to and from an I-SID and perform the MAC header encapsulation and decapsulation functions. The core bridges act as transit nodes. The packets are forwarded based on outer <a href="/facts/VLAN/QhdJNaWX">VLAN</a> ID (B-VID) and Destination <a href="/facts/MAC_address/SVcTfgUH">MAC address</a> (B-DA). </p><p>Forwarding is based on the static forwarding database (FDB) entries; dynamic MAC learning is not used. Any incoming broadcast or multicast frames are either dropped or encapsulated as unicast within the trunk. All <a href="/facts/Destination_Lookup_Failure/5nyTQtNW">Destination Lookup Failure</a> packets are dropped rather than flooded. By eliminating any broadcasting or flooding, and by using only the loop-free forwarding paths configured by management, there is no longer any need to use a spanning tree protocol. </p><p>Path protection is provided by configuring one work and one protect B-VID for each backbone service instance. In case of work path failure (as indicated by loss of 802.1ag continuity check messages, CCMs) the source bridge swaps the B-VID value to redirect the traffic onto the preconfigured protection path within 50 ms. </p><p>PBB-TE equipment leverages <a href="/facts/Economies_of_scale/gtAYHuNT">economies of scale</a> inherent in Ethernet, promising solutions that are 30% to 40% cheaper than <a href="/facts/T-MPLS/csJ3IY3s">T-MPLS</a> networks with identical features and capabilities,<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> giving PBB-TE a better overall return on investment.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> </p> <h2 id="key-features">Key features</h2> <ul><li>Traffic and resiliency</li> <li>Secure</li> <li>Service scalability</li> <li>Operational simplicity</li> <li>Ethernet tunneling with full MPLS interoperability</li> <li>Service and transport layer independence—the services inside the tunnel could be Ethernet, IP, MPLS pseudo-wires, or VPLS.</li></ul> <h2 id="history">History</h2> <p>Provider Backbone Bridge Traffic Engineering was originally developed in 2006 as a <a href="/facts/Nortel/VYJnskS6">Nortel</a> specific protocol named Provider Backbone Transport (PBT). The company championed the technology and brought it to the IEEE 802.1 committee where it was renamed to PBB-TE and a working group, P802.1Qay, was chartered on May 7, 2007.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> 802.1Qay was in sponsor ballot from January 2009<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> to April 2009.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a> It was ratified by the <a href="/facts/IEEE_Standards_Association/2oAacBqP">IEEE Standards Association</a> on June 18, 2009.<a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a> It was published in August 2009.<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Carrier_Ethernet/d6pkk6Ha">Carrier Ethernet</a></li> <li><a href="/facts/Connection-oriented_Ethernet/DuSdx4Vt">Connection-oriented Ethernet</a></li> <li><a href="/facts/IEEE_802.1/EkN6Ltxu">IEEE 802.1</a></li> <li><a href="/facts/IEEE_802.1ah-2008/wblMUsQl">IEEE 802.1ah-2008</a>, Provider Backbone Bridges</li> <li><a href="/facts/IEEE_802.1aq/xslEBCKB">IEEE 802.1aq</a>, Shortest Path Bridging</li> <li><a href="/facts/Metro_Ethernet/mhP92HaH">Metro Ethernet</a></li></ul> <h2 id="external-links">External links</h2> <ul><li><a href="http://www.ieee802.org/1/pages/802.1ay.html">IEEE 802.1Qay project page</a> -Retrieved 29 July 2011</li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"IEEE Ratifies Computer Society-Sponsored 802.1Qay". June 23, 2009. Archived from the original on October 13, 2011. Retrieved August 6, 2011. <a href="https://web.archive.org/web/20111013120345/http://www.computer.org/portal/web/pressroom/2009/802" target="_blank">https://web.archive.org/web/20111013120345/http://www.computer.org/portal/web/pressroom/2009/802</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>EANTC. "Carrier Ethernet Services - The Future" (PDF). EANTC. Retrieved 29 May 2011. <a href="http://www.eantc.com/fileadmin/eantc/downloads/events/2007-2010/CEWC08/EANTC-CEWC08-WhitePaper_v1.1.pdf" target="_blank">http://www.eantc.com/fileadmin/eantc/downloads/events/2007-2010/CEWC08/EANTC-CEWC08-WhitePaper_v1.1.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Cummings, Joanne (2007-06-18). "The T-MPLS vs. PBT debate". <a href="http://www.networkworld.com/supp/2007/ndc4/061807-tmpls-vs-pbt.html" target="_blank">http://www.networkworld.com/supp/2007/ndc4/061807-tmpls-vs-pbt.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"Traffic engineering for Ethernet: PBT vs. T-MPLS". www.lightwaveonline.com. <a href="http://www.lightwaveonline.com/featured-articles/traffic-engineering-for-ethernet-pbt-vs-t-mpls-53438082.html" target="_blank">http://www.lightwaveonline.com/featured-articles/traffic-engineering-for-ethernet-pbt-vs-t-mpls-53438082.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Gubbins, Ed (2008-06-11). "Will PBT go away?". Telephony Online. Retrieved 2008-06-13. <a href="http://telephonyonline.com/ethernet/commentary/pbt-pbb-te-0611/index.html?imw=Y" target="_blank">http://telephonyonline.com/ethernet/commentary/pbt-pbb-te-0611/index.html?imw=Y</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"IEEE802.1Qay Project Status" (PDF). <a href="http://ieee802.org/1/files/public/docs2008/ay-saltsidis-project-status-0508-v01.pdf" target="_blank">http://ieee802.org/1/files/public/docs2008/ay-saltsidis-project-status-0508-v01.pdf</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"IEEE-SA - News, Press Releases & Updates". IEEE. Archived from the original on June 13, 2009. <a href="https://web.archive.org/web/20090613022906/http://standards.ieee.org/announcements/802.1Qay.html" target="_blank">https://web.archive.org/web/20090613022906/http://standards.ieee.org/announcements/802.1Qay.html</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"IEEE Ratifies Computer Society-Sponsored 802.1Qay". June 23, 2009. Archived from the original on October 13, 2011. Retrieved August 6, 2011. <a href="https://web.archive.org/web/20111013120345/http://www.computer.org/portal/web/pressroom/2009/802" target="_blank">https://web.archive.org/web/20111013120345/http://www.computer.org/portal/web/pressroom/2009/802</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"Virtual Bridged Local Area Networks Amendment 10: Provider Backbone Bridge Traffic Engineering" (PDF). IEEE Standard 802.1Qay-2009. August 2009. Archived from the original (PDF) on July 6, 2010. Retrieved August 6, 2011. <a href="https://web.archive.org/web/20100706172734/http://standards.ieee.org/getieee802/download/802.1Qay-2009.pdf" target="_blank">https://web.archive.org/web/20100706172734/http://standards.ieee.org/getieee802/download/802.1Qay-2009.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> </ol>