%% You should probably cite draft-hu-6man-ipv6-flowlabel-load-balancing-rdma-02 instead of this revision.
@techreport{hu-6man-ipv6-flowlabel-load-balancing-rdma-01,
    number =    {draft-hu-6man-ipv6-flowlabel-load-balancing-rdma-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hu-6man-ipv6-flowlabel-load-balancing-rdma/01/},
    author =    {Jiayuan Hu and Jie Dong and Xia Gong},
    title =     {{A RoCEv2 Flow-Level Load Balancing Method Based on the IPv6 Flow Label}},
    pagetotal = 8,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document proposes a method for achieving flow-level load balancing in RoCEv2 (RDMA over Converged Ethernet version 2) networks. Traditional per-flow load balancing based on the 5-tuple cannot distinguish between different RDMA sessions that share the same 5-tuple. This causes "elephant flows" to be hashed to the same path, leading to network congestion. This method resolves this issue by parsing the QP (Queue Pair) information from the IB BTH (Base Transport Header) and IB DETH (Datagram Extended Transport Header) headers of the RoCEv2 packet. By combining this with portions of the IPv6 source and destination addresses as an entropy source, a CRC32 hash algorithm generates a 20-bit value, which is then written into the Flow Label field of the IPv6 header. Network devices can subsequently use the updated "5-tuple + Flow Label" for more granular flow-level load balancing, thereby effectively improving transmission efficiency in high-performance networks such as AI computing.},
}