[Idr] Factoring the bgpPeerAfTable in BGP MIBv2

Jeffrey Haas <jhaas@pfrc.org> Mon, 07 July 2008 02:54 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 782D43A6A0D; Sun, 6 Jul 2008 19:54:48 -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 85BBF3A6A0D; Sun, 6 Jul 2008 19:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[AWL=0.465, 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 6TFfdvLKDj46; Sun, 6 Jul 2008 19:54:45 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id C19C43A6947; Sun, 6 Jul 2008 19:54:45 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 05A63244180; Mon, 7 Jul 2008 02:54:51 +0000 (UTC)
Date: Sun, 6 Jul 2008 22:54:50 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Joan Cucchiara <jcucchiara@mindspring.com>
Message-ID: <20080707025450.GB10534@slice>
References: <06f701c88b5b$22622000$6601a8c0@JoanPC> <20080503223750.GG23560@scc.mi.org> <00f801c8b542$2d1a0c90$6601a8c0@JoanPC> <20080611022929.GA633@slice> <012201c8de39$63ca17b0$6601a8c0@JoanPC>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <012201c8de39$63ca17b0$6601a8c0@JoanPC>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: "Dan Romascanu \(E-mail\)" <dromasca@avaya.com>, David Ward <dward@cisco.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, idr@ietf.org
Subject: [Idr] Factoring the bgpPeerAfTable in BGP MIBv2
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

Joan,

Forking this from the main thread for tracking:

On Fri, Jul 04, 2008 at 08:52:24PM -0400, Joan Cucchiara wrote:
> What I was thinking actually was to not separate Timer objects into
> specific "timer" tables, but to group these with their respective 
> categories
> (i.e. bgp manager instance, bgp peer, session).
>
> However, I say this assuming that there will be more separation than
> currently exists. For example, if the bgpPeerAfTable
> is observed, you have comments, Local, Remote, Session Status in one table.
> The Local refers to (I think?) what you call the "bgp manager instance",
> remote is the "peer" and session status is the "session".
> Timers could also be grouped in these categories.
>
> Taking this all a step farther, would suggest to create a
> Local (bgp manager instance table) and a remote table (which may or may not
> also include session objects).

I think you may be having a small amount of confusion regarding the
objects that constitute the indices of the peer table.

A BGP peer session is defined by a TCP connection between two BGP
speakers.  It is possible for a BGP speaker to have multiple parallel
BGP peering sessions with the same remote BGP speaker so long as the TCP
tuple is different.  See RFC 4271, Section 6.8 for the definition of a
session collision which occurs when two parallel sessions occur with the
same TCP IP address endpoints.

bgpPeerAfInstance serves a somewhat similar purpose as the ENTITY-MIB to
permit multiple BGP sessions.  Since it possible, especially in certain
VPN scenarios, for a given router to permit multiple peering sessions
via differing IP instances, this object was necessary to permit a single
MIB the capability to mange those instances where an end-point might be
the same.

Thus the bgpPeerAfTable's indices are somewhat similar to TcpConnEntry
and should be kept together.  The bgpPeerAfInstance should similarly be
kept with them.

The objects under "Session status" could be factored into an AUGMENTS
table if this will address your concerns.  However, this is the most
factoring I would suggest here.

Overall, I'm not sure what the structural win for this would be.  While
it gains some "purity" of table contents, the similarity to the previous
bgpPeerTable was intentional as an aid to implementors who have to
implement bgpPeerTable.


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