[45719] in North American Network Operators' Group
Re: it's here
daemon@ATHENA.MIT.EDU (Ron da Silva)
Wed Feb 13 12:09:25 2002
Date: Wed, 13 Feb 2002 12:03:42 -0500
From: Ron da Silva <ron@aol.net>
To: nanog@merit.edu
Message-ID: <20020213120342.M4664@aol.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.33.0202131602130.3098-100000@rampart.argfrp.us.uu.net>; from chris@UU.NET on Wed, Feb 13, 2002 at 04:06:23PM +0000
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, Feb 13, 2002 at 04:06:23PM +0000, Christopher L. Morrow wrote:
>
> Long term all users of internet routing hardware (or routing hardware in
> general) should push their vendors to implement line-rate filtering. There
> really is no reason NOT to do it is there? Even better would be the
> ability to look inside the entire packet, this way the next code-red can
> be stopped at a higher level in the network where people that actually
> care about the problem can take appropriate action.
BOTH linerate filtering and packet inspection should be part of the minimal
requirements to sell routing hardware. Hmm...so in case any vendor out there
hasn't heard this directly from us, consider this a clarification of our
requirements. And UUnet's...and ?? any other providers want to make sure
that the vendor community gets the message here?
-ron
