Re: bgp4-17 Cease subcode

Russ White <ruwhite@cisco.com> Tue, 15 January 2002 20:04 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 PAA07021 for <idr-archive@nic.merit.edu>; Tue, 15 Jan 2002 15:04:28 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id DDA0791267; Tue, 15 Jan 2002 15:01:48 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id AD71991268; Tue, 15 Jan 2002 15:01:48 -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 878A791267 for <idr@trapdoor.merit.edu>; Tue, 15 Jan 2002 15:01:42 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 6A5465DDCB; Tue, 15 Jan 2002 15:01:42 -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 F200C5DDCA for <idr@merit.edu>; Tue, 15 Jan 2002 15:01:41 -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 PAA05092; Tue, 15 Jan 2002 15:01:38 -0500 (EST)
Date: Tue, 15 Jan 2002 15:01:38 -0500
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: Susan Hares <skh@nexthop.com>
Cc: Alex Zinin <azinin@nexsi.com>, Eric Gray <eric.gray@sandburst.com>, Inter-Domain Routing Mailing List <idr@merit.edu>
Subject: Re: bgp4-17 Cease subcode
In-Reply-To: <5.0.0.25.0.20020115144930.04a32a00@mail.nexthop.com>
Message-ID: <Pine.GSO.4.21.0201151500510.20905-100000@ruwhite-u10.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-idr@merit.edu
Precedence: bulk

So, then it sounds like the way we should approach this (the
idlehold state in the fsm) is to think about it seperately from
the draft 17 issue (?).

Russ

On Tue, 15 Jan 2002, Susan Hares wrote:

> 
> Alex:
> 
> I know you have been active on the mailing list.
> And you didn't read it before the last call on the FSM.
> And this question was asked on the list because I
> wondered about it.
> 
> ;-)... <giggle on>  --- I guess not even great people are
> perfect.  <giggle off>
> 
> OK, now I've got 2 more against (4 total).  And 15-20 votes
> for it inside the draft.
> 
> I'm sure your vote is a bit more specific.  :-)...
> 
> Is the issue you want to pull exponential out of the draft?
> This is a change to the BGP specification.  This draft
> is about corrections not changes in functionality.
> 
> What do we do?
> 
> Sue Hares
> 
> 
> 
> At 10:30 AM 1/15/2002 -0800, Alex Zinin wrote:
> 
> >Russ, Eric,
> >
> >  I tend to agree here...
> >  I'm currently reviewing the FSM and the impression I'm
> >  getting is that we can go without the IdleHold state
> >  and say that implementations may/should use some local mechanisms
> >  to hold BGP sessions in the *Idle* state to avoid excessive
> >  session flapping. I think this will be simpler and will
> >  match current implementations better...
> >
> >--
> >Alex Zinin
> >
> >Tuesday, January 15, 2002, 7:21:06 AM, Russ White wrote:
> >
> >
> > > 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
> 
> 

_____________________________
riw@cisco.com <>< Grace Alone