Re: bgp4-17 Cease subcode

Randy Bush <randy@psg.com> Thu, 17 January 2002 02:44 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 VAA24619 for <idr-archive@nic.merit.edu>; Wed, 16 Jan 2002 21:44:17 -0500 (EST)
Received: by trapdoor.merit.edu (Postfix) id 9B9F591246; Wed, 16 Jan 2002 21:43:37 -0500 (EST)
Delivered-To: idr-outgoing@trapdoor.merit.edu
Received: by trapdoor.merit.edu (Postfix, from userid 56) id 675CB912C4; Wed, 16 Jan 2002 21:43:37 -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 7BB7591246 for <idr@trapdoor.merit.edu>; Wed, 16 Jan 2002 21:43:36 -0500 (EST)
Received: by segue.merit.edu (Postfix) id 03BB95DDA3; Wed, 16 Jan 2002 21:43:36 -0500 (EST)
Delivered-To: idr@merit.edu
Received: from roam.psg.com (unknown [147.28.4.2]) by segue.merit.edu (Postfix) with ESMTP id 5B4935DD8E for <idr@merit.edu>; Wed, 16 Jan 2002 21:43:35 -0500 (EST)
Received: from randy by roam.psg.com with local (Exim 3.33 #1) id 16R19U-0005pQ-00; Wed, 16 Jan 2002 17:15:36 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Alex Zinin <azinin@nexsi.com>
Cc: idr@merit.edu
Subject: Re: bgp4-17 Cease subcode
References: <20020115140711.GA23937@opentransit.net> <20020114123700.C7761@nexthop.com> <200201141750.g0EHo3634958@merlot.juniper.net> <5.0.0.25.0.20020116090028.039d2fa8@mail.nexthop.com> <114185201786.20020116111047@nexsi.com>
Message-Id: <E16R19U-0005pQ-00@roam.psg.com>
Date: Wed, 16 Jan 2002 17:15:36 -0800
Sender: owner-idr@merit.edu
Precedence: bulk

>  Introduction of the IdleHold does change the FSM,
>  and I thought we wanted the spec to reflect the current
>  running code as much as possible.
>  
>  I agree with Russ and Ishi---the new state does not
>  seem to be necessary, instead it could be as easy
>  as holding the session in Idle and giving clue on
>  how to make the delay exponential. I don't think
>  there's an interoperability issue if people decide
>  to keep the session in Idle using different internal
>  mechanisms.

if the introduction of idlehold makes life clearer for implementors, yet
it changes the fsm but not in incompatible ways (i.e. old would interop
with new and wire looks the same, as jeff asserts.  maybe sufficient
sushi could convince an area director not to ding the progress status of
the document.

randy