For two decades, the optical transport layer was a separate domain — managed by a dedicated team, running on dedicated hardware, with OTN framing providing sub-50ms protection and per-wavelength performance monitoring. Then OpenZR+ pluggable coherent optics arrived, and the router port became the optical endpoint. The question every network architect now faces: keep the OTN layer, or collapse it into IP-over-DWDM? The answer depends on what you are protecting and who operates it.

What Each Architecture Does

OTN (Optical Transport Network). A dedicated transport layer that wraps client signals (Ethernet, Fibre Channel, SDH) into standardized OTN frames. OTN provides per-wavelength performance monitoring, forward error correction, and sub-50ms protection switching at the optical layer. It runs on dedicated transponder/muxponder hardware — separate from routers and switches.

IP-over-DWDM (IPoDWDM). The router's coherent pluggable transceiver connects directly to the DWDM line system. There is no intermediate OTN layer — the router port is the optical endpoint. Protection and monitoring move to Layer 3 (IP/MPLS). This architecture eliminates an entire hardware layer but gives up OTN's per-wavelength OAM and sub-50ms optical protection.

Side-by-Side Comparison

When OTN Still Wins

Three conditions where OTN is the right architecture:

Carrier SLA with sub-50ms protection. OTN's sub-50ms protection switching is mandatory for carrier-grade services. Layer 3 FRR typically converges in 50–200ms — good enough for most enterprise and cloud traffic, but not for financial services or mobile backhaul SLAs that require guaranteed sub-50ms failover.

Multi-service aggregation. OTN transports Ethernet, Fibre Channel, and legacy SONET/SDH on the same wavelength using standardized mapping. IPoDWDM carries only IP/Ethernet. If your optical network carries non-IP services, OTN is required — there is no Layer 3 equivalent for Fibre Channel transport.

Subsea and ultra-long-haul. Subsea cable systems require OTN for FEC interworking between landing stations and per-section performance monitoring across multiple wet plant segments. Coherent pluggables with oFEC can handle the optical reach, but the operational visibility that OTN OAM provides is non-negotiable for subsea operators.

When IPoDWDM Is the Clear Winner

Greenfield cloud and data center DCI. If every service is IP/Ethernet and the operations team owns the routers from end to end, IPoDWDM eliminates an entire hardware class. The cost, power, and space savings are typically 50–70% versus OTN-based transport.

Simplified operations at scale. One team, one platform, one set of tooling. No transport engineering team maintaining a separate OTN network with separate management, separate sparing, and separate training. This operational argument drives most IPoDWDM adoption in cloud and colocation environments.

Decision heuristic: If protection must be sub-50ms at the optical layer, or you carry non-IP services, keep OTN. If all services are IP and the operations team owns the routers end-to-end, IPoDWDM eliminates cost, power, and complexity with no functional loss. The architectural decision is not about technology capability — it is about SLA requirements and operational structure.

APEX Group supplies both architectures — 400G CFP2-DCO and 800G QSFP-DD ZR+ coherent transceivers for IPoDWDM in cloud and enterprise DCI, plus DWDM MUX/DEMUX and EDFA amplification for any line system. Whether you run OTN, IPoDWDM, or a hybrid of both, the optical components come from a single procurement partner.

APEX GROUP — www.apexallinone.com