%% You should probably cite draft-wh-rtgwg-adaptive-routing-arn-04 instead of this revision. @techreport{wh-rtgwg-adaptive-routing-arn-03, number = {draft-wh-rtgwg-adaptive-routing-arn-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-wh-rtgwg-adaptive-routing-arn/03/}, author = {Haibo Wang and Hongyi Huang and Xuesong Geng and Xiaohu Xu and Yinben Xia}, title = {{Adaptive Routing Notification}}, pagetotal = 13, year = 2024, month = sep, day = 14, abstract = {Large-scale supercomputing and AI data centers utilize multipath to implement load balancing and/or improve transport reliability. Adaptive routing (AR), widely used in direct topologies such as dragonfly, is growing popular in commodity data centers to dynamically adjust routing policies based on path congestion and failures. When congestion or failure occurs, the sensing node can not only apply AR locally but also send the congestion/failure information to other nodes in a timely and accurate manner to enforce AR on other nodes, thus avoiding exacerbating congestion on the reported path. This document specifies Adaptive Routing Notification (ARN), a general mechanism to proactively disseminate congestion detection and congestion elimination information for remote nodes to perform re-routing policies.}, }