This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| IEEE 802.3cd | |
|---|---|
| Title | IEEE 802.3cd |
| Status | Published |
| Organization | Institute of Electrical and Electronics Engineers |
| Committee | IEEE 802.3 |
| First published | 2018 |
| Scope | Ethernet physical layer and MAC amendments |
IEEE 802.3cd IEEE 802.3cd is an amendment to Ethernet standards that defines new physical layer speeds and media for high-performance networking, developed by the Institute of Electrical and Electronics Engineers and ratified by the IEEE 802.3 Working Group. The amendment extends Ethernet technology used in data centers, carrier networks, and campus backbones and interacts with related standards from the International Telecommunication Union and the Ethernet Alliance.
IEEE 802.3cd was created within the IEEE 802.3 Working Group alongside related efforts such as IEEE 802.3bs and IEEE 802.3by to provide higher lane rates and multi-lane aggregations for Ethernet, addressing demands from hyperscale operators like Amazon and Google as well as carriers like AT&T and Verizon. The project involved stakeholders including the Ethernet Alliance, the Optical Internetworking Forum, and standards bodies such as the International Telecommunication Union Telecommunication Standardization Sector and the European Telecommunications Standards Institute. The amendment targets physical layer speeds including 50 Gbit/s and 100 Gbit/s per lane and multi-lane solutions used by vendors such as Cisco, Juniper Networks, Arista Networks, Broadcom, Intel, and Mellanox (now part of NVIDIA).
The specification introduces new single-lane and multi-lane physical coding schemes and defines clauses interoperable with existing Ethernet clauses originally specified in IEEE 802.3 and updated in amendments like IEEE 802.3ba and IEEE 802.3bs. It prescribes 50 Gigabit Ethernet variants and 100 Gigabit Ethernet lane rates employing 64b/66b and RS-FEC mechanisms similar to those used in standards from the International Electrotechnical Commission and ITU-T recommendations. The amendment defines link training, clause alignments, and FEC parameters compatible with products from manufacturers such as Finisar (now II-VI), Lumentum, and Sumitomo Electric and interoperable with deployments by operators like Microsoft and Facebook (Meta).
IEEE 802.3cd specifies support for optical modules conforming to MSA formats and demographics influenced by Multi-Source Agreements such as those for QSFP and SFP form factors, aligning with ecosystems driven by companies like Cisco Systems, Hewlett Packard Enterprise, and Dell Technologies. The amendment includes fiber modalities—single-mode fiber and multimode fiber—addressed by fibre standards from Corning, Prysmian, and OFS and coordinated with optical interface efforts from the Optical Internetworking Forum and the Small Form Factor Committee. It also contemplates copper backplane and twinax cable assemblies used in data center topologies deployed by Equinix, Digital Realty, and Google Cloud Platform.
Framing and MAC-layer enhancements retain compatibility with canonical Ethernet frame formats defined by the IEEE 802.3 standard and extend Physical Coding Sublayer (PCS) elements to accommodate higher symbol rates and lane aggregation patterns seen in earlier projects such as IEEE 802.3by and IEEE 802.3bs. The amendment refines auto-negotiation, link training, and alignment marker schemes interoperating with management frameworks like Simple Network Management Protocol implementations used by Juniper Networks and Huawei Technologies. PCS updates enable interoperability with silicon PHY implementations from Broadcom, Marvell, and Xilinx (now part of AMD), facilitating coherent integration into switches and NICs by vendors including Arista Networks and Mellanox/NVIDIA.
Performance targets in the amendment emphasize low-latency forwarding and deterministic timing suited for data center fabrics operated by hyperscalers such as Amazon Web Services and Alibaba Cloud as well as telecom operators following 3GPP timelines for 5G transport. The specification includes Forward Error Correction schemes similar to those in OTN standards and aligns timing with Precision Time Protocol deployments advocated by companies like Cisco and Spirent Communications for synchronization-sensitive applications. Throughput and latency objectives were vetted against test suites used by interoperability events run by the Ethernet Alliance and plugfest activities hosted by the Optical Internetworking Forum.
The IEEE 802.3cd project evolved through Study Group and Task Force phases inside IEEE 802.3 and progressed with contributions from vendors such as Broadcom, Intel, Cisco, and Nokia. Formal ballot and approval steps involved IEEE standards processes similar to those seen for IEEE 802.11 and ITU-T Study Groups, culminating in publication following meetings held at IEEE 802 plenaries in locations visited by delegates from organizations like the IETF and the International Organization for Standardization. The amendment’s timeline intersected with carrier and hyperscaler deployment roadmaps and with collaborative standards efforts including those from MEF and the Open Compute Project.
Adoption of the amendment accelerated port shipments and module availability from transceiver vendors and silicon vendors supplying cloud providers and network operators such as Facebook (Meta), Google, Microsoft, and AT&T, influencing switch ASIC roadmaps at companies like Broadcom and merchant silicon strategies at Marvell. The standard catalyzed ecosystem activity among optical component manufacturers including Fujitsu, NEC, and Corning and spurred interoperability events coordinated by the Ethernet Alliance and the Optical Internetworking Forum, affecting procurement by data center operators such as Equinix and Digital Realty and service providers including Verizon and Deutsche Telekom. Category:IEEE 802.3