BGP-4 MIB
yakov@watson.ibm.com Tue, 17 January 1995 15:49 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03457;
17 Jan 95 10:49 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03453;
17 Jan 95 10:49 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa07120;
17 Jan 95 10:49 EST
Received: by interlock.ans.net id AA49565
(InterLock SMTP Gateway 1.1 for iwg-out@ans.net);
Tue, 17 Jan 1995 10:26:30 -0500
Received: by interlock.ans.net (Internal Mail Agent-2);
Tue, 17 Jan 1995 10:26:30 -0500
Message-Id: <199501171526.AA49561@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1);
Tue, 17 Jan 1995 10:26:30 -0500
Date: Tue, 17 Jan 95 10:22:19 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
To: bgp@ans.net
Subject: BGP-4 MIB
Folks, While we're advancing BGP-4 to a Draft Standard, we also need to consider advancing BGP-4 MIB to a Draft Standard. I would appreciate if the folks who implemented BGP-4 MIB would send e-mail to the current editor of BGP-4 MIB, John Chu (jychu@watson.ibm.com), describing which parts of the BGP-4 MIB are implemented and which are not. That would help us to determine whether we need to make any changes to the MIB or not. Yakov.
- BGP-4 MIB yakov