The IP over ATM Mailing List Archive by date

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



[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: Tue, 30 Jan 96 13:13:39 PST
  • Cc: Yakov Rekhter <yakov@cisco.com>, jhalpern@us.newbridge.com (Joel Halpern), ip-atm@hplb.hpl.hp.com

Curtis,

> This example is relevant to NHRP because it details the consequences
> of the misuse of NHRP.  Such misuse has been discussed and advocated
> by numerous people in the ROLC and IPATM WGs in the past, and
> indications are NHRP continues to be misrepresented by industry
> marketing and sales people who are not closely following the IPATM WG.
> 
> I think this is sufficient reason to 1) leave the example in the
> document, 2) continue to reference the possibility of routing loops in
> the context of misuse of NHRP.

If you'd like to keep the example, then please add the following text:

   It is well-known that truncating AS_PATH information in BGP or losing
   metric information in Distance Vector protocols (e.g., RIP) could
   result in persistent forwarding loops. These loops could occur
   without ATM and without NHRP. The following example illustrates
   how the use of NHRP in the environment where forwarding loops could
   exist even without NHRP (due to either truncated AS_PATH information
   or loss of metric information) could produce forwarding loops.
   
as this text clarifies the source of looping.

Yakov.