2009/1/12 Larry Brown <[email protected]>:
> In the description of some of the enhancements from v1 to v2 it lists
> the ability to include "bit strings".
I presume you are referring to the pseudo-type BITS.
This is effectively a set of enumerations (i.e. zero or more
of a collection of named values).
> Does this mean that a value held
> under a particular OID could be a binary blob
That has always been supported, using the OCTET STRING type.
Note that OCTET STRING is inherently a binary type - it's not
limited to printable strings (although there are several TCs
which do restrict values to printable strings).
> And if it is, is there some limit to the size of such a file?
>From RFC 2578:
SimpleSyntax ::=
CHOICE {
-- OCTET STRINGs with a more restrictive size
-- may also be used
string-value
OCTET STRING (SIZE (0..65535)),
}
and from section 7.1.2
7.1.2. OCTET STRING
The OCTET STRING type represents arbitrary binary or textual data.
Although the SMI-specified size limitation for this type is 65535
octets, MIB designers should realize that there may be implementation
and interoperability limitations for sizes in excess of 255 octets.
Dave
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
