The Routing Over Large Clouds Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Feb> msg00009



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

The Hole in my proposal

  • From: Joel Halpern <jhalpern@newbridge.com>
  • Date: Fri, 3 Feb 1995 23:27:09 +0500
  • Cc: rolc@maelstrom.timeplex.com
  • X-Sun-Charset: US-ASCII

Some people have suggested that BGP has "all of the functionality needed"
for the determination of best paths.

Whether this is a true statement depends on the definitions one uses.

If the scope of the NHRP-like query is all within BGP, there are probably
techniques to use the BGP information to detect relevant routing changes,
and therefore keep the complexity down.

However, if one assumes that the scale will be large enough that aggregation
is likely to occur within the boundaries of the ATM cloud, then even the
BGP advertisements with next hop indication will have compressed out some
of the necessary information.  Thus, de-aggreagtion is needed as part of
the exit selection, not just the address resolution phase.
(I do recognize that the allowance for such aggregation brings back
 some risk of loop formation.  However, as long as we are within a single
 protocol scope, even with aggreagation, I expect safety to be achievable.)

At least we are getting some discussion of these issues.
Thank you,
Joel M. Halpern			jhalpern@newbridge.com
Newbridge Networks Inc.