Access Official Technical PDF

Share Summary:LinkedInEmail

Ethernet standards development shapes the networking technologies that industrial organizations specify, integrate and maintain. The IEEE 802.3 Working Group is one of the bodies responsible for this work: its charter is to maintain and revise the Ethernet standard, develop new Ethernet standards in a reasonable time frame, forward standards to ISO/IEC JTC1 SC6, and coordinate with other relevant groups. For automation engineers and technical decision-makers, understanding that mandate helps clarify how Ethernet standards are maintained and where industry stakeholders participate.

What the IEEE 802.3 Working Group does

The group’s responsibilities cover both ongoing maintenance and the creation of new standards. Maintaining and revising a standard is distinct from developing new work: one concerns the continuing stewardship of existing specifications, while the other addresses additional standards as the group’s work progresses. The charter also calls for forwarding standards to ISO/IEC JTC1 SC6 and maintaining liaisons with other parts of the IEEE 802 LAN/MAN Standards Committee and relevant standards development organizations.

This remit places IEEE 802.3 within a wider standards landscape. Its work is not described as an isolated activity; liaison and formal forwarding are explicit parts of the charter. For organizations that build or operate networked systems, that context matters when tracking standards work and considering how Ethernet specifications relate to broader standards coordination.

A cross-industry membership

A membership roster dated January 5, 2018, lists 216 participants and their affiliations. The names span a broad range of organizations, including semiconductor and networking companies, equipment and component suppliers, communications providers, test and measurement organizations, universities, industrial automation companies and end users in sectors such as automotive.

Examples in the roster include Rockwell Automation, Emerson Automation Solutions, Siemens, Pepperl+Fuchs, Endress + Hauser, Johnson Controls and Audi, alongside companies involved in networking, connectivity, testing, computing and communications. The roster also includes the University of New Hampshire InterOperability Laboratory. These affiliations illustrate the range of perspectives represented in the group; they do not, by themselves, establish the position or influence of any individual organization.

For industrial automation, this diversity is relevant because Ethernet is used across a technology ecosystem that includes network equipment, cabling and connectivity, semiconductors, testing, and industrial systems. A standards group with participants from multiple parts of that ecosystem can bring different technical and application perspectives into standards work. The roster is a snapshot, however, and should be read as a record of membership at that date—not as a current membership list or a summary of the group’s decisions.

Why standards work matters to automation teams

Industrial networking decisions have practical consequences for system design, equipment selection and long-term support. Standards provide a common technical framework for products and systems to be developed against. The IEEE 802.3 charter shows how that framework is stewarded: through maintenance and revision, development of new standards, and coordination with other standards bodies.

Automation professionals can use this context to make their standards engagement more focused. When evaluating a network technology or planning a migration, teams should distinguish between:

  • Published standards: the specifications available for implementation and reference.
  • Standards development: ongoing work to revise existing standards or develop new ones.
  • Industry participation: the organizations and individuals involved in the working group at a particular point in time.

Keeping these categories separate helps avoid treating a membership list as evidence of a technical requirement or product capability. It also helps teams frame questions for suppliers and integrators: which standard or revision is relevant, whether a specification has been completed, and how the equipment being considered aligns with the applicable standard.

Following Ethernet standards development

The working group’s stated responsibilities offer a useful guide for following its work. First, identify whether a topic concerns maintenance of an existing Ethernet standard or development of a new one. Next, consider the group’s coordination responsibilities, including liaison with other IEEE 802 groups and relevant standards development organizations. Finally, check the date and status of any membership information being used. A roster from 2018 can describe participation at that time, but it cannot confirm who is involved today or the current status of a standards project.

For plant managers, operations leaders and system integrators, this disciplined approach supports better technical conversations. It keeps planning grounded in published specifications and verified project status rather than assumptions drawn from organizational names or an old roster.

Conclusion

IEEE 802.3’s mandate encompasses maintaining and revising Ethernet standards, developing new standards, forwarding them to ISO/IEC JTC1 SC6 and coordinating with related organizations. Its 2018 membership roster illustrates broad participation across technology suppliers, industrial automation, communications, testing and other sectors. For automation teams, the practical lesson is to track standards work by its documented scope and status, and to treat membership records as dated context—not as a substitute for the standards themselves.

Access Official Technical PDF

About The Author