| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
TCP/IP MIB Objects, Object Characteristics and Object Types (Page 4 of 4) SMIv2 Textual Conventions In addition to these types, other defined types are also created to again, indicate more specific semantics for a particular data type. These are called textual conventions and are described in RFC 2579 for SMIv2. For example, a type called TimeStamp is defined which is the same as TimeTicks. However, seeing an object using the former rather than the latter makes it more clear that the variable is representing a particular time stamp value. Another is called TimeInterval, which is also just an integer underneath its name, but conveys a different interpreted meaning. If all of the above seemed very confusing to you, note that this topic is in fact a significant simplification of SMI's object definitions. SNMP is so much fun! If an example will help, check out Table 207, which shows an object definition from RFC 3418, using SMIv2.
Note that DisplayString is a textual convention for a displayed text string. The last part, { system 6 }, will be explained in the next topic.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||