Ballot: 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> Thu, 02 March 1995 17:32 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08679; 2 Mar 95 12:32 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08674; 2 Mar 95 12:32 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09400; 2 Mar 95 12:32 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08663; 2 Mar 95 12:32 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08659; 2 Mar 95 12:32 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa09390; 2 Mar 95 12:32 EST
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa08646; 2 Mar 95 12:31 EST
To: Internet Engineering Steering Group <iesg@CNRI.Reston.VA.US>
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Reply-To: IESG Secretary <iesg-secretary@CNRI.Reston.VA.US>
Subject: Ballot: Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2 to Draft Standard
Date: Thu, 02 Mar 1995 12:31:46 -0500
X-Orig-Sender: scoya@CNRI.Reston.VA.US
Message-ID: <9503021231.aa08646@IETF.CNRI.Reston.VA.US>
Last Call to expire on: 02/27/1994 Please return the full line with the vote. Yes No-Objection Discuss * Abstain Scott Bradner [ ] [ ] [ ] [ ] Joel Halpern [ X ] [ ] [ ] [ ] Erik Huizer [ ] [ ] [ ] [ ] John Klensin [ ] [ ] [ ] [ ] Stev Knowles [ ] [ ] [ ] [ ] Allison Mankin [ ] [ ] [ ] [ ] Paul Mockapetris [ ] [ ] [ ] [ ] Mike O'Dell [ ] [ ] [ ] [ ] Joyce K. Reynolds [ ] [ ] [ ] [ ] Marshall T. Rose [ ] [ ] [ ] [ ] Jeff Schiller [ ] [ ] [ ] [ ] Claudio Topolcic [ ] [ ] [ ] [ ] Yes => I have read the spec and know it is good stuff. No Obj => I am familiar with the protocol and believe it to be OK. Note: The ballot contains analysis from the AD which may be adequate information to vote positively. Discuss => There is something fishy that may need clarification or modification. May be considered a "no" vote. Abstain => I am not familiar with the spec, have no interest/expertise in the subject or otherwise feel obliged to skip the voting. 2/3 (8) Yes or No-Objection votes needed to pass. * Indicate reason if "Discuss". To: IETF-Announce:; Dcc: ******* Cc: RFC Editor <rfc-editor@isi.edu> Cc: Internet Architecture Board <iab@isi.edu> Cc: bgp@ans.net 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 ------------- 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.