Re: [Idr] IETF73 IDR WG meeting minutes

Jeffrey Haas <jhaas@pfrc.org> Wed, 26 November 2008 22:49 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A322A3A6A3A; Wed, 26 Nov 2008 14:49:50 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C6063A6A3A for <idr@core3.amsl.com>; Wed, 26 Nov 2008 14:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxmVHiFVPDmb for <idr@core3.amsl.com>; Wed, 26 Nov 2008 14:49:49 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 69DE63A69CE for <idr@ietf.org>; Wed, 26 Nov 2008 14:49:49 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id D6E92244190; Wed, 26 Nov 2008 22:49:46 +0000 (UTC)
Date: Wed, 26 Nov 2008 17:49:46 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Yakov Rekhter <yakov@juniper.net>
Message-ID: <20081126224946.GB23993@slice>
References: <200811251511.mAPFBBM94741@magenta.juniper.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <200811251511.mAPFBBM94741@magenta.juniper.net>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: idr@ietf.org
Subject: Re: [Idr] IETF73 IDR WG meeting minutes
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Tue, Nov 25, 2008 at 07:11:11AM -0800, Yakov Rekhter wrote:
> MIB (Jeff Haas)
> 
> KiraKasha (spelling)(Cisco) 
> 
> Why is there no system timer?
> 
> - Jeff: The argument to the system uptime were updated. Discontinuity 
>   could be put in the system timer.
> 
> - Also multiple instances of BGP follow the initial timer information.

This is off a little bit.

The question is why aren't the MIB discontinuity objects present on a
per-peer basis rather than on a per BGP instance basis.

My response was that peer discontinuities do not result in MIB counter
resets.  MIB counter resets only occur when there is a discontinuity in
the BGP instance.

Not said at the meeting: This does mean that for the majority of
implementations of BGP where multiple instances are done in a single
process that when you have a discontinuity event (BGP crashes and
restarts), all of the discontinuity timers will have reset.

-- Jeff
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr