Return-path: <owner-nanog@merit.edu> Received: from psg.com ([147.28.0.62]) by rip.psg.com with esmtp (Exim 3.33 #1) id 15YyHE-0001K5-00 for randy@rip.psg.com; Mon, 20 Aug 2001 16:16:12 -0700 Received: from trapdoor.merit.edu ([198.108.1.26]) by psg.com with esmtp (Exim 3.33 #1) id 15YyH9-000BoL-00 for randy@psg.com; Mon, 20 Aug 2001 16:16:07 -0700 Received: by trapdoor.merit.edu (Postfix) id 6E4589125A; Mon, 20 Aug 2001 19:13:39 -0400 (EDT) Delivered-To: nanog-outgoing@trapdoor.merit.edu Received: by trapdoor.merit.edu (Postfix, from userid 56) id 401239125B; Mon, 20 Aug 2001 19:13:39 -0400 (EDT) Delivered-To: nanog@trapdoor.merit.edu Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id ACD079125A for <nanog@trapdoor.merit.edu>; Mon, 20 Aug 2001 19:13:36 -0400 (EDT) Received: by segue.merit.edu (Postfix) id 7FF3A5DDC6; Mon, 20 Aug 2001 19:13:36 -0400 (EDT) Delivered-To: nanog@merit.edu Received: from taxi.speedtrak.com (ssfnat-204.routescience.com [64.254.174.204]) by segue.merit.edu (Postfix) with ESMTP id D54645DDA1 for <nanog@merit.edu>; Mon, 20 Aug 2001 19:13:35 -0400 (EDT) Received: from routescience.com (dhcp-64-101.speedtrak.com [192.168.64.101]) by taxi.speedtrak.com (8.11.1/8.11.1) with ESMTP id f7KNDTT25695; Mon, 20 Aug 2001 16:13:29 -0700 Message-ID: <3B819999.AA6D0907@routescience.com> X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 References: <Pine.LNX.4.10.10108201539210.27998-100000@arch.exigengroup.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-nanog@merit.edu Precedence: bulk Errors-To: owner-nanog-outgoing@merit.edu X-Loop: nanog Date: Mon, 20 Aug 2001 16:13:29 -0700 From: Sean Finn <seanf@routescience.com> Organization: Newly Organized. To: Vadim Antonov <avg@exigengroup.com> Vadim,
we recognize, and appreciate your concerns.
Two major points with regard to the PathControl product, and it's impact on the BGP environments:
1) PathControl is currently targeted toward providing optimized egress routes to multihomed enterprises. Our technology is applicable to core routing, but we certainly acknowledge the constraints in that environment are radically different ...
2) We've integrated extensive anti-flapping capabilities into the product, and in addition have user-configurable settings for maximum rate of route change.
Given a high rate of changing performance measurements, the box is capable of generating routing decisions at a high rate. Our analysis (and default settings) show that significant performance gains can be realized with a rate of change in typical deployments less than ~100 prefix changes per hour. (And maximum rates can be constrained lower than this, if desired.)
you're doing releasing just the perfect kind of sheep to graze the routing commons of which i have been speaking, for example see <http://psg.com/~randy/010809.ptomaine.pdf>, folk, it's time to get those prefix length filters in before the real /22-/24 pollution gets really crazy. randy