[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
#58 Mapping Modules to Files
- To: sming WG <sming@ops.ietf.org>
- Subject: #58 Mapping Modules to Files
- From: David Harrington <dbh@enterasys.com>
- Date: Wed, 18 Apr 2001 17:17:38 -0400
- Delivery-date: Wed, 18 Apr 2001 14:18:31 -0700
- Envelope-to: sming-data@psg.com
- Organization: Enterasys Networks
- Reply-To: dbh@enterasys.com
I think this is two separate requirements with different potentials
effects on the community and should be described separately.
I have no issue with deciding that there should only be one module per
file, or that more than one can be bundled together. (I prefer the
single module per file to make updates easier)
I am concerned that requiring specific filename formatting may prevent
files from being used on some operating systems. I gladly accept that
the documents should recommend, but not require, a consistent format for
naming mib files. But I would consider it a bad thing to have a compiler
refuse to compile a mib because the filename doesn't match the mib name,
or whatever.
--
---
David Harrington Network Management Standards Architect
dbh@enterasys.com Office of the CTO
+1 603 337 2614 - voice Enterasys Networks
+1 603 332 1524 - fax Rochester NH, USA