UEC 1.0 · Packet spray · UET

Ultra Ethernet: UEC 1.0 for AI Fabrics

Ultra Ethernet is the open, multi-vendor path to InfiniBand-class AI networking on standard Ethernet. The UEC 1.0 specification, released in June 2025, defines the Ultra Ethernet Transport (UET) with packet spraying, multi-path RDMA, out-of-order delivery, selective retransmission, and both sender- and receiver-based congestion control. It does not require a lossless PFC fabric. IP Infusion is a member of the Ultra Ethernet Consortium, and OcNOS-DC runs lossless RoCEv2 AI fabrics with DLB in production today.

June 2025UEC 1.0 specification
RoCEv2OcNOS-DC lossless fabric today
up to 800GOcNOS-DC on Tomahawk 5
600+operator networks on OcNOS
How UET moves a message

Packet spray across every path

A single RDMA message between two GPUs is sprayed packet-by-packet across all four spine paths at once. The fabric tolerates out-of-order arrival and the destination UEC NIC reassembles in order. No flow-pinning, no hash collisions, no idle uplinks.

Ultra Ethernet packet spray across a 4-spine fabric Two GPUs connected through two leaves and four spines. A single RDMA message is split into four packets and sent across all four spine paths simultaneously. At the receiving NIC, packets arrive out of order and are reassembled in order before delivery to the GPU. Bottom band lists UEC properties: packet spray, multi-path RDMA, out-of-order delivery, NIC reassembly. P1 P2 P3 P4 Spine-1UEC fabric Spine-2UEC fabric Spine-3UEC fabric Spine-4UEC fabric Leaf-1Ethernet Leaf-2Ethernet GPU-AUEC NIC GPU-Breassembly UEC 1.0 · PACKET SPRAY · MULTI-PATH RDMA · OUT-OF-ORDER DELIVERY · NIC REASSEMBLY
Inside the transport

What the Ultra Ethernet Transport adds

RoCEv2 works, but it inherits older design constraints: one hashed path per flow, network-wide PFC pause, and window-restart loss recovery. The UEC 1.0 specification keeps the standard physical Ethernet you can buy from anyone and replaces the upper layers with a transport (UET) built for 1k to 100k GPU jobs.

Path use

Packet spraying

A single message is sprayed across every available path at once. No flow pinning, no ECMP collisions, so fabric utilisation approaches the theoretical maximum during a collective.

RDMA

Multi-path RDMA

RDMA is carried over many parallel paths rather than one, so a large transfer is no longer capped by the bandwidth of a single hashed link.

Delivery

Out-of-order delivery

The fabric is allowed to reorder. The UEC NIC reassembles in order before delivery, so applications and the GPU never see disorder.

Recovery

Selective retransmission

Lost packets are recovered selectively rather than restarting the RDMA window, collapsing the tail-latency penalty of any in-fabric loss.

Control

Modern congestion control

Both sender- and receiver-based schemes replace coarse PFC pause as the primary tool. UET does not require a lossless PFC fabric; pause becomes a backstop, not the front line.

Ecosystem

Open and multi-vendor

UET runs on standard Ethernet from any vendor. The consortium, whose members span silicon, NIC, switch, and cloud companies, publishes the spec openly.

Where each fits

UEC, RoCEv2, and InfiniBand, axis by axis

RoCEv2 runs most AI fabrics in production today. Ultra Ethernet is the standards-based path forward as UEC-capable NICs ship, and InfiniBand remains the single-vendor specialist. Which axis matters depends on the workload and the timeline.

Axis RoCEv2Ethernet, today Ultra EthernetUET, open multi-vendor InfiniBandsingle-vendor
Path useOne hashed ECMP path per flow; parallel paths can sit idle.Packet spray across every available path in parallel.Adaptive routing built into the spec.
Loss handlingLossless via PFC + ECN + DCQCN; relies on network-wide pause.Tolerates loss and reorder; does not require a lossless PFC fabric.Lossless by credit-based flow control.
ReorderingIn-order delivery only.Out-of-order delivery, reassembled in order at the NIC.In-order delivery.
RetransmissionWindow-based recovery taxes tail latency.Selective retransmission of only the lost packets.Link-level recovery.
Congestion controlDCQCN with ECN marking.Both sender- and receiver-based control at the endpoints.Credit-based at the link.
EcosystemMulti-vendor Ethernet at every layer.Open, multi-vendor; any vendor can build to the UEC 1.0 spec.Effectively single-vendor for NIC and switch silicon.
OcNOS-DC statusProduction today on Tomahawk 4 / Tomahawk 5.IP Infusion is a UEC member; OcNOS-DC runs RoCEv2 in production today.Not applicable; separate fabric and tooling.
OcNOS-DC today

What OcNOS-DC runs in AI fabrics today

OcNOS-DC runs a production lossless RoCEv2 fabric today with PFC, ECN, DCQCN, and sub-millisecond DLB on Broadcom Tomahawk 4 and Tomahawk 5 switches. IP Infusion is a member of the Ultra Ethernet Consortium.

Transport

Lossless RoCEv2

