Introduction to 802.1Qaz (Enhanced Transmission Selection – ETS)

Enhanced Transmission Selection (ETS) is the second part of the Data Center Bridging puzzle (I’ve already described Priority Flow Control). It specifies two different technologies:

  • Queuing mechanisms in bridges
  • Data Center Bridging eXchange protocol: a Control/Negotiation protocol that allows bridges and hosts to negotiate QoS parameters in a bridged network.

Although some bridges from some vendors supported numerous QoS mechanisms in the past, 802.1Qaz is the first attempt to standardize a richer set of QoS behaviors than the strict priority queuing defined in 802.1p.

QoS mechanisms defined in 802.1Qaz

802.1Qaz defines three QoS mechanisms:

  • Strict priority queuing with preemption (as defined in 802.1p);
  • Credit-based shaping (as defined in 802.1Qav) … actually rate-limited strict priority queuing;
  • Enhanced Transmission Selection.

As with 802.1p and 802.1Qav, the queues are based on traffic classes which are again based on 802.1p priorities. You can group more than one priority value into a single class, but you cannot have more than eight classes.

An ETS-compliant bridge shall support at least three ETS traffic classes (so there’s no wiggle room for vendors claiming to support full DCB suite but having only strict priority queuing). The actual ETS algorithm is not specified in the 802.1Qaz draft; anything that meets the performance requirements specified in the draft can be used (this is definitely a great gray area where FUD and misinterpretations will galore and analysts will thrive).

ETS queues are low-priority queues: packets are transmitted from the ETS queues only if there’s no traffic available for transmission in credit-based shaping or strict priority queues (usually the credit-based shaping queues have higher priority than the strict priority queues).

Weighted round robin definitely meets the requirement ... but it’s not hard to meet them when the draft requires bandwidth granularity of 1% and +/-10% accuracy.

Pre-standard implementations (speculative)

As with 802.1Qbb (PFC), all current ETS implementations are pre-standard, but I don’t expect any recent (and decent) data center switch requiring a hardware upgrade, as most of them support WRR queuing based on 802.1p priorities.

DCBX is a control-plane protocol that can be easily fixed with a software upgrade.

Need more?

You’ll get an overview of DCB, FCoE and numerous other Data Center technologies in my Data Center 3.0 for Networking Engineers webinar (buy a recording or yearly subscription).

The 802.1az page has links to numerous presentations.


Post a Comment

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Ivan Pepelnjak, CCIE#1354 Emeritus, is an independent network architect. He has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced technologies since 1990. See his full profile, contact him or follow @ioshints on Twitter.