The MPLS WG Archive

[neil.2.harrison@bt.com]

Venkata,

So that I can better understand what you mean here, can you please then
explain:
-	how you are going to know how to load balance when we have IP
clients and other clients of the LSPs (eg the XoverMPLS PWE3 drafts)
-	how pkt misordering is avoided for clients that expect ordered
delivery?
-	how correctly behaving load-balancing is ensured, ie how are defects
in the load balancing detected/diagnosed?
-	where is all the above specified?

regards, Neil

> -----Original Message-----
> From: Naidu, Venkata [mailto:Venkata.Naidu@Marconi.com]
> Sent: 27 June 2002 22:03
> To: 'Shahram Davari'; 'Eric Osborne'; George Sheng
> Cc: scullptor@yahoo.com; mpls@UU.NET
> Subject: RE: your mail
> 
> 
> Shahram,
> 
> -> > ECMP is inherent in the architecture. 
> -> 
> -> What? ECMP is a kludge to overcome LDP's inability to TE. If 
> -> you think about it doing hashing of multiple labels and 
> -> perhaps IP header in the middle of an LSP actually defeats 
> -> the purpose of MPLS, which was supposed to be have a simple 
> -> label lookup in the core.
> 
>  Who said that ECMP will be achieved only by hashing labels
>  or IP header? I think you are thinking IP ECMP methods
>  (RFCs 2991 and 2992) to solve MPLS ECMP. You can do ECMP
>  in what ever way a vendor likes - after all, it is for
>  load balancing. You can still achieve simple label lookup at
>  the core by using appropriate ECMP technique(s).
> 
> --
> Venkata.
>