Warning given is correct??

Hello,
I have defined the SYNTAX of one mib objects as "InetAddressIPv4" - Imported from INET-ADDRESS-MIB. The smilint tool gives an warning that "'InetAddress' should be used instead of `InetAddressIPv4". What is the meaning of this warning?? Is this warning correct?? Thanks & Regards, Vivekanandan.V
*************************************************************************** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended.
If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. ***************************************************************************

Hi!
Vivekanandan> I have defined the SYNTAX of one mib objects as Vivekanandan> "InetAddressIPv4" - Imported from INET-ADDRESS-MIB. The Vivekanandan> smilint tool gives an warning that "'InetAddress' should Vivekanandan> be used instead of `InetAddressIPv4". What is the Vivekanandan> meaning of this warning?? Is this warning correct??
Please take a look at RFC 2851 (or better the upcoming update draft-ietf-ops-rfc2851-update-06.txt). Its intent (and the intent of the above mentioned warning in libsmi) is to support MIB design that uses IP address objects which are indenpendent of the IP version.
If your managed device or service currently does not support all addressing types then the corresponding InetAddressType object(s) are simply limited to a certain subset.
Note that the IESG will no longer accept MIBs in the standards process that do not support IPv6. It's probably a good idea to do the same for vendor MIBs or other non-IETF MIBs.
-frank
participants (2)
-
Frank Strauss
-
Vivekanandan V