The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Nov> msg00041



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

CLASSTYPE object

  • From: Nabil Seddigh <nseddigh@tropicnetworks.com>
  • Date: Wed, 07 Nov 2001 11:28:41 -0500
  • CC: "'Vishal M'" <vishal_study@yahoo.com>, mpls@UU.NET
  • Organization: Tropic Networks

Sami,

Currently, the CLASSTYPE object cannot really be used with 
E-LSPs in the manner you describe. The CLASSTYPE object is only
useful with L-LSPs.

In order to utilize the concept of bandwidth pools in E-LSP,
one needs to be able to signal traffic parameters per class 
or per-PSC. That capability is not present in the standards today.

The closest proposal to achieve what you describe is the following:
http://www.ietf.org/internet-drafts/draft-ganti-mpls-diffserv-elsp-00.txt

Best,
Nabil Seddigh

> 
> Your understanding that the CLASSTYPE is used to
> specify the bandwidth pool to be used for allocating
> resources during LSP Setup is correct. In this context,
> the service class which is signalled via EXP bits
> (in the case of E-LSPs) dictate the treatment given
> to the individual packets, and the CLASSTYPE, which
> is signalled per LSP, dictates where the bandwidth
> is coming from (used in CAC).
> 
> [....deleted....]
>
> Ideally, I would prefer to get rid of the CLASSTYPE
> concept and advertise available bandwidth per service class.