On Thu, 8 Feb 2024 at 17:11, Tom Beecher via juniper-nsp <juniper-nsp@puck.nether.net> wrote:
> For any use cases that you want protocol interaction, but not substantive > traffic forwarding capabilities , cRPD is by far the better option. No one is saying that cRPD isn't the future, just that there are a lot of existing deployments with vRR, which are run with some success, and the entire stability of the network depends on it. Whereas cRPD is a newer entrant, and early on back when I tested it, it was very feature incomplete in comparison. So those who are already running vRR, and are happy with it, changing to cRPD just to change to cRPD is simply bad risk. Many of us don't care about DRAM of vCPU, because you only need a small number of RRs, and DRAM/vCPU grows on trees. But we live in constant fear of the entire RR setup blowing up, so motivation for change needs to be solid and ideally backed by examples of success in a similar role in your circle of people. -- ++ytti _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
