Re: [Idr] Configuration objects in BGP MIB v2: Call for consenus

Curtis Villamizar <curtis@occnc.com> Wed, 09 July 2008 14:25 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 89B273A6AA3; Wed, 9 Jul 2008 07:25:46 -0700 (PDT)
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 8B62F3A68E1 for <idr@core3.amsl.com>; Wed, 9 Jul 2008 07:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.161
X-Spam-Level:
X-Spam-Status: No, score=-0.161 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.1]
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 1SaF4WMdFvRH for <idr@core3.amsl.com>; Wed, 9 Jul 2008 07:25:44 -0700 (PDT)
Received: from harbor.brookfield.occnc.com (unknown [69.37.59.172]) by core3.amsl.com (Postfix) with ESMTP id 8E84D3A68DB for <idr@ietf.org>; Wed, 9 Jul 2008 07:25:44 -0700 (PDT)
Received: from harbor.brookfield.occnc.com (harbor.brookfield.occnc.com [69.37.59.172]) by harbor.brookfield.occnc.com (8.13.6/8.13.6) with ESMTP id m69EPZiv015960; Wed, 9 Jul 2008 10:25:35 -0400 (EDT) (envelope-from curtis@harbor.brookfield.occnc.com)
Message-Id: <200807091425.m69EPZiv015960@harbor.brookfield.occnc.com>
To: Jeffrey Haas <jhaas@pfrc.org>
From: Curtis Villamizar <curtis@occnc.com>
In-reply-to: Your message of "Sun, 06 Jul 2008 21:50:00 EDT." <20080707015000.GB8722@slice>
Date: Wed, 09 Jul 2008 10:25:35 -0400
Cc: idr@ietf.org
Subject: Re: [Idr] Configuration objects in BGP MIB v2: Call for consenus
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: curtis@occnc.com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

In message <20080707015000.GB8722@slice>
Jeffrey Haas writes:
>  
> Working Group,
>  
> Back around 2005 I had a number of discussions with people who had
> provided input for the BGP MIBv2 work.  These conversations were
> specifically regarding the configuration objects in the MIB.
> draft-ietf-idr-bgp4-mibv2-05 was the last version of the MIB that
> contained the proposed configuration objects.
>  
> The results of those discussions were effectively that the configuration
> mechanisms in that MIB were too complex and had some potential issues.
> In particular:
>  
> - Modern BGP implementations tend to be more complex than the feature
>   set covered by the proposed MIBs.  It was not possible to
>   configure all session specific features from the MIB.  Since the base
>   MIB is not intended to cover all possible current and future features
>   this is problematic.
> - Configuration of peering sessions are not sufficient to fully
>   implement BGP in an operational network.  BGP fundamentally requires
>   policy for the population of the Ribs.  Policy elements and algebra
>   vary considerably among vendors.  
>  
>   Providing a general policy engine for BGP in the MIB is likely out of
>   scope of this work.
>  
> Presume that the structural issues from draft-05 may be addressed.
> Should they be addressable, do we wish to pursue including configuration
> objects in the BGP MIB?
>  
> Given the operational impact of this issue, I would appreciate it if
> this call for consensus was distributed within and without IETF.  I will
> be forwarding this to NANOG as a first step.
>  
> -- Jeff
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


Jeff,

Configuration object in the BGP MIB are useless.  It is best to remove
them.

Curtis

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