The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1996-Jan> msg00247



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

draft-ietf-ipatm-framework-doc-06.txt

  • From: Yakov Rekhter <yakov@cisco.com>
  • Date: Mon, 29 Jan 96 10:24:14 PST
  • Cc: Yakov Rekhter <yakov@cisco.com>, jhalpern@us.newbridge.com (Joel Halpern), ip-atm@hplb.hpl.hp.com

Curtis,

> You are not questioning the technical accuracy of these examples at
> all, here or below.  Below you are simply stating what the solution
> is.  The solution in one case is to make sure the PV path information
> is not lost (the currently favored solution is to run BGP in addition
> to NHRP) and in the other two cases make sure DV metrics are not lost
> (the currently favored solution is to run an IGP in addition to NHRP).

I question the relevance of these examples. Truncating AS_PATH
in BGP, or dropping metric in DV is *well-known* to produce
forwarding loops by itself, with neither NHRP nor ATM involved. 

So, why the examples that illustrate how truncating AS_PATH
in BGP or dropping metric in DV could result in forwarding loops
should be included in the IP ATM Framework in the section that
talks about NHRP ? 

Yakov.