BGP 4 MIB to a Draft Standard
yakov@watson.ibm.com Fri, 03 February 1995 18:02 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06258;
3 Feb 95 13:02 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06254;
3 Feb 95 13:02 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa15568;
3 Feb 95 13:02 EST
Received: by interlock.ans.net id AA41490
(InterLock SMTP Gateway 1.1 for iwg-out@ans.net);
Fri, 3 Feb 1995 12:49:48 -0500
Received: by interlock.ans.net (Internal Mail Agent-2);
Fri, 3 Feb 1995 12:49:48 -0500
Message-Id: <199502031749.AA19726@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1);
Fri, 3 Feb 1995 12:49:48 -0500
Date: Fri, 3 Feb 95 12:49:45 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
To: bgp@ans.net
Subject: BGP 4 MIB to a Draft Standard
Folks, We need to make progress on moving BGP-4 MIB to a Draft Standard. Recent e-mail exchange showed that there are some objections to moving the current MIB "as is" to a Draft Standard. However, there are also objections to changing the current MIB. Since there is "working code" already, the only thing that is missing is "rough consensus". There are two choices for getting it: (a) via e-mail (b) at the next WG meeting Choice (b) is a fallback plan if (a) wouldn't work. Comments ? Yakov
- BGP 4 MIB to a Draft Standard yakov
- Re: BGP 4 MIB to a Draft Standard Paul Traina
- Re: BGP 4 MIB to a Draft Standard Dimitry Haskin