 |
1.1 |
1 |
(% class="row" %) |
|
|
2 |
((( |
|
|
3 |
(% class="col-xs-12 col-sm-8 test-report-content" %) |
|
|
4 |
((( |
|
|
5 |
---- |
|
|
6 |
|
|
|
7 |
The Ultra Ethernet Consortium (UEC) was founded with the mission to deliver an Ethernet-based, open, interoperable, high-performance, full communications stack architecture capable of meeting the rapidly growing network demands of AI and HPC at scale. UEC brings together more than 50 leading software, hardware, and solution providers, alongside strategic alliances such as the Open Compute Project (OCP), Storage Networking Industry Association (SNIA), OpenFabrics Alliance (OFA), and the IEEE 802.3 working group. In 2025, 4 UEC working groups collaborated to release the UEC Tech Spec 1.0. |
|
|
8 |
The technical specification introduced 5 layers in Ultra Ethernet (UE): software, transport, network, link, and physical layer. Notably, the link and physical layers require next-generation chipsets, while the software and transport layers depend on UE server deployments and support from real NIC vendors. However, due to the limited time before our event, we were unable to fully implement all layers. As a result, Arista and Keysight provided UEC-capable devices so we could demonstrate UEC's packet-trimming feature at the network layer. It is important to note that this was not a comprehensive interoperability test. For instance, Keysight IxNetwork could generate UEC traffic but could not interact with trimmed packets. Regarding packet trimming, this network-layer feature is designed for congestion control. In short, packet trimming is a mechanism in which switches trim packet payloads and use a different traffic class to forward the resulting headers to the destination. The upper-layer protocol then uses the trimmed packet information to ensure fast retransmission of lost packets. |
|
|
9 |
First, we ensured that the interface was not overloaded. Under these conditions, all packet sizes remained at 1000 bytes, and traffic class values stayed at 0. |
|
|
10 |
Next, we intentionally overloaded the interface to simulate network congestion. As a result, we observed that the packet size was trimmed to 206 bytes and the traffic class value was changed to 24. |
|
|
11 |
|
