At 12:02 PM 8/27/2008, Yakov Rekhter wrote:
Lou, > If you drop the "unless they share identical Traffic Engineering > Attributes" then we have alignment. If they do share identical TE attributes, then there is no problem to aggregate such routes. So, the current text is correct. Yakov.
I think you need some additional semantic and aggregation function definition if you want to aggregate. (For example: Does the TE aggregate represent the resources available to *each* route or to *all* the routes? If the latter, what's the distribution function?)
Also I think some discussion on impact on scaling is warranted. (consider the case where each <PPI, CPI> tuple from a PE now needs it's own advisement due to dissimilar TE information per port.)
Lou