Skip to main content

IEEE 802.1 standards: base standards, amendments, revisions and families

· 10 min read
PhD candidate, LyRIDS (ECE) × CEDRIC (Cnam)

Papers on TSN cite "802.1Qbv-2015", "802.1Q-2018" and "802.1Q-2022" for what looks like the same mechanism. They are not contradictory: the mechanism was written as an amendment, then merged into a new edition of the base standard, which was later revised again. This post explains how IEEE 802.1 documents are created, changed, merged and grouped, using 802.1Q as the running example.

PARnew projectBase standard, edition Ncapital letters, e.g.802.1Q-2018revisionBase standard, edition N+1rolls up all changes,e.g. 802.1Q-2022and so on,at least every10 yearsAmendmentlower-case letters: 802.1Qcc;adds or changes contentCorrigendum“Cor”: fixes errors only,no new contentmerged into the next editionSupersededreplaced by thenext editionInactivereserved: not revised in 10 ywithdrawn: by ballotedition N
Figure 1. The life of an IEEE standard. A PAR starts a new base standard. While it is active, amendments add or change content and corrigenda fix errors. A revision rolls them all into a new edition, which supersedes the old one. A standard not revised within 10 years becomes inactive.Source: own drawing, after the IEEE SA maintenance FAQ and D. Pannell, How IEEE 802.1 Works, 2020, slide 4.
Abbreviations used in this post (23)
AbbreviationStands forMeaning
ATSAsynchronous Traffic ShapingIEEE 802.1Qcr: per-stream token-bucket shaping at every hop using local clocks only.
CBSCredit-Based ShaperThe IEEE 802.1Qav shaper that limits a traffic class to its reserved rate (idleSlope) with a per-queue credit. In MEF bandwidth profiles, CBS instead means Committed Burst Size.
CorCorrigendumA document that only corrects errors or ambiguities in a standard, without adding new material, for example 802.1Q-2014/Cor 1-2015.
CQFCyclic Queuing and ForwardingIEEE 802.1Qch: two queues per class alternate every cycle, so a frame advances one hop per cycle.
CSDCriteria for Standards DevelopmentThe IEEE 802 criteria (such as broad market potential and technical feasibility) used to judge whether a PAR should go forward.
IECInternational Electrotechnical CommissionThe international standards body for electrical and electronic technologies; co-owner of IEC/IEEE 60802.
IEEEInstitute of Electrical and Electronics EngineersThe professional association whose Standards Association publishes the IEEE 802 LAN/MAN standards.
LMSCLAN/MAN Standards CommitteeThe IEEE Computer Society standards committee better known as IEEE 802; its working groups include 802.1, 802.3 and 802.11.
MRPMultiple Registration ProtocolIEEE 802.1ak, now in 802.1Q: the framework for declaring and registering attributes such as VLANs, multicast addresses and streams.
MSTPMultiple Spanning Tree ProtocolIEEE 802.1s, now in 802.1Q: several spanning trees, each used by a group of VLANs.
NesComNew Standards CommitteeThe IEEE SA Standards Board committee that reviews PARs before work may start.
PARProject Authorization RequestThe document that authorises work on a new standard, amendment or revision, stating its scope and purpose; approved by the IEEE SA Standards Board on the recommendation of NesCom.
PSFPPer-Stream Filtering and PolicingIEEE 802.1Qci: stream filters, stream gates and flow meters that enforce each stream’s contract at ingress.
RevComStandards Review CommitteeThe IEEE SA Standards Board committee that checks a balloted draft followed due process before it is approved as a standard.
SASBIEEE SA Standards BoardThe board that approves PARs and standards and oversees the standards process.
SPBShortest Path BridgingIEEE 802.1aq: bridges compute shortest path trees with IS-IS, so all links can be used.
SRPStream Reservation ProtocolIEEE 802.1Qat: distributed admission control in which talkers advertise streams and listeners subscribe, reserving resources hop by hop.
TAGTechnical Advisory GroupA group of experts on a topic that crosses working groups; it may write a recommended practice.
TASTime-Aware ShaperIEEE 802.1Qbv scheduled traffic: a gate per queue, opened and closed by a repeating gate control list.
TGTask GroupA part of a working group that focuses on one subject, such as the TSN task group of IEEE 802.1.
TSNTime-Sensitive NetworkingThe set of IEEE 802.1 standards that give Ethernet bounded latency, time synchronisation and high reliability.
WGWorking GroupThe group responsible for the standards of one area, such as IEEE 802.1 (higher layer LAN protocols); only its voting members vote in working-group ballots.
YANGYet Another Next Generation (data modelling language)The language in which network configuration and state are modelled for NETCONF and RESTCONF (RFC 7950).

