Available source records contain 6 distinct definitions; some records may not include a definition.
Show 6 published definitions
controllerBaseStandards · deprecated
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition> For use in this object, an ASCII string that shall identify all of the standard document numbers that define or reference MIBs upon which the device is based. Where applicable, profiles shall be referenced rather than the base standards.
<Format> The version string shall be constructed as follows:
The acronym of the standards development organization (or other body) that developed and approved the standard; a space; the standards document number; a colon; and the documents version number as designated by the standards development organization (or other body). Separate entries in the list of standards shall be separated by a carriage return (0x0d) and line feed (0x0a).
In the case of NTCIP documents prior to formal approval, the version number shall be the version number in the form of lower case 'v' followed by the major version followed by a period followed by the minor revision. In the case of approved NTCIP standards, the publication year shall precede the version number. In the case of amended NTCIP standards, the version number shall be replaced by the four digit year of publication of the published standard followed by the upper case letter 'A', followed by the amendment number.
For example, a message sign may have the following value for this object:
NTCIP 1201:v02.19
NTCIP 1203:1997A1
NTCIP 2101:2001 v01.19
NTCIP 2103:v01.13
NTCIP 2201:v01.14
NTCIP 2301:2001 v01.08
<Superseded by> SNMPv2-MIB.sysORID (from RFC 3418)
<Informative> sysORID provides more refined information using OIDs to identify compliance statements that can be processed by computers without having to parse strings.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.4"
::= { globalConfiguration 4 }controllerBaseStandards · mandatory
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>For use in this object, an ASCII string that shall
identify all of the standard document numbers that define or
reference MIBs upon which the device is based. Where applicable,
profiles shall be referenced rather than the base standards. The
version string shall be constructed as follows: The acronym of the
standards development organization (or other body) that developed
and approved the standard; a space; the standards document number;
a colon; and the documents version number as designated by the
standards development organization (or other body). Separate
entries in the list of standards shall be separated by a carriage
return (0x0d) and line feed (0x0a).
In the case of NTCIP documents prior to formal approval, the
version number shall be the version number in the form of lower
case ‘v’ followed by the major version followed by a period
followed by the minor revision. In the case of approved NTCIP
standards, the publication year shall precede the version number.
In the case of amended NTCIP standards, the version number shall
be replaced by the four digit year of publication of the published
standard followed by the upper case letter ‘A’, followed by the
amendment number.
For example, a message sign may have the following value for this
object:
NTCIP 1201:v02.19
NTCIP 1203:1997A1
NTCIP 2101:2001 v01.19
NTCIP 2103:v01.13
NTCIP 2201:v01.14
NTCIP 2301:2001 v01.08
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.4"
::= { globalConfiguration 4 }controllerBaseStandards · mandatory
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>An ASCII string that shall identify all of the
standard document numbers that define or reference MIBs upon which
the device is based. Where applicable, profiles shall be
referenced rather than the base standards. The string shall be
constructed as follows: The acronym of the standards development
organization (or other body) that developed and approved the
standard; a space; the standards document number; a colon; and the
documents version number as designated by the standards
development organization (or other body). Separate entries in the
list of standards shall be separated by a carriage return (0x0d)
and line feed (0x0a).
In the case of NTCIP documents prior to formal approval, the
version number shall be the version number in the form of lower
case ‘v’ followed by the major version followed by a period
followed by the minor revision. In the case of approved NTCIP
standards, the version number shall be the four digit year of
publication followed by a space and the version string indicated
above. In the case of amended NTCIP standards, it shall consist of
the four digit year of publication of the published standard
followed by the upper case letter ‘A’, followed by the amendment
number.
For example, a message sign may have the following value for this
object:
<DescriptiveName>Controller.baseStandards:text
<DataConceptType>Data Element"
::= { globalConfiguration 4 }controllerBaseStandards · unconfirmed
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"<Definition> For use in this object, an ASCII string that shall identify
all of the standard document numbers that define or reference MIBs upon
which the device is based. Where applicable, profiles shall be referenced
rather than the base standards.
<Format> The version string shall be constructed as follows:
The acronym of the standards development organization (or other body) that
developed and approved the standard; a space; the standards document
number; a colon; and the documents version number as designated by the
standards development organization (or other body). Separate entries in the
list of standards shall be separated by a carriage return (0x0d) and line
feed (0x0a).
In the case of NTCIP documents prior to formal approval, the version number
shall be the version number in the form of lower case 'v' followed by the
major version followed by a period followed by the minor revision. In the
case of approved NTCIP standards, the publication year shall precede the
version number. In the case of amended NTCIP standards, the version number
shall be replaced by the four digit year of publication of the published
standard followed by the upper case letter 'A', followed by the amendment
number.
For example, a message sign may have the following value for this object:
NTCIP 1201:v02.19
NTCIP 1203:1997A1
NTCIP 2101:2001 v01.19
NTCIP 2103:v01.13
NTCIP 2201:v01.14
NTCIP 2301:2001 v01.08
<Supplanted by> SNMPv2-MIB.sysORID (from RFC 3418)
<Informative> sysORID provides more refined information using OIDs to
identify compliance statements that can be processed by computers without
having to parse strings.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.6.1.4"
::= { globalConfiguration 4 }controllerBaseStandards · mandatory
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>An ASCII string that shall identify all of the standard document numbers that define or reference MIBs upon which the device is based. Where applicable, profiles shall be referenced rather than the base standards. The string shall be constructed as follows: The acronym of the standards development organization (or other body) that developed and approved the standard; a space; the standards document number; a colon; and the documents version number as designated by the standards development organization (or other body). Separate entries in the list of standards shall be separated by a carriage return (0x0d) and line feed (0x0a).
In the case of NTCIP documents prior to formal approval, the version number shall be the version number in the form of lower case 'v' followed by the major version followed by a period followed by the minor revision. In the case of approved NTCIP standards, the version number shall be the four digit year of publication followed by a space and the version string indicated above. In the case of amended NTCIP standards, it shall consist of the four digit year of publication of the published standard followed by the upper case letter 'A', followed by the amendment number.
For example, a message sign may have the following value for this object:
NTCIP 1201:v02.19
NTCIP 1203:1997A1
NTCIP 2101:2001 v01.19
NTCIP 2103:v01.13
NTCIP 2201:v01.14
NTCIP 2301:2001 v01.08
<DescriptiveName>Controller.baseStandards:text
<DataConceptType>Data Element"
::= { globalConfiguration 4 }dmsSignWidth · unconfirmed
dmsSignWidth OBJECT-TYPE
SYNTAX Integer32 (0..65535)
UNITS "millimeters"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"<Definition> Indicates the sign width in millimeters including the border
(dmsHorizontalBorder).
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.1.4"
::= { dmsSignCfg 4 }