Separating Address Families and the Purpose of Address Families. Every time I come to read this thread, this point I'm going to comment on comes to mind, and I end up forgetting.
I went back to the initial message of the thread to mention what I believe is important, which is separating address families according to their role within the network. From my point of view, in a network that is no longer so small, with several devices, it makes sense that Route Reflector services are separated according to their functions in the network. I like the model in which the base Address Families and the end-service Address Families are separated. The example I like to give most is to leave IPv4 and IPv6 Main, RT-Filter, private L3VPN, L2VPN VPLS, BGP-LU in one set of RRs. And VPNv4+VPNv6 for DFZ/Cache/PNIs, and FlowSpec in another set of RRs. Here in Bob's fantastic world, which is my brain, the role of EVPN is changing. But so far I see it within the first group of RRs. Even if you put these two types of RRs in the same box (because it's still too small to justify separating them), if you use different loopbacks for the two types of RRs... Separating them in the future to allow scaling becomes very simple. It's worth saying that I believe it's always better to improve the RR in Off-Path. Em ter., 2 de jun. de 2026 às 03:22, Tom Samplonius via NANOG < [email protected]> escreveu: > Hi, > > Is Free Range Routing (FRR) a viable choice for a pure BGP route > reflector for a regional ISP with ~ 35 routers? A mix of L3VPN-MPLS and > BGP-EVPN services. Full transit, plus some peering. About 5 x L3VPN > instances, and maybe 500 x EVPN-MPLS instances. > > I don’t see a lot of posts of people using FRR for RR. And not a lot of > people reporting issues, so maybe it is just the perfect RR solution? > > > > Tom > > _______________________________________________ > NANOG mailing list > > https://lists.nanog.org/archives/list/[email protected]/message/STLGD7H4RECEM3F4IFDWRZWXL7L4M5KJ/ -- Douglas Fernando Fischer Engº de Controle e Automação _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/QASZOXRF5DY2KX556YDTIC3UMC7KZ3SR/
