On Wed, Mar 28, 2012 at 12:01 PM, Paul Jakma <[email protected]> wrote: > On Wed, 28 Mar 2012, Jakob Heitz wrote: > >> The issue is SIDR can not aggregate multiple paths. > > >> Should SIDR work on path aggregation? > > > If we ever want to make routing state scale sub-linearly (i.e. make IDR > "compact") in the size of the internet, then we're almost certainly going to > need some form of conglomeration of routing information in some shape or > form. Still having support for aggregation in BGP could then be useful.
or we could have fixed the problem with locator/id separation... oh well. > > It'd be a shame if we ended up having to choose between scalable and secure > routing. it's hardly a choice of one or the other, framing the question in this manner is a 'suckers choice'. <http://sourcesofinsight.com/refuse-the-suckers-choice-4/> It's certianly possible that at some point when aggregation between AS's becomes used properly and effectively... someone will figure out the security properties if this configuration. > (OTOH scalable routing is potentially so far off in the future, and might be > so different, that it's hard to say what level of extra engineering or > overhead, if any would be justified for SIDR). it seems that to date, folk can't seem to figure out the aggregation bits, maybe that will change in the future. -chris _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
