RE: TE Requirements Draft - ELSP

["Joel M. Halpern" <joel@stevecrocker.com>]

If the ratio is different for each LSP, then the elements need to know it.
However, if the ratio is fixed across the service provider, then there are 
ways to engineer traffic (that is what we are doing here, right?) that 
avoid needing to know internally the component weights.  (And yes, you 
don't lose capacity in doing so.)

If there are two types of LSPs which mix traffic classes in two different 
proportions, then you probably start having trouble, although I have not 
analysed that as carefully.

Yours,
Joel M. Halpern

At 10:49 AM 11/22/01 +0100, Roberto Mameli (ERI) wrote:
>Referring to Jim's example (where ratio between voice-sig and 
>voice-payload is known and stable so both traffic can be treated together 
>as a whole from CSPF viewpoint) my concern is the following. I understand 
>that the ratio voice-sig/voice-payload is known, but I guess that it is 
>known only to the user originating these flows. Since there is no way to 
>signal this ratio to network elements I guess that those elements don't 
>know the exact proportion of the two types of traffic carried within the E-LSP.
>
>Here comes up my question: do network elements along the path need to know 
>this ratio of traffic? I think they do, and this is what the protocol 
>doesn't allow at the moment. But maybe this is not an issue and I have 
>just misunderstood the problem. In that case, I guess that all the issues 
>related to the allocation of intra-LSP resources are up to the LSP 
>ingress. So again, I don't see a great difference with the standard 
>DiffServ model, and this is the reason that leads me to the conclusion 
>that probably this is not what is commonly known as "aggregate TE".