Return-Path: <jhawk@MIT.EDU>
Received: from central-city-carrier-station.mit.edu by po11.mit.edu (8.9.2/4.7) id TAA00341; Wed, 26 Sep 2001 19:02:19 -0400 (EDT)
Received: from melbourne-city-street.mit.edu (MELBOURNE-CITY-STREET.MIT.EDU [18.7.21.86])
	by central-city-carrier-station.mit.edu (8.9.2/8.9.2) with ESMTP id TAA21846;
	Wed, 26 Sep 2001 19:02:18 -0400 (EDT)
Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73])
	by melbourne-city-street.mit.edu (8.9.2/8.9.2) with ESMTP id TAA20616;
	Wed, 26 Sep 2001 19:02:18 -0400 (EDT)
Received: (from jhawk@localhost) by multics.mit.edu (8.9.3)
	id TAA21518; Wed, 26 Sep 2001 19:02:17 -0400 (EDT)
Date: Wed, 26 Sep 2001 19:02:17 -0400
From: John Hawkinson <jhawk@MIT.EDU>
To: Theodore Tso <tytso@MIT.EDU>
Cc: "McNerney, Tim" <TMcNerney@chipwrights.com>,
        "'sipb@mit.edu'" <sipb@MIT.EDU>
Subject: Re: Who do I talk to about e19-rtr-backbone.mit.edu lossage?
Message-ID: <20010926190216.P3186@multics.mit.edu>
References: <93A4BBB9515ED411AE9D00508BD955A5198C1F@intranet> <20010922124756.E853@thunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20010922124756.E853@thunk.org>
User-Agent: Mutt/1.3.19i

Theodore Tso <tytso@MIT.EDU> wrote on Sat, 22 Sep 2001
at 12:47:56 -0400 in <20010922124756.E853@thunk.org>:

> 	I think you're misdiagnosing the problem.  As others have
> said, the main problem was caused by worms running on Microsoft boxes

Remember that Tim is referring to a problem that he's seen
building for months if not years.

> No, actually it doesn't make any sense.  Remember, a router's job is
> to as quickly as possible, take the packet and move it some where
> else.  So if it's going to get handled at all, it's going to be moved
> as expeditiously as possible to the output interface.  So packets are
> *always* going to be handled as with as low a latency as possible.  A
> router can't afford to hang onto a packet, simply because it would
> take too much memory and processing power.

That's not true, Ted. There is support in high-speed routers for
doing priority queueing and related things. It incurs some
performance penalty, but typically on the order of 5-15%, which is
generally considered an acceptable price to pay.

> If you're trying to squeeze packets down a congested, slow link, such
> as down a slow 28.8k PPP connection, then it might make sense to
> reorder packets based on the port or type-of-service bits in the IP
> header, so that telnet packets get sent ahead of bulk ftp packets.

I don't think there is any in-principal problem with doing this sort
of prioritization at high speeds, no. What are you referring to?

> Finally, this sort of thing which you're describing requires making
> changes to the router's hardware and software, and as such is
> something for which SIPB (or even MIT Network Opertions) could do much
> about.  If you want to make such changes, you'd have to go work for
> Cisco and then try to exaplain to them why your idea is one which
> their thousands of network engineers haven't tried already.  :-)

Cisco's routers support this already.

--jhawk