1. Definition: three kinds of projects​

IEEE 802.1 works on three kinds of standards projects [1][2]:

KindWhat it isHow it is namedExample
Base standardA stand-alone documentUpper-case letters after "802.1" (the rule since about 2003)802.1Q (bridging), 802.1AS (timing), 802.1CB (redundancy)
AmendmentA change to a base standard; only the amendment's changes are open to ballot commentsLower-case letters added to the name of the base standard802.1Qbv (scheduled traffic), 802.1ASdm (hot standby), 802.1CBdb (extended stream identification)
RevisionA new edition of a base standard; the whole document may be open to commentsThe base name followed by "-Rev" while in progress, then by the year802.1Q-Rev, a roll-up; 802.1AS-Rev, in which the entire document was open

Two more conventions complete the picture [1]:

  • A corrigendum ("Cor") fixes errors or ambiguities only and may not add material, for example 802.1Q-2014/Cor 1-2015.
  • A leading P marks a project that is still a draft: P802.1Q is the revision now in progress, 802.1Q-2022 the published edition.

When a revision is used only to roll up amendments into a new edition, its scope forbids adding features [2]. New functions arrive through amendments; the roll-up gathers them into one document.

2. Who writes them​

Organisation chart of the IEEE Standards Association down to the IEEE 802 committee
Figure 2. Where IEEE 802 sits in the IEEE Standards Association: the Standards Board and its committees (NesCom approves new projects, RevCom approves finished standards) above the standards committees, of which IEEE 802 is one, formed by the Computer Society.Source: J. Farkas, “IEEE 802.1 TSN TG Overview,” DetNet–TSN workshop, IEEE 802.1, 11 November 2018, slide 3; cropped, otherwise unchanged.

IEEE 802, the LAN/MAN Standards Committee, is one of the standards committees of the IEEE Computer Society. Its working groups each own an area: 802.1 bridging and architecture, 802.3 Ethernet, 802.11 wireless LANs [1]. Inside a working group, task groups focus on one subject, as the TSN task group does for time-sensitive networking [1]. The terms used along the way [1]:

TermMeaning
PAR, Project Authorization RequestThe document that authorises work on a project
CSD, Criteria for Standards DevelopmentThe basis for deciding whether to forward a PAR
WG, Working GroupResponsible for developing the standards of one area
TG, Task Group (or task force)Part of a working group, focused on one subject
TAG, Technical Advisory GroupExperts on a topic that crosses working groups; may write a recommended practice

3. From idea to published standard​

Stages of an IEEE 802.1 standard: new idea, PAR, task group, work group, SA ballots, standard
Figure 3. The stages of an IEEE 802.1 project, as the 802.1DG editor summarised them.Source: D. Pannell, “Status & Content of the IEEE TSN Auto Profile,” IEEE Ethernet & IP @ Automotive Technology Day, September 2020, slide 6; cropped, otherwise unchanged.
The standard development process: PAR, NesCom approval, task group ballot, working group ballot and recirculation, sponsor ballot and recirculation, RevCom approval, publication
Figure 4. The development process in more detail. Each ballot can repeat (the loops i to m) until no new comments remain; recirculation ballots are open only on the changes since the previous round.Source: J. Farkas, “IEEE 802.1 TSN TG Overview,” DetNet–TSN workshop, IEEE 802.1, 11 November 2018, slide 7; cropped, with the slide footer blanked.

