Hi, I have one little question/doubt on scalability point of RIFT ...
Assume that someone would like to signal IPv6 prefix SID for Segment Routing in the underlay within RIFT. Wouldn't it result in amount of protocol state in full analogy to massive deaggregation - which as of today is designed to be very careful and limited operation only at moments of failure(s) ? I sort of find it a bit surprising that RIFT draft does not provide encoding for SID distribution when it is positioned as an alternative to other protocols (IGPs or BGP) which already provide ability to carry all types of SIDs. Cheers, Robert. PS1: Horizontal links which were discussed could be installed to offload from fabric transit massive amount of data (ex: storage mirroring) directly between leafs or L3 TORs and not to be treated as "backup". PS2: Restricting any protocol to specific topologies seems like pretty slippery slope to me. In any case if protocol does that it should also contain self detection mechanism of "unsupported topology" and flash red light in any NOC.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
