Re: problems with RFC1227, RFC1238, and RFC1248
Keith McCloghrie <kzm@hls.com> Thu, 22 August 1991 18:09 UTC
Received: from nisc.psi.net by NRI.NRI.Reston.VA.US id aa14577; 22 Aug 91 14:09 EDT
Received: by nisc.psi.net (5.61/2.1-PSINet Operations ) id AA05800; Thu, 22 Aug 91 13:50:35 -0400
Received: from LANSLIDE.HLS.COM by nisc.psi.net (5.61/2.1-PSINet Operations ) id AA05795; Thu, 22 Aug 91 13:50:31 -0400
Received: from nms.netman (nms.hls.com) by lanslide.hls.com (4.1/SMI-4.0) id AA20740; Thu, 22 Aug 91 10:51:22 PDT
Received: by nms.netman (4.1/SMI-4.1) id AA16546; Thu, 22 Aug 91 10:51:31 PDT
From: Keith McCloghrie <kzm@hls.com>
Message-Id: <9108221751.AA16546@nms.netman>
Subject: Re: problems with RFC1227, RFC1238, and RFC1248
To: kolb@psi.com
Date: Thu, 22 Aug 1991 10:51:30 -0700
Cc: snmp-wg@nisc.psi.net
In-Reply-To: <9108221448.AA25946@psi.com>; from "kolb@psi.com" at Aug 22, 91 10:48 am
Organization: Hughes LAN Systems
X-Mailer: ELM [version 2.2 PL0]
Status: O
Chris,
> RFC1227-MIB (SMUX):
>
> macro reference "OBJECT-TYPE" is imported from mib reference
> "RFC1212". no such mib reference exists. the correct mib
> is reference "RFC-1212".
Actually, RFC 1212 defines neither "RFC1212" nor "RFC-1212".
So, "correctness" to this level/depth is not achievable by any
of today's MIBs.
> RFC1248-MIB (OSPF):
>
> value reference "ospf" is defined in terms of the value
> reference "standard-mib", which neither imported into nor
> defined in mib reference "RFC1248-MIB".
>
> ospf OBJECT IDENTIFIER ::= { standard-mib 13 }
>
> "standard-mib", i assume, really should be "mib-2", which
> will need to be imported from mib reference "RFC1213-MIB".
RFC 1248 has been re-issued as RFC1252, correcting this problem.
Keith.