PFC pauses per-priority traffic before buffers overflow, ECN marks packets early, and DCQCN buffer profiles are tuned for RDMA collective traffic.

Path use

Dynamic load balancing

DLB reads live ASIC queue depth and rebinds flowlets to less-loaded paths in under a millisecond, so large flows stop colliding on one uplink.

Hardware

Tomahawk 4 / 5 silicon

Runs on Broadcom Tomahawk 4 (25.6T) and Tomahawk 5 (51.2T) open switches from Edgecore and UfiSpace.

Protection

PFC deadlock watchdog

A per-port, per-priority watchdog detects paused-queue cycles and drains the queue before jobs hang.

Telemetry

Streaming telemetry

PFC pauses, ECN marking, DCQCN thresholds, and buffer depths stream over gNMI with OpenConfig YANG for tuning during cluster bring-up.

Open hardware

Vendor-neutral path

Pairing OcNOS-DC with open hardware keeps the NIC, GPU, and switch choices with the cluster owner, so no single vendor owns the AI fabric.

The migration picture

Build on RoCEv2 now, plan for UEC as NICs ship

Real fabrics do not switch overnight. RoCEv2 carries production AI training today, and UEC-capable NICs bring a multipath transport to standard Ethernet as they ship.

  • RoCEv2 today. Production-grade for clusters built right now. OcNOS-DC ships pre-tuned RoCEv2 on Tomahawk 4 / Tomahawk 5. Most fabrics in production in 2026 are RoCEv2.
  • UEC as NICs ship. UEC-capable NICs bring packet spray and selective retransmission to scale-out clusters. Cluster owners pick the NIC vendor.
  • InfiniBand stays specialist. Single-vendor performance with separate cabling, management, and ecosystem. UEC brings comparable transport techniques to standards-based, multi-vendor Ethernet.
The IP Infusion view

Open Ethernet for AI fabrics, on OcNOS-DC today

Ultra Ethernet brings multipath transport techniques to standard, multi-vendor Ethernet. IP Infusion is a member of the Ultra Ethernet Consortium, and OcNOS-DC runs lossless RoCEv2 with DLB in production today.

A consortium member

IP Infusion is a member of the Ultra Ethernet Consortium, which publishes the Ultra Ethernet specification openly.

Production RoCEv2 now

OcNOS-DC delivers lossless RoCEv2 with PFC, ECN, and sub-millisecond DLB today on validated open hardware from vendors such as Edgecore and UfiSpace.

Your choice of NIC

OcNOS-DC runs on open Broadcom Tomahawk 4 and Tomahawk 5 hardware and leaves the NIC and GPU choice with the cluster owner.

Ultra Ethernet, answered

What is Ultra Ethernet (UEC)?
Ultra Ethernet is an open standard from the Ultra Ethernet Consortium (UEC) that adapts Ethernet for AI and HPC workloads. The UEC 1.0 specification, released in June 2025, defines the Ultra Ethernet Transport (UET): endpoint packet spray across every path, multi-path RDMA, out-of-order delivery with reassembly at the NIC, selective retransmission, and both sender- and receiver-based congestion control, so large training and inference jobs stop being limited by single-path hashing and network-wide pause.
Is IP Infusion a member of the Ultra Ethernet Consortium?
Yes. IP Infusion is a member of the Ultra Ethernet Consortium (UEC), the industry group that develops and publishes the open Ultra Ethernet specification for AI and HPC networking.
How is Ultra Ethernet different from RoCEv2?
RoCEv2 pins each flow to one ECMP path and depends on network-wide PFC to stay lossless. Ultra Ethernet sprays a single message across every available path in parallel, reassembles it in order at the destination NIC, retransmits only the lost packets, and controls congestion at both the sender and the receiver. UET does not require a lossless PFC fabric, which reduces the reliance on PFC pause and lowers tail latency on large collectives.
Does OcNOS support Ultra Ethernet today?
OcNOS-DC runs a production lossless RoCEv2 fabric today with PFC, ECN, DCQCN, and sub-millisecond DLB on Broadcom Tomahawk 4 and Tomahawk 5 switches. The Ultra Ethernet transport runs on UEC-capable NICs, and IP Infusion is a member of the Ultra Ethernet Consortium. To plan how UEC fits a specific build, talk to an IP Infusion engineer.
Do I need new hardware for Ultra Ethernet?
Ultra Ethernet endpoint behavior (packet spray, reassembly, selective retransmission) runs on UEC-capable NICs. The UEC 1.0 specification also covers link and switch behavior, so the fabric requirements for a UEC deployment depend on the NIC, the switch silicon, and the NOS release. Size the fabric with an IP Infusion engineer against your NIC choice.
What are packet spray and out-of-order delivery?
Packet spray sends the packets of one message across all parallel fabric paths at once instead of down a single hashed path, so no link becomes a hot spot during a collective. Because packets can then arrive out of order, the destination NIC reassembles them into the original sequence. Together they keep every path busy and shorten the slowest transfer in a job.

Planning an AI fabric? Let's design it together

Tell us the workload and the GPU scale, and an IP Infusion engineer will size the leaf-spine fabric with you, or start a first-pass layout in the AI Fabric Design Suite.