[Idr] BGP MIB representation of RIBs (Re: [MIB-DOCTORS] BGP MIBv2 discontinuity objects)

john heasley <heas@shrubbery.net> Thu, 17 July 2008 00:55 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 [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 63D123A68FD; Wed, 16 Jul 2008 17:55:07 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 233FE3A68D8; Wed, 16 Jul 2008 17:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id tmVpjjiCDsuq; Wed, 16 Jul 2008 17:55:05 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net []) by core3.amsl.com (Postfix) with ESMTP id 752853A68FD; Wed, 16 Jul 2008 17:55:05 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id CE4D0108699; Thu, 17 Jul 2008 00:55:35 +0000 (UTC)
Date: Wed, 16 Jul 2008 17:55:35 -0700
From: john heasley <heas@shrubbery.net>
To: Jeffrey Haas <jhaas@pfrc.org>
Message-ID: <20080717005535.GA4195@shrubbery.net>
Mime-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/
Cc: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, idr@ietf.org
Subject: [Idr] BGP MIB representation of RIBs (Re: [MIB-DOCTORS] BGP MIBv2 discontinuity objects)
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

I've not followed the BGP MIBv2 thread closely, but I believe the heat is
related to BGP RIB representation and this is something that I've been
wanting to ask about.

Specifically, we see no value that this kind of data, along with route
attributes, be in a MIB.  Rather it seems to slow standardization and
implementation.  For example, we've been wanting peer in-RIB sums for
some time.

Can't the RIB be eliminated?  If not, can it be split into a separate and
optional MIB?
Idr mailing list