Re: Last Call: Definitions of Managed Objects for the Fourth Version

Paul Traina <pst@cisco.com> Wed, 06 December 1995 04:03 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29023; 5 Dec 95 23:03 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa29018; 5 Dec 95 23:03 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa23095; 5 Dec 95 23:03 EST
Received: by interlock.ans.net id AA22665 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Tue, 5 Dec 1995 22:52:16 -0500
Message-Id: <199512060352.AA22665@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Tue, 5 Dec 1995 22:52:16 -0500
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Tue, 5 Dec 1995 22:52:16 -0500
To: "Jeffrey T. Johnson" <jjohnson@cisco.com>
Cc: iesg@IETF.CNRI.Reston.VA.US, bgp@ans.net, ietf@CNRI.Reston.VA.US
Subject: Re: Last Call: Definitions of Managed Objects for the Fourth Version
In-Reply-To: Your message of "Wed, 29 Nov 1995 17:13:48 PST." <199511300113.AA13206@interlock.ans.net>
Date: Tue, 05 Dec 1995 19:52:10 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Traina <pst@cisco.com>

  From: "Jeffrey T. Johnson" <jjohnson@cisco.com>
  Subject: Re: Last Call: Definitions of Managed Objects for the Fourth Version
  IESG Secretary sez:
  >
  >
  >The IESG has received a request from the Inter-Domain Routing Working
  >Group to consider:
  >
  >Definitions of Managed Objects for the Fourth Version of Border Gateway
  >Protocol (BGP-4) <draft-ietf-idr-bgp4-mib-00.txt>
  >
  >for the status of Draft Standard. This is an update to RFC1657,
  >currently a Proposed Standard.
  
  I have a procedural question and a technical comment.
  
  Question: can this document proceed to Draft Standard even though
  it depends on documents that are only at Proposed Standard,
  specificially RFC 1442?  As an aside, I'm surprised to see that
  RFC 1442 was omitted from the References section of the document.

Given the current state of affairs in that area, it seems like we need to
do seems to be to eliminate the SNMPv2 boilerplate and framework entirely
and replace the MIB notification section with one that is based upon native
SNMPv1 identifiers.  All of this is basicly mechanical translation of text.

Jeff, would you be willing to take a whack at the draft this week
or next week with me?

Yakov, do you have access to the nroff source from John?

Paul