The MPLS WG Archive

[Snigdho Bardalai <snigdho.bardalai@fnc.fujitsu.com>]

Neetu Gupta wrote:

> Snigdho,
>     When the LSPs are created using Integrated Signalling protocol, the entry
> is made in the Forwarding Engine, that contains a label for the information:
> Source Address, Source Port, Destination Address, DestPort, Protocol, Class of
> Service. This Class of Service can be the value specified for the Class of
> Service in the Service Level Agreement with the Customer.
> So, when the data packet comes, all these above mentioned fields are matched
> with the fields in the IP Header of the Packet including  Class of Service
> that is matched to TOS byte.
> So, can't we map Class of Service to any of the DSCP values, and specify the
> corresponding DSCP value for COS in the agreement with the Customer?

Sure you can - technically !!! It may not always be acceptable, but instead of
your customer being aware of such mappings you could perform the mapping
at an ingress LER. You must keep in mind that IntServ and DiffServ services
do not match in terms of service characteristics, so mapping services
could be tricky.

>
> Snigdho Bardalai wrote:
>
> > If you expect to have a DiffServ compliant application the IP header TOS
> > bits should contain the DiffServ DSCP values like expedited, assured
> > services etc.
> >
> > But if you expect to support Integrated Services the TOS bits in the IP
> > header may not have any significance.
> >
> > Snigdho
> >

Snigdho

--
Snigdho C. Bardalai
Phone - (972) 479-2951
Fax   - (972) 479-4724
Email - snigdho.bardalai@fnc.fujitsu.com