> -> - scalability: Since you are maintaining multiple Routing
> -> tables, doing at line rate is pretty difficult and hence
> -> doesnt scale well.
> I agree with you here. Yes! there are performance and
> scalability problems if we go for DiffRouting in a
> hop-by-hop fashion. Then you have to maintain
> different route tables, line rate forwarding issues etc etc.
>
> That is why we went for source routing (using MPLS-TE).
> That effectively solved the problem of maintaining
> multiple routing tables. Connection-less to connection-oriented
> move (with small fixed length label lookup) solved the
> problem of line rate forwarding (directly or indirectly).
>
> Now we are moving towards MPLS-TE with DiffServ.
who told you diffserv-aware MPLS -TE scalable?
Section 4.4 and 3.1 of http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-05.txt clearly points out the scalability problems.
This archive was generated by hypermail 2b29 : Mon Aug 04 2003 - 04:10:04 EDT