For years, I've crawled over Internet-Drafts and RFCs to find things that look like MIB modules, to construct my set of pages at http://www.icir.org/fenner/mibs/ . It occurred to me, after seeing that some of the MIBs that Net-SNMP distributes are out of date, that this info could be relatively easily used to construct the rfclist file that Net-SNMP uses.
I wrote a script that generates an rfclist from my indexes, with the ability to exclude modules via regexp (e.g., IANA.* and RFC.*) and the ability to augment the automatically generated index with manual information (e.g., including a couple of RFC* modules anyway). The rfclist that my stuff generates is at http://electricrain.com/fenner/tmp/rfclist and the diff from the 5.4 rfclist is at http://electricrain.com/fenner/tmp/rfclist-diff.txt . This raises a couple of questions: - Is the rfc collection intended to include all RFCs, or were the elements of the collection chosen individually? i.e., is it "default accept" or "default deny"? - Are there any MIBs in the new list that shouldn't be there? I got rid of COFFEE-POT-MIB already ;-) - Would it be useful to have these scripts for Net-SNMP (or for me to run them and occasionally submit updates to the rfclist file?) - Is it useful to do the same with IANA MIBs? Thanks, Bill ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
