Re: [Idr] [sidr] BGP4 MIB module

heasley <heas@shrubbery.net> Wed, 21 March 2012 17:38 UTC

Return-Path: <heas@shrubbery.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E536B21E801A; Wed, 21 Mar 2012 10:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bm3DwxCg1rLm; Wed, 21 Mar 2012 10:38:36 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DFE21F8569; Wed, 21 Mar 2012 10:38:24 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id A4BDC88B70; Wed, 21 Mar 2012 17:38:23 +0000 (UTC)
Date: Wed, 21 Mar 2012 17:38:23 +0000
From: heasley <heas@shrubbery.net>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
Message-ID: <20120321173823.GB75903@shrubbery.net>
References: <0E2C44659B4E4C22A58EDF7E0A834092@BertLaptop> <A0244F66-9C6D-4AC1-A0B9-6BAD839D0DE9@juniper.net> <4F5FB239.7090009@bwijnen.net> <4F68A20F.5000506@bwijnen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4F68A20F.5000506@bwijnen.net>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Jeffrey Haas <jhaas@juniper.net>, idr@IETF.ORG, sidr wg list <sidr@ietf.org>
Subject: Re: [Idr] [sidr] BGP4 MIB module
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 21 Mar 2012 17:38:37 -0000

Tue, Mar 20, 2012 at 04:28:15PM +0100, Bert Wijnen (IETF):
> So I had been in discussion with Jeff in order to see
> if we could get the BGP4-mibv2 module in good shape.
> 
> Below is out discussion.
> 
> Those who are interested in this MIB module at all
> may want to take a look to make sure they agree with
> the changes being proposed.
> 
> The most modules we're discussion are:
> 
> - drafts/draft-ietf-idr-bgp4-mibv2-13.txt
> - drafts/draft-ietf-idr-bgp4-mibv2-tc-mib-03.txt
> 
> In fact I had below discussion on bgp4-mibv2-12.txt,
> which resulted in revision 13.

I'm disappointed in the speed at which this draft has progressed.  I do
understand that mibs are often partially gated for/by trial implementation
(or so I've been told), but I have the impression its pace is wholly due to
the complexity of the proposed mib.  I also feel that there is a fair
amount of fluff that we find unnecessary for network management and would
be better suited to a separate mib; the RIBs, for example.  bgp4-mibv2
("lite"), bgp4-ribs, etc; or some approach that would allow the necessities
of peer state, nlri counts, and the like to progress without the fluff and
thus be more timely.

As such, I am unsure why its been brought to the sidr list, but I am hoping
that no attempt will be made to add SIDR-related stuff to this mib and
further delay adoption.