Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!agate!ucbvax!INRIA.INRIA.FR!prindevi
From: prindevi@INRIA.INRIA.FR (Philippe-Andre Prindeville)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  When is a link saturated?
Message-ID: <9101160021.AA09073@inria.inria.fr>
Date: 16 Jan 91 00:21:45 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21


	well, to my best understanding the "priority output queue" feature as
	implemented in cisco 8.2 DOESN'T support giving high priority to
	telnet, rlogin, etc. interactive tcp/ip services no matter what the
	announcement on sep 18, 1990 said.  this is because the extended
	access lists (on which the feature is based) simply are not powerfull
	enough to do so.  i'm pleased if someone can prove that i'm wrong by
	giving me the proper configuration commands.

You're overlooking a point here:  the *hosts* are just as involved
in this process -- they *must* use proper type-of-service labelling
of their packets (as per Host Req.) for this to work.  It is not
the job of the router to look at Transport-level information, no
matter what nifty features ciscos have.  Thus telnet/rlogin must
use low-delay, and ftp high throughput service specifiers in their
IP header.

The latest version of telnet, which will be released with 4.4,
includes code to enable this option.

-Philip