BGP-4 MIB to a Draft Standard
yakov@watson.ibm.com Fri, 03 February 1995 18:36 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id ab07305;
3 Feb 95 13:36 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa07300;
3 Feb 95 13:36 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa16333;
3 Feb 95 13:36 EST
Received: by interlock.ans.net id AA41094
(InterLock SMTP Gateway 1.1 for iwg-out@ans.net);
Fri, 3 Feb 1995 13:27:00 -0500
Received: by interlock.ans.net (Internal Mail Agent-2);
Fri, 3 Feb 1995 13:27:00 -0500
Message-Id: <199502031826.AA30841@interlock.ans.net>
Received: by interlock.ans.net (Internal Mail Agent-1);
Fri, 3 Feb 1995 13:27:00 -0500
Date: Fri, 3 Feb 95 13:26:51 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: yakov@watson.ibm.com
To: bgp@ans.net
Cc: jhalpern@newbridge.com
Subject: BGP-4 MIB to a Draft Standard
Folks, Based on the messages I received so far there seems to be a rough consensus on keeping BGP-4 MIB as is. So, the WG would like to ask the IESG to advance BGP-4 MIB to a Draft Standard. The text is RFC1657. Yakov