Hi Chris, |So, it's not that RRG doesn't acknowledge this problem, it's that the |problem ought to be fixed (to some extent at least) with the work RRG |is doing?
Yes, of course the problem exists, but again, it's more to be fixed within IDR. BGP is not an architecture; it's a protocol. Protocol changes are in scope for IDR and architecture changes are in scope for RRG. |> Paths that are introduced for the sake of traffic |engineering are a well |> understood and self-inflicted problem. If those folks that |introduced the | |I don't think it's just 'traffic engineering' that is the problem |here, it's often other things like L3vpn/2547-vpn/mpls-vpn, 'internal |services' or 'service networks' (Peter's notes about phones on IP |roaming around the sprint core). | |Surely TE prefixes are issues, but that's not the only source of |internal route growth... one large one is 'this IP thing, it's kinda |successful!' (convergence). VPN prefixes are also wholly self-inflicted and have been well discussed as a scalability issue for a decade or more. No one is required to run VPNs, so it's also a self-inflicted problem, just as if you decided to run DECnet. ;-) Tony _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
