Hi, Pretty interesting idea however I have few basic questions:
a) Why do you define a new SID type instead of using existing node or adj SID and putting flow control as a SID function ? The entire idea of network programming is not about adding more and more SID types ... it is about inventing and adding network functions. b) If this is for WAN how do you assure all nodes on the path between src and dst support PFC ? I assume by WAN you mean number of transit ASNs with different IGPs and no BGP-LS NNI running. Or do you mean that such WAN would always be under the same administrative domain ? c) I recommend you add some OAM enhancements to indicate with ping/traceroute that such support is there. Moreover I also would like to see reporting of the state of the buffers with any already defined inband OAM SR mechanism. d) Your proposal requires a lot of queues and buffers to be available on each transit node. That's pretty expensive and sometimes harmful for real time data where microseconds or less matters. Have you done any comparison or educated simulations how would it compare with end-to-end ECN say using DCTCP ? Wouldn't end to end not be more efficient if we are talking about few WAN nodes under same administration ? Thx a lot, Robert On Tue, Jun 24, 2025 at 6:13 AM 阮征(联通集团本部) <[email protected]> wrote: > Hello everyone, > > We have just submitted a new draft titled "Priority-based Flow Control SID > in SRv6". The concept of this draft originates from cross-DC communication > scenarios, aiming to achieve end-to-end flow control through coordination > between WAN and data center networks by enhancing flow control capabilities > of selected WAN devices, thereby reducing network packet loss. > > This document proposes a new End.X.PFC SID to identify network interfaces > with PFC capabilities, enabling backpressure frames to be transmitted > across hops via SRv6 tunnels. > > This technology can be leveraged to mitigate congestion and packet loss > caused by micro-burst traffic in the network, with enhanced effectiveness > in specific scenarios such as RDMA over WAN and elephant flow environments. > > Please review the draft in the following link: > > > https://datatracker.ietf.org/doc/draft-ruan-spring-priority-flow-control-sid/ > > Welcome any feedback and comments. > > Best Regards > > Ruanzheng on behalf of co-authors > > _______________________________________________ > spring mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
