Skip to main content

OCAP SNMP Interface please confirm MIBObjects are in TLV format

1 reply [Last post]
mertl
Offline
Joined: 2010-06-22
Points: 0

When Calling MIBManager::setMIBObject(MIBObject mibToSet)
Is the data in MIBObject:: byte[] getData() in the format of TLV or just V?
ie for an OctecString is it { 0x04 0x0a 'H' 'e' 'l' 'l' 'o' } or { 'H' 'e' 'l' 'l' 'o' }?
I assume it is in TLV format
also when getting MIBManager::MIBDefinition[] querytMIBs(oid)
each MIBDefinition.getMIBObject() is also in TLV format.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
sarendt
Offline
Joined: 2009-07-21
Points: 0

The OCAP spec hints that it is TLV but doesn't seem to explicitly say it. If it were not TLV, then there would be no way to determine data type except by a separate reference to the mib file. So, I think it's TLV.
MIBDefinition.getMIBObject() returns a MIBObject, so, within the MIBObject, the getData call would return TLV.