... installed.^1.1

An error message like RTNETLINK answers: Invalid argument indicates that the kernel does not contain support for traffic control, or that some elements are not enabled. A message like example.sh: tc: command not found indicates that iproute2/tc is not installed at all, while a message like Unknown qdisc "dsmark", hence option "dev" is unparsable indicates that iproute2/tc was built without support for Differentiated Services.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...dsmark^2.1

dsmark can be called egress when used as the top-level egress queuing discipline of a device, which is the only place where dsmark is normally used. Therefore, we use dsmark and egress as synonyms in this document.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...priomap^2.2

For a description of priomap, please refer to the section on prio in [LARTC].

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...^2.3

fields.tc is split into the files meta.tc for packet meta data, fields4.tc for IPv4 and IP version independent headers, and fields6.tc for IPv6 headers. All three are included by fields.tc and should not be included individually.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... octet^2.4

We follow current practice in calling the second byte of the IPv4 header the ``TOS octet'' and not the ``TOS field'', because the original name ``TOS field'' ([RFC791]) was redefined in now obsolete [RFC1349].

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...^2.5

http://www.iana.org/assignments/port-numbers

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... reference''^3.1

This is actually closer to the even more exotic ``call by name'', e.g. also MACRO(field sth) would work in this example.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... empty.^6.1

end does this by simply advancing the simulation time to ``infinity'', a value larger than any time that can be specified in the simulation, and serving all events that occur until then, including new events generated by them.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... packet.^6.2

The heuristic used for this is that the first byte in the packet must be in the range 0x45$\ldots$0x4f, and the packet must contain at least twenty bytes.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...^6.3

protocol is preserved because this information is typically stored in link-layer headers, and is therefore preserved in real life too.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

... output.^7.1

While we use the expression key ``phrase'', all currently recognized phrases are actually single words. This may change in the future.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.