distance vector algorithms

Tony Li <tli@cisco.com> Thu, 21 May 1992 10:53 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa00464; 21 May 92 6:53 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa10291; 21 May 92 6:59 EDT
Received: from PIZZA.BBN.COM by NRI.Reston.VA.US id aa10287; 21 May 92 6:59 EDT
Received: from pizza by PIZZA.BBN.COM id aa28484; 20 May 92 14:05 EDT
Received: from BBN.COM by PIZZA.BBN.COM id aa28478; 20 May 92 14:03 EDT
Received: from lager.cisco.com by BBN.COM id aa10896; 20 May 92 14:06 EDT
Received: by lager.cisco.com; Wed, 20 May 92 11:05:55 -0700
Date: Wed, 20 May 92 11:05:55 -0700
From: Tony Li <tli@cisco.com>
Message-Id: <9205201805.AA10268@lager.cisco.com>
To: msteenst@bbn.com
Cc: idpr-wg@bbn.com
In-Reply-To: Martha Steenstrup's message of Wed, 20 May 92 08:08:04 -0400 <9205201250.AA25143@jerico.usc.edu>
Subject: distance vector algorithms

Hi Martha,

   Using path vector algorithms for policy-based routing and applying
   route selection criteria based on source and transit policies means
   that gateways executing these algorithms do not necessarily accept the
   most recent routes that they learn about.  They judge each route
   according to its consistency with their policies.  That is exactly as
   it should be.  However, such route selection also means the possibility
   of the type of looping I described in the previous messages.  Hence,
   path vector algorithms for policy-based routing should have increased
   loop detection capabilities, to reduce the probabilities of such loops.
   Even so, I do not believe that these algorithms can ever eliminate this
   type of looping problem.

The mechanism that I described in my previous message completely
eliminates looping problems.  It is not an addition, but is already
present in BGP.

Tony