routing loops
Martha Steenstrup <msteenst@bbn.com> Fri, 22 May 1992 22:33 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa03430; 22 May 92 18:33 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa19776; 22 May 92 18:39 EDT
Received: from PIZZA.BBN.COM by NRI.Reston.VA.US id aa19770; 22 May 92 18:39 EDT
Received: from pizza by PIZZA.BBN.COM id aa07563; 22 May 92 18:24 EDT
To: tli@cisco.com
cc: idpr-wg@bbn.com
Subject: routing loops
Date: Fri, 22 May 1992 18:22:40 -0400
From: Martha Steenstrup <msteenst@bbn.com>
Message-ID: <9205221839.aa19770@NRI.Reston.VA.US>
Hi Tony, I've just reread the BGP-3 specification. The general looping problem I am talking about is addressed in a more specific form in section 10, Detection of Inter-AS Policy Contradictions. The last paragraph of that section says:"... the protocol itself does not provide any mechanism for suppressing the route oscillation that may result from these unsatisfiable policies". I don't mean to pick on BGP. As I've already said, the architecture document discusses general distance vector algorithms for policy routing. It's just that I don't see how you can say that this looping problem is not a problem in BGP, unless the implementation differs from the protocol specification. m
- routing loops Martha Steenstrup
- routing loops Martha Steenstrup
- routing loops Martha Steenstrup
- routing loops Tony Li