
Take a copper lane from 100 Gb/s to 200 Gb/s and the Nyquist frequency nearly doubles, to 53.125 GHz in IEEE P802.3dj. Yet the loss budget grew. The task force allows 40 dB from die to die, while OIF's 2022 framework lists 28 dB at 28 GHz for CEI-112G long reach. Package, board, connector and receiver all have to share that bigger number at a far harsher frequency.
This post follows one end of the budget, from the die bump to the connector, where the adopted symmetrical case allows 11.5 dB per host. It then prices the ways out. In a worked 7 inch route, a cabled host recovers about 4.4 dB with no extra SerDes, while a retimer on one 8-lane port adds about 17 W under our illustrative 5 pJ/b. Each input is either sourced or marked illustrative, so you can redo the sums.
Key takeaways
- "224G" is shorthand. P802.3dj signals at 106.25 GBd PAM4, which is 212.5 Gb/s on the lane and a unit interval of about 9.41 ps.
- The adopted symmetrical copper cable budget is 11.5 + 17 + 11.5 = 40 dB. The package takes about 5 dB of each 11.5 dB host in the task force's example.
- Board trace costs about 1.4 dB per inch when hot. Twinax in the same example costs about 0.32 dB per inch, which is why cabled hosts matter.
- Published 224G silicon quotes analogue energy, not the whole link. Treat 3 pJ/b as a floor when you size a switch.
- A retimer doubles the transceivers on a lane. Buy decibels from the channel first where you can.
Where the 40 dB came from
The number was a negotiated one. The May 2023 proposal to the IEEE task force (Mellitz et al.) reported SerDes builders asking for 36 to 37 dB and system builders for 42 to 45 dB, and it called 40 dB a compromise. Its COM (channel operating margin) runs reached the 3 dB pass threshold on channels of that loss. The task force adopted 40 dB at 53.125 GHz for backplanes that month, then for copper cable that July.
A later motion split the budget. For the symmetrical cable link, each host gets 11.5 dB and the cable assembly gets 17 dB. Two asymmetrical cases followed, because real hosts are not alike: a 16.5 dB host facing a 6.5 dB host leaves 17 dB for the cable, and an 11.5 dB host facing a 6.5 dB host leaves 22 dB. Each case sums to 40 dB, and the host figures include allowances for the BGA and connector footprint vias.
One caution on status. P802.3dj was still in Standards Association balloting at draft 3.3, with final comment responses dated 14 October 2026, and the IEEE 802.3 ballot page showed no open ballots on 6 November 2026. We did not read the draft itself, and the budget figures here come from task force motions and contributions of 2023 and 2024. Check them against the published clauses. OIF told IEEE in April 2026 that CEI-224G-LR and MR had reached revision 12, with access restricted to IEEE 802.3 participants, so we use no numbers from those documents.
From bump to connector
The clearest public breakdown is in the November 2023 contribution by Tracy et al. These are example allocations for the cable case, not normative limits, and backplanes share the 40 dB without this split. The totals are the budgets. The splits are one way to meet them.
| Segment at 53.125 GHz | Low host, PCB | Nominal host, PCB | Nominal host, cabled | High host, PCB | High host, cabled |
|---|---|---|---|---|---|
| Package | 3.9 dB | 5 dB | 5 dB | 9 dB | 9 dB |
| BGA transition | 0.5 dB | 0.5 dB | 0.5 dB | 0.5 dB | 0.5 dB |
| PCB trace | 2.1 dB (1.5 in) | 6 dB (4.28 in) | 2.8 dB (2 in) | 7 dB (5 in) | 2.8 dB (2 in) |
| Near-package connector | none | none | 1 dB | none | 1 dB |
| Internal twinax | none | none | 2.2 dB (6.8 in, 30 AWG) | none | 3.2 dB (8 in, 32 AWG) |
| Host total | 6.5 dB | 11.5 dB | 11.5 dB | 16.5 dB | 16.5 dB |
| Routed distance after the BGA | 1.5 in | 4.28 in | 8.8 in | 5 in | 10 in |
Three things stand out once you divide the columns through.
The trace rate is a hot number. Each PCB entry works out at about 1.4 dB per inch. That matches the August 2023 channel models by Weaver and Chan of Arista, which give about 1.25 dB per inch at room temperature and about 1.40 dB per inch hot, on conventional construction with no skip layers or microvias. Their 9 inch channel loses 1.28 dB more at 80 °C than at 25 °C (15.73 dB against 14.45 dB, with one vendor's connector). Sign off a budget at the hot corner, or that margin is imaginary. Those same models imply about 3.1 dB of fixed loss for the BGA, vias, connector and module trace: 7.32 dB at 3 inches, less 3 × 1.40 dB.
The package varies more than the board does. The task force adopted two reference packages: Class A, optimised for loss, and Class B, for high radix. Feeding their published transmission line parameters into the Annex 93A loss formula gives our own estimate of trace loss alone at 53.125 GHz:
| Reference package | Loss per mm (our calculation) | Modelled trace lengths | Trace loss |
|---|---|---|---|
| Class A | 0.153 dB | 12 mm, 33 mm | 1.84 dB, 5.05 dB |
| Class B | 0.184 dB | 8, 24, 30, 45 mm | 1.47, 4.41, 5.52, 8.28 dB |
As a check on the method, the same formula applied to OIF's board parameters returns 1.30 dB per inch at 56 GHz, the figure OIF quotes. The results also land close to the 5 dB and 9 dB examples above, once vias and pads are added. The practical message is that shortest and longest lanes in one large package can differ by several decibels, so a single "package loss" entry hides your worst port.
Twinax changes the trade. The 30 AWG example is 2.2 dB over 6.8 inches, about 0.32 dB per inch, more than four times better than the hot PCB rate. For the same 6 dB of host routing, the cabled option covers 8.8 inches and the PCB covers 4.28 inches. OIF's framework goes further and raises cables that terminate on the package itself, skipping the host-to-package transition.
A worked budget: 7 inches to the connector
Suppose a switch has a lane that must travel 7 inches from the package ball to the I/O connector, and the far end is a nominal 11.5 dB host. The route and the choice of scenario are illustrative. The unit rates come from the sources above: 5 dB package, 0.5 dB BGA, 1.4 dB per inch of PCB, 1 dB near-package connector and 2.2 dB per 6.8 inches of 30 AWG twinax.
| Line | All PCB | 2 in PCB + 5 in twinax |
|---|---|---|
| Package and BGA | 5.5 dB | 5.5 dB |
| PCB trace | 7 × 1.4 = 9.8 dB | 2 × 1.4 = 2.8 dB |
| Near-package connector | none | 1 dB |
| Twinax | none | 5 × 0.3235 = 1.6 dB |
| Bump to connector | 15.3 dB | 10.9 dB |
| Against the 11.5 dB nominal host | 3.8 dB over | 0.6 dB under |
| Left for cable and its 2 connectors (40 less this host, less 11.5) | 13.2 dB | 17.6 dB |
The cabled route recovers 4.4 dB. The all-PCB route still fits inside a 16.5 dB high host, with 1.2 dB to spare, but the far end must then be gentle or the external cable short. That is the point of the asymmetrical budget: a loss-heavy port is allowed, provided something else gives way.
What the receiver does with what is left
Insertion loss is the easy part to add up. OIF's framework warns that 112G work exposed the effect of return loss in low-loss channels, and that 224G metrics must weigh more than insertion loss. It also shows how a 4 ps intrapair skew distorts a 9 ps pulse. This is why COM, not a dB figure, decides whether a channel passes. Use the dB budget to plan and COM to judge.
The feasibility work suggests how much receiver is implied. The 2023 COM sets (explicitly not a parameter proposal) used a transmit FFE with 4 pre-cursor and 1 post-cursor taps, a receive FFE spanning 6 pre-cursor and either 24 or 60 post-cursor positions, one DFE tap equivalent, and MLSE (sequence detection). That sort of structure is hard to build without digitising first, which is why the long-reach receiver went digital. If you need the basics, here is a comparison of analogue and DSP SerDes design.
Error targets are the other lever. In March 2024 the task force set a detector error ratio (DER0) of 2e-4 for backplane and copper cable links. Comment files on draft 3.3 cite a maximum PMD link BER of 2.761e-4. OIF notes that relaxing a target from 1e-6 to 1e-4 improves SNR margin by 2.19 dB. That is margin at the slicer, not 2.19 dB of channel, and the price is paid in FEC and latency elsewhere.
Published silicon shows the state of the art, with the usual caveat that these are authors' own results on their own test chips:
- Synopsys, ISSCC 2024 (Pfaff et al.). A 7-bit DAC transmitter and a 7-bit ADC receiver in 3 nm, with up to 20 dB of front-end peaking and 4.0 bits ENOB at 50 GHz. The press kit gives a pre-FEC BER of 5e-7 over a 35 dB bump-to-bump channel at 3 pJ/b analogue. The paper's title in the programme and in JSSC states 40 dB, and a 2025 invited CICC paper is titled 42 dB post-FEC error free. These numbers are not interchangeable, so read each one's own conditions.
- Intel, ISSCC 2024 (Cusmai et al.). A transmitter alone: 7-bit DAC, 9-tap FFE, 1 Vppd, 36.0 dB SNDR and 0.92 pJ/b analogue, with PAM-4 and PAM-6 modes.
- ISSCC 2025 paper 7.2 (Mostafa et al.). Titled 2.2 pJ/b at 212.5 Gb/s with more than 46 dB reach in 5 nm. We read only the title record, not the paper.
Do not rank these on a single axis. Node, BER, reach and what counts as "analogue" all differ.
The power side of the budget
Here is a simple model for sizing. The 3 pJ/b is the published analogue claim, assumed to hold at 212.5 Gb/s. "Analogue" suggests that DSP and FEC sit outside that figure, so the second column adds a digital allowance of 2 pJ/b. That 2 pJ/b is illustrative, as are the port and switch scenarios. Substitute your IP vendor's number.
| Line | 3 pJ/b (analogue only) | 5 pJ/b (illustrative total) |
|---|---|---|
| One transceiver lane at 212.5 Gb/s | 0.6375 W | 1.0625 W |
| 8-lane port, one end | 5.1 W | 8.5 W |
| 8-lane link, both ends, no retimer | 10.2 W | 17 W |
| Same link with one retimer per lane | 20.4 W | 34 W |
| Added per port by the retimer | 10.2 W | 17 W |
| 512-lane switch, SerDes only | 326.4 W | 544 W |
| Retimers on 16 of its 64 ports | 163.2 W | 272 W |
The retimer lines follow OIF's point that removing a repeater halves the SerDes on a switch port, from four to two. We assumed a retimer lane burns the same energy as a host lane, and a retimer built for a shorter reach could do better. Even so, the comparison is stark. The 4.4 dB in the worked budget came from routing, with no new SerDes. A retimer removes the budget problem outright, but it adds latency and may not fit the power envelope, a concern OIF raises directly.
The same logic explains near-package and co-packaged optics: a shorter electrical channel means less equalisation and no repeater. OIF expects a mix of approaches rather than one winner. For the system side of that argument, see where the bottleneck moves once copper runs short.
Five checks before you freeze the floorplan
- Have you budgeted the worst lane? Use the longest package trace and the furthest connector, not an average.
- Is the board rate from your stack-up, at temperature? A 0.15 dB per inch gap between room and hot is 1.05 dB over 7 inches.
- Which far end did you assume? A high-loss host only works if the partner host and the cable leave room for it.
- Did you run COM with real connector and via models? A channel that meets its dB line can still fail on reflections or crosstalk.
- Did you quote total energy? Ask for analogue, DSP and FEC separately, at your BER and your loss.
Our SoC lifecycle on The Semiconductor Hub shows where package, board and IP decisions fall in a programme.
FAQ
Does the 40 dB apply to chip-to-module links?
No. The objective covers backplane and copper cable PHYs. Chip-to-module has its own channels and error allocation. A November 2023 fixture study (Kocsis and Sekel) gives a sense of scale, with a short channel model of 10.32 dB and a mated test fixture of 9.31 dB, of which 2.00 dB is the simulated module connector.
Why not lower the baud rate with PAM6?
OIF's table shows PAM6 at 224 Gbps runs at 90 GBd, with a 45 GHz fundamental instead of 56.25 GHz, at a 3.62 dB SNR penalty. That is a real option in research, and Intel's transmitter supports it, but the task force adopted PAM4 in May 2023, and the KR baseline runs at 106.25 GBd.
Sources
- IEEE P802.3dj Task Force, Key Motions, as of 14 March 2024.
- Mellitz et al., "200 Gb/s per lane KR Backplane Objective Proposal", May 2023.
- DiMinico, "802.3dj - CR Considerations for Insertion Loss Budget Baseline", September 2023.
- Tracy et al., "A Baseline Proposal To Enable More Flexible Architectures and Longer Reach 200Gb/Lane Passive Copper Cables", November 2023.
- Li et al., "IEEE P802.3dj Reference Package Model and Parameters", November 2023, and "200G/Lane KR Baseline for 802.3dj", March 2024.
- Weaver and Chan, "212Gb/s Per Lane PAM4 Chip-to-Module Conventional Channels: Room vs. Hi Temp", August 2023.
- Kocsis and Sekel, "Considerations of Technical Feasibility for Mated Compliance Fixtures", November 2023.
- IEEE P802.3dj Chief Editor's Report, September 2026; D3.3 ballot comments, final responses, 14 October 2026; IEEE 802.3 ballot announcements page, updated 6 November 2026.
- OIF, "Next Generation CEI-224G Framework", OIF-FD-CEI-224G-01.0, February 2022, and liaison letter to IEEE 802.3, 1 April 2026.
- ISSCC 2024 Advance Program and Press Kit, session 7, 2024.
- Pfaff et al., "A 224 Gb/s 3 pJ/bit 40 dB Insertion Loss Transceiver in 3-nm FinFET CMOS", IEEE JSSC vol. 60, January 2025 (bibliographic record), and CICC 2025 invited paper (bibliographic record).
- Mostafa et al., "A 2.2pJ/b 212.5Gb/s PAM-4 Transceiver with >46dB Reach in 5nm FinFET", ISSCC, February 2025 (bibliographic record).
The worked budget and power model use illustrative scenarios and an illustrative digital allowance, as marked. Loss allocations are task force examples rather than limits, and the package loss per mm is our own calculation. Vendor and paper figures are the authors' own claims, as published on the dates shown.


Your comments will be moderated before it appears here.