Re: bgp4-17 Cease subcode

Eric Gray <eric.gray@sandburst.com> Tue, 15 January 2002 15:17 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 KAA25076 for <idr-archive@nic.merit.edu>; Tue, 15 Jan 2002 10:17:33 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 3E5D591255; Tue, 15 Jan 2002 10:14:58 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id D9E2C9125C; Tue, 15 Jan 2002 10:14:57 -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 325D791255 for <idr@trapdoor.merit.edu>; Tue, 15 Jan 2002 10:14:54 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 0EF5E5DDA0; Tue, 15 Jan 2002 10:14:54 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from sandmail.sandburst.com (sandmail.sandburst.com [216.57.132.42]) by segue.merit.edu (Postfix) with ESMTP id BFB415DD96 for <idr@merit.edu>; Tue, 15 Jan 2002 10:14:53 -0500 (EST)
Message-ID: <3C44476C.E0FFA783@sandburst.com>
Date: Tue, 15 Jan 2002 10:14:52 -0500
From: Eric Gray <eric.gray@sandburst.com>
MIME-Version: 1.0
To: Russ White <riw@cisco.com>
Cc: Inter-Domain Routing Mailing List <idr@merit.edu>
Subject: Re: bgp4-17 Cease subcode
References: <Pine.GSO.4.21.0201151005270.20745-100000@ruwhite-u10.cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-idr@merit.edu
Precedence: bulk

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