The MPLS-OPS Archive

[Michael Hallgren <m.hallgren@free.fr>]

Quoting Srihari Raghavan <sraghava@vt.edu>:

> Hi all,

Hi,


>   While going through the "MPLS technology and applications" book and
> other
> web resources, it seems to point out that Route aggregation will be very
> bad
> for MPLS (particularly in control-driven mode, essential for MPLS
> Traffic
> Engineering), in that the intermediate LSRs will be forced to do L3
> forwarding too. I also happened to see a paper on label switching in
> IPv6
> networks, saying that, high route aggregation in IPv6 networks would
> be
> detrimental for MPLS.
>   Can anyone please explain the consequences or some
> facts/explanations
> regarding this problem. I happen to think that future networks will use
> a
> good amount of route aggregation.



Well, to my understanding, the design planning/complexity level's getting 
somewhat higher in the way that network planning is becoming (even) more
important - and based on a slightly different set of axioms (that's where
complexity - like prognostics on traffic patterns, etc, come into the
picture; wiser guys than I, may have discussed context sensitive schemes?).

Thing is that, IP space distribution would preferrably be done with FEC's
in mind. Unless done, we'll have to return to routing for what's not fit into 
the partitioned space - since "not belonging to class" means having to be
treated as a non-conform special case or (rather) default - like any "by 
cases" deterministic algorithm.

mh


> 
> Thank you in advance
> 
> Srihari Raghavan
> Graduate student
> Dept. of Computer Science
> Virginia Tech
> =========================
> 
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
> 



--

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml