RFC 1349:Type of Service in the Internet Protocol ...
RFC-Ref

throughput


Click on the red underlined text to get to the source

... call setup or per-packet charges, while others do not do usage-based charging. Throughput and delay also vary widely. Often there are tradeoffs: the path that provides the highest throughput may well not ...
... charging. Throughput and delay also vary widely. Often there are tradeoffs: the path that provides the highest throughput may well not be the one that provides the lowest delay or the lowest monetary cost. Therefore, the "optimal" path for a packet to follow through ...


... network should make tradeoffs between throughput, delay, reliability, and cost. The TOS ...


... 1000 -- minimize delay 0100 -- maximize throughput 0010 -- maximize reliability ...


... sending side of a bulk data transfer application should request that throughput be maximized, whereas the receiving side might request that delay be minimized (assuming that it is primarily ...


... FTP Control 1000 (minimize delay) Data (2) 0100 (maximize throughput) TFTP ...
... SMTP (3) Command phase 1000 (minimize delay) DATA phase 0100 (maximize throughput) ----- Type-of-Service ...
... TCP Query 0000 Zone Transfer 0100 (maximize throughput) NNTP ...
... 0000 (all normal) Use default metric 1000 (minimize delay) Use delay metric 0100 (maximize throughput) Use default metric 0010 (maximize reliability) Use reliability ...
... reliability 6 0011 8 0100 maximize throughput 10 0101 12 0110 ...


... TOS field to request that the network choose a path which maximizes throughput, but cannot use that mechanism to say that it needs or wants a particular number of kilobytes or megabytes per second ...
... requires, it would be inappropriate for the network to decide to discard a packet which requested maximal throughput because no "high throughput" path was available. ...
... to discard a packet which requested maximal throughput because no "high throughput" path was available. The inability to provide resource guarantees is a serious drawback ...



Google
Web
RFC-Ref