Description: A row is created in this table automatically by an LSR for every interface capable of supporting MPLS and is enable to do so, since it AUGMENTs the mplsInterfaceConfTable.

According to the [DSTE-REQ] draft, an administrator can deploy upto 8 Class-Types. It also allows the tweaking of the overbooking ratio for each of these Class-Types on a per interface basis.

Each entry in this table allows the administrator to configure a overbooking factor on a per-link per-class-type basis. [However, if the mplsInterfaceConfTable has a conceptual row with index 0, all of the LOMs corresponding to that row will be no significance and will can not be modified]

The overbooking ration defined in this entry, will be significant for different Class-Types, only when the corresponding Class-Type is supported in the LSR (see the mplsDsTeClassTable).

Additionally, agent might have to enforce other requirements as per the Bandwidth Constraint Model.

The units of the bandwidth constraints are in terms of percentage (%) of the actual bandwidth requested by the connection. A LOM with value 100 indicates no overbooking in use <100 indicates underbooking in use >100 indicates overbooking in use.

By default, all the overbooking multipliers defined in this table will be initialized to 100 (i.e. no overbooking).