(unknown)
Juergen Schoenwaelder <[email protected]> Fri, 21 Nov 2003 18:20:07 +0100
| Newsgroups | gmane.ietf.snmpv3 |
|---|---|
| Message-ID | <[email protected]> |
>>>>> owner-snmpv3 writes: poojan> I want to convert a group of MIB Scalars into a single MIB poojan> Table of a propriety MIB. poojan> I am not sure how to go about it. poojan> The options that I can think: 1. Obsolote all MIB Scalars and poojan> create a new MIB Table with the new name of for each of the poojan> MIB Objects eventhough the functionality remain same for all poojan> them. poojan> 2. Deprecate all the existing MIB Scalars and continue to poojan> provide support. At the same time create a new MIB Table with poojan> the same set of MIB Objects with the name changed. poojan> 3. Comment out the existing MIB scalars. Define a new MIB poojan> Table with the same set of MIB Objects and keep the same name. Option 3. has no advantage which I can see compared to option 1 and option 2 so I would advise not to do this. Whether you deprecate the scalars or obsolete them really depends on the question whether you can/want to still support them. If you can support them (in the sense that the semantics can still be satisfied), then you should just deprecate the scalars to get a smoother transition period. In other words: If you can still implement the scalars with the right semantics, I suggest to go for option 2. If the scalars just do not work anymore and applications really need to use the table objects, go for option 1. /js -- Juergen Schoenwaelder International University Bremen <http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany