---
oid: "1.3.6.1.4.1.1206.4.2.6.1.4"
short-description: "controllerBaseStandards OBJECT-TYPE"
last-modified: "2025-07-02"
parent-oid: "1.3.6.1.4.1.1206.4.2.6.1"
---

## OID: `1.3.6.1.4.1.1206.4.2.6.1.4`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 1206 transportation(4) devices(2) global(6) globalConfiguration(1) controllerBaseStandards(4)}
```

### Description

```asn1
controllerBaseStandards OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"<Definition>An ASCII string that shall identify all of thestandard document numbers that define or reference MIBs upon whichthe device is based. Where applicable, profiles shall bereferenced rather than the base standards. The string shall beconstructed as follows: The acronym of the standards developmentorganization (or other body) that developed and approved thestandard; a space; the standards document number; a colon; and thedocuments version number as designated by the standardsdevelopment organization (or other body). Separate entries in thelist of standards shall be separated by a carriage return (0x0d)
and line feed (0x0a).
In the case of NTCIP documents prior to formal approval, theversion number shall be the version number in the form of lower
case 'v' followed by the major version followed by a periodfollowed by the minor revision. In the case of approved NTCIPstandards, the version number shall be the four digit year ofpublication followed by a space and the version string indicatedabove. In the case of amended NTCIP standards, it shall consist ofthe four digit year of publication of the published standardfollowed by the upper case letter 'A', followed by the amendmentnumber.
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"
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.