Re: bgp4-17 Cease subcode
Russ White <ruwhite@cisco.com> Tue, 15 January 2002 15:21 UTC
Received: from trapdoor.merit.edu (postfix@trapdoor.merit.edu [198.108.1.26]) by nic.merit.edu (8.9.3/8.9.1) with ESMTP id KAA25212 for <idr-archive@nic.merit.edu>; Tue, 15 Jan 2002 10:21:48 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id D29DA91254; Tue, 15 Jan 2002 10:21:10 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 9E6A891256; Tue, 15 Jan 2002 10:21:10 -0500 (EST)
Delivered-To: idr@trapdoor.merit.edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41]) by trapdoor.merit.edu (Postfix) with ESMTP id C786591254 for <idr@trapdoor.merit.edu>; Tue, 15 Jan 2002 10:21:08 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 958835DDC0; Tue, 15 Jan 2002 10:21:08 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from cisco.com (uzura.cisco.com [64.102.17.77]) by segue.merit.edu (Postfix) with ESMTP id 1F3F45DDDA for <idr@merit.edu>; Tue, 15 Jan 2002 10:21:08 -0500 (EST)
Received: from ruwhite-u10.cisco.com (ruwhite-u10.cisco.com [64.102.48.251]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA00713; Tue, 15 Jan 2002 10:21:06 -0500 (EST)
Date: Tue, 15 Jan 2002 10:21:06 -0500
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: Eric Gray <eric.gray@sandburst.com>
Cc: Inter-Domain Routing Mailing List <idr@merit.edu>
Subject: Re: bgp4-17 Cease subcode
In-Reply-To: <3C44476C.E0FFA783@sandburst.com>
Message-ID: <Pine.GSO.4.21.0201151019240.20772-100000@ruwhite-u10.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-idr@merit.edu
Precedence: bulk
Something like: "BGP implementations can/should/must (?) implement some method to prevent continuous flapping of peering sessions at a high rate," and then a footbote explaining that an exponential backoff is one such possible method? Russ On Tue, 15 Jan 2002, Eric Gray wrote: > Russ, > > Very good point. However, how would you represent "do some > private magic here" in an FSM? That may make it the dreaded ISM. > Perhaps it might be sufficient to remove this from the FSM and > add a footnote (possibly mentioning an exponential back-off as an > example?). > > You wrote: > > > Well, I just took it as 'do people do this?' I agree that it > > won't cause interop problems either way--it's actually something > > that's implementation local, so I'm not certain why the > > exponential backoff would be in the fsm (?). There are, in other > > words, other ways I could imagine handling this problem that > > wouldn't effect interoperability as well.... > > > > :-) > > > > Russ > > > > On Tue, 15 Jan 2002, Eric Gray wrote: > > > > > Russ, > > > > > > I don't think that NAKs are in order on this question - even from the > > > 1500 pound dragon. :-) > > > > > > The fact that anyone's implementation doesn't do X is important only > > > if not doing X causes interoperability problems with implementations > > > that do X. That is not the case here, I believe... > > > > > > You wrote: > > > > > > > > > On Mon, Jan 14, 2002 at 09:28:53AM -0800, Yakov Rekhter wrote: > > > > > > > Please remember that the goal of the draft is to document > > > > > > > what is *currently* implemented and deployed, *not* what > > > > > > > *could* be implemented and deployed. > > > > > > > > > > > > Is the expoential backoff in the FSM in current implementations? > > > > > > > > > > I guess we are going to find this out as part of the > > > > > implementation report. And if it is not in (at least two) > > > > > current implementations, we'll take it out of the text. > > > > > > > > Cisco doesn't do this.... > > > > > > > > :-) > > > > > > > > Russ > > > > > > > > _____________________________ > > > > riw@cisco.com <>< Grace Alone > > > > > > -- > > > Eric Gray (mailto:eric.gray@sandburst.com) > > > http://www.mindspring.com/~ewgray > > > > > > > > > > > > > _____________________________ > > riw@cisco.com <>< Grace Alone > > -- > Eric Gray (mailto:eric.gray@sandburst.com) > http://www.mindspring.com/~ewgray > > > _____________________________ riw@cisco.com <>< Grace Alone
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Susan Hares
- Re: Comments on FSM Susan Hares
- Re: bgp4-17 Cease subcode Vincent Gillet
- Re: bgp4-17 Cease subcode Vincent Gillet
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: Comments on FSM Jeffrey Haas
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Kunihiro Ishiguro
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode andrewl
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Randy Bush
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: Comments on FSM Alex Zinin
- Re: bgp4-17 Cease subcode Randy Bush
- Re: Comments on FSM Kunihiro Ishiguro
- Comments on FSM Alex Zinin
- Re: bgp4-17 Cease subcode Enke Chen
- Re: bgp4-17 Cease subcode Greg Hankins
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Kunihiro Ishiguro
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Kunihiro Ishiguro
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Jeffrey Haas
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Alex Zinin
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Eric Gray
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Eric Gray
- Re: bgp4-17 Cease subcode Jeff Pickering
- Re: bgp4-17 Cease subcode Vincent Gillet
- Re: bgp4-17 Cease subcode Russ White
- Re: bgp4-17 Cease subcode Susan Hares
- Re: bgp4-17 Cease subcode Yakov Rekhter
- Re: bgp4-17 Cease subcode Jeffrey Haas
- Re: bgp4-17 Cease subcode Yakov Rekhter
- Re: bgp4-17 Cease subcode Tom Petch
- Re: bgp4-17 Cease subcode Yakov Rekhter
- bgp4-17 Cease subcode Tom Petch
- Re: processing order of reach/unreach in rfc2858b… Jeffrey Haas
- Re: processing order of reach/unreach in rfc2858b… Enke Chen