The stages, in the words of an 802.1 editor [2]:

  1. Ideas and presentations. Anyone may bring a problem within the scope of 802.1; the proposers must show there is a need and a market.
  2. PAR. Enough 802.1 voters must support it, and the IEEE approves it (through NesCom).
  3. Task group ballots. Requirements are collected and solutions worked out. Anyone can comment and vote.
  4. Working group ballots. The solutions are validated. Anyone can comment and every comment is answered, but only 802.1 voters' votes count.
  5. Standards Association (sponsor) ballots. The last step, checking that all IEEE procedures were followed. Anyone can join the ballot pool.
  6. Approval and publication, after RevCom has reviewed the process.

At each level a first ballot covers the whole document, and recirculations cover only the changes [3]. Technical decisions need agreement of at least 75 %. The process rests on due process, consensus, openness, balance between interested parties, and a right of appeal [3].

4. How amendments merge into editions​

The IEEE 802.1 introduction to newcomers puts it in one sentence: periodically the amendments get merged into a revision of the main standard [1]. 802.1Q shows how this plays out over 25 years.

EditionKey amendments, rolled into the next edition802.1Q-19981998MSTP802.1sProtocolVLANs802.1v+1 corrigendumroll-up802.1Q-20052005Providerbridges802.1adMRP802.1akPBB802.1ahCBSQavSRPQat+6 moreroll-up802.1Q-20112011SPB802.1aqETSQazPFCQbbEVBQbgMAC bridges802.1D-2004+5 moreroll-up802.1Q-20142014TASQbvPreemptionQbuPCRQcaCQFQchPSFPQci+3 moreroll-up802.1Q-20182018TSNconfigurationQccYANGQcpATSQcr+2 moreroll-up802.1Q-2022activeYANG forTSNQcwPBBattachmentQcjCongestionisolationQcz+3 moreroll-upP802.1Qrevision in progressthe next roll-up: it will supersede 802.1Q-2022 and absorb its amendments
Figure 5. The editions of IEEE 802.1Q. For each edition, the key amendments approved against it (keyword above, designation below), which the next edition rolled into its text. The IEEE SA page of each edition, linked below, lists all of them.Source: own drawing from the IEEE SA pages of 802.1Q-1998, 802.1Q-2005, 802.1Q-2011, 802.1Q-2014, 802.1Q-2018, 802.1Q-2022 and P802.1Q, which list every amendment and corrigendum of each edition.

Reading the figure:

  • Each TSN mechanism entered 802.1Q twice. First as an amendment (802.1Qbv-2015, 802.1Qbu-2016, 802.1Qci-2017), then as clauses of the next edition, 802.1Q-2018. A paper citing "802.1Q-2018" for scheduled traffic and one citing "802.1Qbv-2015" mean the same text.
  • A whole standard can be absorbed. 802.1Q-2014 superseded not only 802.1Q-2011 but also 802.1D-2004, the separate standard for MAC bridges, whose content it took over [4].
  • The cycle never stops. 802.1Q-2022 is the active edition. It already has six amendments (2023 to 2025) and three amendment projects, and a revision PAR approved on 5 June 2023 will supersede it [4].

Other base standards follow the same pattern. 802.1AS went from 802.1AS-2011 to 802.1AS-2020, a revision in which the whole document was open, and has since had amendments such as 802.1ASdm (hot standby) and a further revision [2][5]. 802.1CB-2017 was amended by 802.1CBdb-2021 and is being revised [5].

Because 802.1Q gathers so many former amendments, it can be considered many individual standards integrated into a single document. The introduction suggests a reading order [1]:

  • clauses 6 to 9 for the general bridge architecture;
  • the clause titled "Principles of …" for an unfamiliar area;
  • clause 5, Conformance, to find the requirements of a given device.

5. Status and maintenance​

Every approved IEEE standard has a 10-year life cycle [6]:

