Hi Magnus Fromreide, Thanks a lot for information. I will go through the RFS 2578.
Regards, Pushpa.T On Mon, Oct 16, 2023 at 11:35 PM Magnus Fromreide <ma...@lysator.liu.se> wrote: > On Mon, Oct 16, 2023 at 02:14:28PM +0530, Pushpa Thimmaiah wrote: > > Hi, > > > > Could you please provide information about following > > 1. Is there any lifespan for enterprise OID allocated by IANA. > > OID allocations are forever. > > > 2. When a company got acquired by another company, > > Eg: old company's mib tree .*1.3.6.1.4.1.xxxx.1.2.5* > > New company's mib tree > > * .1.3.6.1.4.1.yyyy* > > > > is it recommended to migrate exiting mib-objects unter new company's > > enterprise OID? > > Customers that have bought a thingie from old-company expect to be > able to continue using their OIDs under old-company.thingie so no, it is > counter to good practice. > > > i.e > > *.1.3.6.1.4.1.yyyy.1.2.5* > > Can we retain exiting mib object as it is i.e under old-company's > > enterprise OID? > > i.e . > > *1.3.6.1.4.1.xxxx.1.2.5 * > > You should do it but you could change their STATUS to deprecated. > > > > > I feel if enterprise-OID has no lifespan or renewal period then old > > company's oid can be retained. > > > > Kindly guide. > > RFC 2578 (STD 58) section 10 is all about how MIB modules should be updated > as time goes by and it lists the allowed changes to a MIB module. > > Read RFC 2578!!! > > /MF >
_______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
