Protocol Action: Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 to Draft Standard

IESG Secretary <iesg-secretary@CNRI.Reston.VA.US> Sat, 11 March 1995 15:58 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa05716; 11 Mar 95 10:58 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa05712; 11 Mar 95 10:58 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa06551; 11 Mar 95 10:58 EST
Received: by interlock.ans.net id AA25087 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Sat, 11 Mar 1995 10:37:20 -0500
Message-Id: <199503111537.AA25087@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Sat, 11 Mar 1995 10:37:20 -0500
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Sat, 11 Mar 1995 10:37:20 -0500
To: IETF-Announce: ;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: bgp@ans.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Protocol Action: Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 to Draft Standard
Date: Sat, 11 Mar 95 10:30:43 -0500
X-Orig-Sender: scoya@CNRI.Reston.VA.US

  The IESG has approved the Internet-Draft "Definitions of Managed Objects
  for the Fourth Version of the Border Gateway Protocol (BGP-4) using
  SMIv2" <RFC1657> as a Draft Standard. This document is the product of the
  Inter-Domain Routing Working Group. The IESG contact person is Joel
  Halpern.


Technical Summary

  This MIB defines the management objects for managing an instance of
  the BGP-4 routing protocol.

Working Group Summary

  After reviewing the situation and discussing possible changes, the
  working group concluded that the existing MIB, defined when the protocol
  was standardized at the Proposed level, is still correct.


Protocol Quality

  This is a sound and implementable MIB to manage a BGP-4 protocol entity.
  It has been reviewed by Joel M. Halpern, the Routing Area Director.