StatusMeaning
ActiveBeing maintained
SupersededReplaced by a revised edition, or by a compilation of the standard with all its amendments, corrigenda and errata
Inactive-reservedRemoved from active status because no revision was completed within 10 years
Inactive-withdrawnRemoved from active status by a ballot of the balloting group

An active standard must go through a revision at least every 10 years to stay active [6]. Amendments and corrigenda change its content but do not reset that clock: only a revision does [6]. This is one reason why base standards such as 802.1Q are revised regularly even when no single amendment requires it.

6. How standards are grouped​

The word "group" means several things in IEEE 802.1:

  • By working group. The number after "802." names the working group that owns a standard: 802.1 for bridging and architecture, 802.3 for Ethernet [1]. Frame preemption, for example, needed one standard from each: 802.3br and 802.1Qbu.
  • By base standard. A base standard, its amendments and its corrigenda form one family until the next revision merges them. The letters after the base name show the family: 802.1Qcc belongs to 802.1Q, 802.1CBdb to 802.1CB.
  • By role in TSN. The TSN task group sorts its documents into three tiers.
TSN standards grouped into profiles, configuration and base technology
Figure 6. The three tiers of TSN standards and projects: base technology (the tools), configuration (YANG models and configuration protocols), and profiles (selections of tools for one application).Source: J. Farkas, “IEEE 802.1 TSN TG Overview,” DetNet–TSN workshop, IEEE 802.1, 11 November 2018, slide 9; cropped, otherwise unchanged.
  1. Base technology: the tools themselves, for example 802.1AS, 802.1Qbv and 802.1CB.
  2. Configuration: how the tools are set up, for example 802.1Qcc and the YANG models 802.1Qcp and 802.1Qcw.
  3. Profiles: documents that select and constrain the tools for one application, for example 802.1BA, 802.1CM and IEC/IEEE 60802.

A profile may make an optional feature mandatory but may not create new features or protocols. A gap found while writing a profile becomes an amendment to a base standard [2]. In the other direction, mechanisms that change how a bridge forwards frames are written as amendments to 802.1Q, while functions also used outside the bridge, such as time synchronisation (802.1AS) or frame replication (802.1CB), are separate base standards.

Some standards are written jointly with another body and carry both logos. IEC/IEEE 60802 is a joint IEC SC65C/WG18 and IEEE 802 project that produces one dual-logo standard [7].

7. How to cite a standard​

  • Cite with a year for a specific text: "IEEE Std 802.1Q-2022". A designation without a year means the latest edition [1].
  • Cite the amendment for history, the edition for the text: "introduced by 802.1Qbv-2015, now specified in 802.1Q-2022".
  • Check the status first. An IEEE SA page states whether a standard is active, superseded or inactive, and lists its amendments and the edition that superseded it, as used for Figure 5.
  • Free access. IEEE 802 standards become free to download through the IEEE GET Program some months after publication.

References​

  1. J. Farkas, "Introduction to IEEE 802.1: Focus on the Time-Sensitive Networking Task Group," 15 May 2017, slides 10–16. Slides
  2. D. Pannell, "Status & Content of the IEEE TSN Auto Profile," IEEE Ethernet & IP @ Automotive Technology Day, September 2020, slides 4–6 and 9. Slides
  3. J. Farkas, "IEEE 802.1 TSN TG Overview," DetNet–TSN workshop, 11 November 2018, slides 3, 5, 7 and 9. Slides
  4. IEEE SA, pages of IEEE 802.1Q-1998, -2005, -2011, -2014, -2018, -2022 and of the P802.1Q revision project. 802.1Q-2014, 802.1Q-2022, P802.1Q
  5. IEEE 802.1, Time-Sensitive Networking (TSN) Task Group, list of standards and projects. Web page
  6. IEEE SA, "Maintenance of IEEE Standards FAQs." Web page
  7. IEEE 802.1, IEC/IEEE 60802 TSN Profile for Industrial Automation, project page. Web page