Re: A proposed change to BGP-4 MIB bgpPeerTable INDEX clause

Robert Snyder <snyder@cisco.com> Thu, 19 January 1995 19:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07605; 19 Jan 95 14:47 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07601; 19 Jan 95 14:47 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa12702; 19 Jan 95 14:47 EST
Received: by interlock.ans.net id AA21291 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Thu, 19 Jan 1995 14:35:02 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Thu, 19 Jan 1995 14:35:02 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Thu, 19 Jan 1995 14:35:02 -0500
Message-Id: <199501191934.LAA25297@hubbub.cisco.com>
To: bgp@ans.net
Cc: "John Y. Chu" <jychu@watson.ibm.com>, pst@cisco.com
Subject: Re: A proposed change to BGP-4 MIB bgpPeerTable INDEX clause
In-Reply-To: Your message of "Thu, 19 Jan 95 11:24:51 PST." <199501191924.LAA18227@feta.cisco.com>
Date: Thu, 19 Jan 95 11:34:57 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Robert Snyder <snyder@cisco.com>

The proposal is illegal.

You can not add an Index to an existing table.

The only way you could do this is to deprecate the existing table and
create a new one.

>   From: jychu@watson.ibm.com (John Y. Chu)
>   Subject: A proposed change to BGP-4 MIB bgpPeerTable INDEX clause
>   
>   Folks,
>   A change to the BGP-4 MIB definition has been proposed.  The change
>   is to use an existing field (bgpPeerLocalAddr) as the secondary index
>   of bgpPeerTable, as shown:
>   
>   
>                   bgpPeerEntry OBJECT-TYPE
>                       SYNTAX     BgpPeerEntry
>                       MAX-ACCESS not-accessible
>                       STATUS     current
>                       DESCRIPTION
>                               "Entry containing information about the
>                               connection with a BGP peer."
>                       INDEX { bgpPeerRemoteAddr,
>   +                           bgpPeerLocalAddr  }
>                       ::= { bgpPeerTable 1 }
>   
>   
>   The BGP-4 protocol spec allows multiple BGP sessions to be established
>   with a single peer, and each session is distinguished by its local IP
>   address.  Thus the change.
>   
>   Comment?
>