The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Oct> msg00026



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

RE: MPLS QoS architecture

  • From: "Mooney Sherman" <Mooney.Sherman@gov.ab.ca>
  • Date: Sat, 9 Oct 2004 10:30:55 -0600
  • Resent-Date: Sat, 9 Oct 2004 12:54:03 -0400
  • X-MIME-Autoconverted: from quoted-printable to 8bit by host.secure4-hosting.net id i99GVkWe008320
  • X-OriginalArrivalTime: 09 Oct 2004 16:30:54.0382 (UTC) FILETIME=[59023CE0:01C4AE1D]

 Hi Sudeep:

One option is Diffserv and using DSCP for prioritizing different traffic, There are other QoS methods available but in MPLS core - this is more common.

When you say end to end do you mean desk top to desk top or do you mean PE to PE? Most service providers only provide SLAs from PE to PE and the customer needs to provide QoS that can mark the QoS using the same methodology as the service provider.

Hope this helps.


Mooney

-----Original Message-----
From: Sudeep Goyal
To: mpls-ops@mplsrc.com
Sent: 10/8/2004 3:20 PM
Subject: [MPLS-OPS]: MPLS QoS architecture

Hi all,

  I am working on QoS architecture for MPLS and I need to provide 
"end-to-end" QoS guarantees (delay, jitter, latency) for different 
applications.
  Is anyone here aware of such work anywhere or doing smt related?

Thanks a lot,

Regards,
Sudeep


--
When a great leader's work is done, people say "we did it ourselves".
-Lao Tzu

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
------------------------------------------------------------------------
--------------------

This communication is intended for the use of the recipient to which it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communication received in error, or subsequent
reply, should be deleted or destroyed.

--------------------------------------------------------------------------------------------

This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml