Alternate Name: Service Domain::Service ABE::QoS Service ABE::Network Forwarding Service ABE::Traffic Identification ABE
Category: [a] Class
The function of a MarkerService is to mark packets in a flow so that different devices in the network know how to treat the traffic that these packets belong to. This is done by #@#@coloring#@#@ a packet so that it can be identified and distinguished among other packets that are receiving traffic conditioning. In effect, this partitions a network into multiple priority levels or classes. Marking packets is done using a technology-specific mechanism, such as the ToS byte, the DSCP, or other methods for other media.\n\nIn DEN-ng, this function is modeled by the MarkerService. This service will mark a selected field in a network packet with a specified value. Packets are marked in order to indicate to downstream components what types of TrafficConditioningServices they will subsequently receive.\n\nThe definition of how to mark a particular packet is defined using the MarkerPool class.\n\nNote that there is a fundamental difference between its two subclasses. StandardMarkerService enables different types of technology-specific marking, which directly affect subsequent operations, to be defined. Examples of this include the difference between DiffServ marking and IEEE 802 marking. The PreambleMarkingService is used to capture the result of traffic conditioning operations and store them in a preamble. The two types of marking can be combined in some implementations.\n
This was created from the Frameworx 16.0 Model