pgross@NRI.RESTON.VA.US ("Phillip G. Gross") (03/14/90)
Chris, Let me cast a vote in favor of your suggestion to make MIB information widely available. A couple suggestions - - you may want to consider a common format and presentation of the MIB info. The format you choose might depend on what audience you wish to reach (eg, developers may be comfortable reading ASN.1, but end users would probably prefer a text description). - you might consider taking an approach similar to that taken by the folks who put together the NOC Tools catalog in the IETF. They developed a template to insure that the information was presented in a consistent and common format across all entries. Then they organized the various entries into categories, and supplied some additional descriptive boilerplate information. In the end, they produced a very complete and useful document. This may be a larger task than you had planned. However, since Joyce Reynolds is also the chair of the IETF User Services Working Group and keeper of the F.Y.I. series of informational RFCs, you might ask her if she would be willing to help organize such an effort. In any case, I encourage and applaud your suggestion. Phill Gross
chris@SALT.ACC.COM (Chris VandenBerg) (03/15/90)
Phill, Thanks for the additional points to keep in mind. I think Gary Malkin at Proteon brought up the same format question right away and I think it's something we need to hash out. I did, however, make a solemn promise to Joyce that this wouldn't add significantly to her workload and I feel honor-bound to keep that promise. So I will try and voice that concern with regards to suggestions on how to do all this. I'll probably wait for the end of the week to roll around then look at all the great ideas we've gotten to see if we can reach a concensus on how to implement this beast. thanks again, Chris VandenBerg(chris@salt.acc.com) PS - Keep those opinions and ideas coming in folks!