The MPLS WG Archive

[PaulYungShain.Wu@swisscom.com]

Dear Gupta:

A scenario:
The customer get a subscrition for a service, say Olympic Gold data service,
with a SP.
At the time of authentication via the AAA-Server. The SP might be in the
position to assign the DSCP according to the subscrition contract to the
user. The DSCP of the IP header of the customer's data will be set
accordingly.

At the point of interconnection (PoI) - where the PE will translate the
DDSCP into CoS - the corresponding VPN, say VPN-Gold of this SP, will be
used for forwarding the user data according to the SLS (Service Level Spec)
and TCS (Traffic Conditioning Spec) contracted with the NP.

Is this feasible?

Regards,
Paul

-----Ursprüngliche Nachricht-----
Von: Neetu Gupta [mailto:neetug@daewoo.dti.daewoo.co.kr]
Gesendet am: Mittwoch, 7. Juni 2000 10:52
An: mpls
Betreff: Re: Applications running on RSVP Aware Host End

Eric,
    Does that mean the Customer will not set TOS byte in the data packet?

Then when the data packets are coming at the ingress point of the MPLS
Domain, how will it be known, to which Diff Serv LSP, the packet has to be
sent, since DSCP value is not set in the header.

Then, who will set the DSCP value?


Eric Gray wrote:

> Neetu,
>
>         Considering the primary application du jour
> for MPLS is traffic engineering, only network
> elements would determine the treatment of host
> packets in the network.  This could - for example
> - be the result of a service level agreement or
> a network domain local decision.
>
>         In general, it would be nice if the network
> operators could rely on hosts to properly set bits
> in the IP header according to how the packets will
> be treated in competition with other packets in a
> network.  But this is unlikely since "cheaters"
> prosper only too well.
>
> --
> Eric Gray