I seem to have got myself confused with QoS / CoS (Class of Service) over MPLS etc and downstream network locations not on our MPLS cloud. The idea was to bring either Juniper / Riverbed WAN optimisers at each sites and see if we can get out of the cycle of constantly upgrading our MPLS links.
Now, I was wondering, in a post WAN Optimiser scenario, For example, if we have users in London and users in Berlin who want to videoconference with each other, a perfectly natural thing for users to want to do, it will be fine and dandy because we will have Qos/CoS on the MPLS and that will deliver the packets in a timely manner. But, CoS is about getting the packets there fast, not about partitioning the bandwidth, so if the guys doing the video conference decide they want to run it in High Definition at 2Mbps, then all of the bandwidth will disappear as they have consumed it all (assuming a 2Mbps pipe in London) and all other applications regardless of class will stop, if video is classfied as higher than say, our E-Business Suite.
So, here is the question, do we need our WAN Optimisers to be (some thing like) Packeteers also? Something like a Traffic Shaping capability? The two devices are mutually exclusive as we cant allocate bandwidth if WAN Optimiser has allocated it all to get it to go fast.
Am I clear??
This will be more acute on the Intra site connections that are made up of internet VPN and point to point leased lines as these cant do CoS (unless we fancy programming some Cisco routers to do CoS (I dont)), so for these non MPLS connected sites, should we be considering Packeteer instead of Riverbed????
Do you see what I am getting at? And what the answer is?