problems with RFC1227, RFC1238, and RFC1248
kolb@psi.com Thu, 22 August 1991 15:15 UTC
Received: from nisc.psi.net by NRI.NRI.Reston.VA.US id aa09647; 22 Aug 91 11:15 EDT
Received: by nisc.psi.net (5.61/2.1-PSINet Operations ) id AA02302; Thu, 22 Aug 91 10:48:56 -0400
Received: from psi.com by nisc.psi.net (5.61/2.1-PSINet Operations ) id AA02293; Thu, 22 Aug 91 10:48:52 -0400
Received: from localhost by psi.com (5.61/2.1-PSI/PSINet) id AA25946; Thu, 22 Aug 91 10:48:50 -0400
Message-Id: <9108221448.AA25946@psi.com>
To: snmp-wg@nisc.psi.net
Subject: problems with RFC1227, RFC1238, and RFC1248
Date: Thu, 22 Aug 1991 10:48:48 -0400
From: kolb@psi.com
Status: O
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".
type reference "DisplayString" is used but not imported (from
mib reference "RFC1213-MIB").
RFC1238-MIB (CLNP):
type reference "PhysAddress" is imported from mib reference
"RFC-1213". no such mib reference exists. the correct mib
reference is "RFC1213-MIB".
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".
chris