[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: Malloc MIB

Mmmm... I wonder why this happens more than it should.

- I guess one reason is that we've not been checking that
  too rigurously
- Another is that it is not always clear since the 
  reference does nto exist.
  Several years back I saw things like:

     IMPORT
     SnmpAdminString 
     FROM   SNMp-FRAMEWORK-MIB  -- RFC xxxx [RFCxxxx]

  But some one objected to that... and since then I do not
  see it much (if at all). If we started to recommend that
  approach, then the normative references would more easily
  show up.

Comments?

Bert 

-----Original Message-----
From: C. M. Heard [mailto:heard@pobox.com]
Sent: woensdag 29 januari 2003 6:50
To: Dave Thaler
Cc: Wijnen, Bert (Bert); Allison Mankin (E-mail)
Subject: RE: Malloc MIB

.. snip ..

All the ones we brought up before, yes (and may I say that it looks
like you put quite a lot of thought into the security considerations
section).  Unfortunately there is something I did not notice before
(because it was not at that time on my mib reviewer's checklist):
the MALLOC-MIB imports from INET-ADDRESS-MIB, IPMROUTE-STD-MIB,
and SNMP-FRAMEWORK-MIB, so there should be normative references
to RFCs 3291, 2932, and 3411 respectively.  At least I think we
agreed to do that on the MIB Doctor's mailing list.  Mea culpa.

//cmh