Kurtis, My apologies on the low SNR. The original question(s) centered around the customer requirements/applications/experience and I thought the product guys could speak to it better than I ... and certainly and without giving away any of our "patent pending processes". :) I think "native" can be translated as to mean "non-ATM". All core links are PPP/POS. MPLS does not imply or require DSCP, or vice versa. DSCP/EXP promotion ensures priority packets to be forwarded ahead of best effort at each hop thru the network. Could this be done other ways? Sure. The original question was how was/is this being done for customer traffic - this is how we do it in the core...along with queueing gymnastics. As for MPLS features, I think fast re-route qualifies. MPLS also provides traffic eng capabilities, as well as in-order packet delivery, which we've found to be useful for customer voice 'n video traffic. J -----Original Message----- From: Kurt Erik Lindqvist [mailto:kurtis@kurtis.pp.se] Sent: Thursday, July 25, 2002 5:54 AM To: nanog@merit.edu Subject: RE: QoS/CoS in the real world? Appart from that this to me looks like a marketing post....

Sorry I didn't see this note earlier, but wanted to make you aware that Masergy Communications is actually offering such a service on a native MPLS based IP network. We provide differentiated IP services via

"native MPLS based IP network" ? Native to what?

MPLS based IP network. We provide differentiated IP services via customer DSCP marking at the network edge. QoS is supported end to end

through the Masergy core via promotion to the MPLS EXP marking.

Uhm, I never figured out why we need MPLS to honor the DSCP markings. After reading further in the text it doesn't seem to me as if you are using any of the MPLS "features" either... Sorry - I couldn't resist... - kurtis -