@azonenberg @gsuberland @karotte ( … and that's before...

@azonenberg @gsuberland @karotte ( … and that's before you learn about the fact that in long-haul connections, you need to put in as much power as you can to get good OSNR at the output, but not as much that your mutual information per symbol drops due to phase smear due to fiber medium nonlinearity at high E-field strengths, but still want to do wavelength multiplex with only small guard bands between the carriers, but of course wavelengths' powers will mutually cause nonlin./phase distortion)

Like 19 January at 2:05 | Wall-to-wall | Open on mastodon.social

3 comments

Andrew Zonenberg

@funkylab @gsuberland @karotte Oh I bet fiber gets cursed when you go fast enough.

But at 10/25G its easy.

19 January at 2:23 | Open on ioc.exchange

Darrell Harmon

@azonenberg @funkylab @gsuberland @karotte I'd argue the FEC layer in 25GBASE-R is cursed due to all the transcoding and gearboxes to convert 80 64b66b codewords to one 5140b block to append the 140b parity resulting in the same 5280 bits. It's not pretty.

25GBASE-CR-S is nice and pure like 10GBASE-R but the FEC layer is required in everything else 25GBASE-R.

The FEC itself isn't cursed just the wrapper around it.

19 January at 2:29 | Open on chaos.social

roukemap

@dlharmon @azonenberg @funkylab @gsuberland @karotte
Unfortunately people can and do try to run 25G without FEC in the wild (and not short range twinax) . And then there is the firecode vs rsfec question if you do run FEC. The whole history of the 25G consortium, followed by IEEE standardization also adds another layer of cursedness.

19 January at 5:21 | Open on social.treehouse.systems