The MPLS WG Archive

[Jay Wang <jawang@cosinecom.com>]

Title: RE: Fw: MPLS and CAC

Well, "Gold" when used as an adjective is a relative term.
But in any case, no, an accurate characterization of customer
traffic does not lead to a conclusion that tells you whether you
can overbook your "Gold" customer or not.  This is primary a
SLA and policy issue.  One way of the other, accurate customer
traffic profiling only gives you the ability to execute your SLA
more precisely and possibly more efficiently by, for example,
taking advantage of multiplexing gain.

regards,

- Jay 

> -----Original Message-----
> From: Ram Krishnan [mailto:ram@axiowave.com]
> Sent: Wednesday, August 30, 2000 2:02 PM
> To: 'Kireeti Kompella'; david.charlap@marconi.com; mpls@UU.NET
> Subject: RE: Fw: MPLS and CAC
>
>
> Even with Gold customers, you can do this as long as you
> can characterise the traffic profiles of your Gold customers
> carefully and provision parameters such as effective bandwidth
> and buffer space accurately.
>
> Regards,
> Ram
>
>
> While we are on the subject of overbooking, let me point out two
> things:
>    a) it makes sense to traffic engineer best effort IP traffic,
>       and assign it a bandwidth parameter (a point that I believe
>       Curtis mentioned, but I'm speaking from memory);
>    b) persistent overbooking is fairly common.
> (a) is a common reason for (b).
>
> One scenario for (b) is where you have bursty traffic (happens a
> lot with IP): say that some traffic trunk averages 40Mbps, but peaks
> to 70Mbps.  You could put two of these on a 100Mbps link, and most
> of the time, you are just fine.  If the two trunks peak at the same
> time, you have some dropped traffic, but on the whole, you come out
> ahead (modulo the SLAs with your customers).
>
> You may not want to do this with your Gold customers, but for best
> effort IP, this should work just fine.
>
> Kireeti.
>