classifier table, thus simplifying management
of the information.- Classifier table – indicates how traffic flows
are to be sorted. The criteria used here could
in theory be any identifiable property of a par-
ticular flow or behaviour aggregate (DSCP). - Metering table – implemented as a simple set
of pass/fail tests applied to a stream of traffic
passing a particular token bucket meter. The
action to be taken with conforming and non-
conforming traffic is specified in the Action
table. It is also possible to cascade the meters
in this table for more complex behaviour. - Action table – Several actions are considered
in this specification: traffic marking, counting
of the traffic passing a certain point, applying
a drop policy, queueing of traffic. The ele-
ments in this table specify behaviour resulting
from a classification, a metering operation or
another action. - Queue table – This table specifies the be-
haviour of individual queues, in terms of
bandwidth and queuing mechanisms. The
elements specified in this table are the result
of a queueing action and can be used for both
queuing and shaping.
6 Concluding Remarks
Efficiently managing the IP-based network is an
obvious goal for an operator. Searching for this,
the operator would utilise different mechanisms
referring to the IP level, the management system
and on the business level. This paper has out-
lined some of the essential aspects that should be
considered, relating Traffic Engineering to man-
agement systems, policy and Service Level
Agreements.
References
[Asga01] Asfari, A et al. 2001. A Monitoring
and Measurement Architecture for Traffic Engi-
neering IP Networks. In: Proc. of IEEE/IFIP/
IEE Int. Symp. on Telecom. (IST2001).
[eTOM] 2001. TeleManagement Forum GB921:
eTOM – The Business Process Framework. Ver.
1.0.
[ID_bgpte] Abarbanel, B, Venkatachalam, S.
- BGP-4 support for Traffic Engineering.
draft-abarbanel-idr-bgp4-te-01.txt. Work in
progress.
[ID_cim] IETF. 2000. Moore, B et al. Policy
Core Information Model – Version 1 Specifica-
tion.draft-ietf-policy-core-info-model-08.txt.
Work in progress.
[ID_COPS] Jacquenet, C. 2001. A COPS client-
type for IP traffic engineering.draft-jacquenet-
ip-te-cops-02.txt. Work in progress.[ID_fwpib] IETF. 2000. Fine, M et al. Frame-
work Policy Information Base.draft-ieft-rap-
frameworkpib-03.txt. Work in progress.[ID_MPLScops] Reichmeyer, F, Wright, S, Gib-
son, M. 2000. COPS Usage for MPLS/Traffic
Engineering.draft-franr-mpls-cops-00.txt. Work
in progress.[ID_polreq] IETF. 2000. Mahon, H et al.
Requirements for a Policy Management System.
draft-ietf-policy-req-02.txt. Work in progress.[ID_pterm] IETF. 2000. Westerinen, A et al.
Policy Terminology.draft-ietf-policy-terminol-
ogy-01.txt. Work in progress.[ID_qpim] IETF. 2000. Snir, Y et al. Policy
Framework QoS Information Model.draft-ietf-
policy-qos-ifno-model-02.txt. Work in progress.[ID_sfsls] Rajan, R et al. 2000. Service Level
Specification for Inter-domain QoS Negotiation.
Work in progress.[RFC2251] IETF. 1997. Wahl, M, Howes, T,
Kille, S. Lightweight Directory Access Protocol
(v3).(RFC 2251.)[RFC2570] IETF. 1999. Case, J et al. Introduc-
tion to Version 3 of the Internet-standard Net-
work Management Framework.(RFC 2570.)[RFC2571] IETF. 1999. Harrington, D et al. An
Architecture for Describing SNMP Management
Frameworks.(RFC 2571.)[RFC2572] IETF. 1999. Case, J et al. Message
Processing and Dispatching for the Simple Net-
work Management Protocol (SNMP).(RFC
2572.)[RFC2574] IETF. 1999. Blumenthal, U, Wijnen,
B. User-based Security Model (USM) for ver-
sion 3 of the Simple Network Management Pro-
tocol (SNMPv3).(RFC 2574.)[RFC2750] IETF. 2000. Herzog, S. RSVP Exten-
sions for Policy Control.(RFC 2750.)[RFC2753] IETF. 2000. Yavatkar, R et al. A
Framework or Policy-based Admission Control.
(RFC 2753.)[RFC2998] IETF. 2000. Bernet, Y et al. A
Framework for Integrated Services Operation
over Diffserv Networks.(RFC 2998.)